In the sender.log file on the secondary, I am getting an error when the secondary is trying to connect to the primary. The error is 'There is no existing connection, Win32 error -1396". Could someone point me in the right direction on this one?

That's a login failure: the target aacount name is incorrect. Can you doublecheck the address on the primary site. Maybe delete it and create it again.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Thanks, Kent. I already have 4 other secondaries that are working just fine. Here is what is different. The ones I am trying to connect are in a different town from the primary. All are on private IPs locally and using NAT addresses to get out. We cannot change the DNS entries for these machines, as they would then not be able to communicate within their local LAN. So we have put entries in the hosts file on each end to make it work. The secondary has already created its object in AD and I can ping both ways as well as see the IIS7 screen in IE when I type in the server name. That's the background. Now...which account are you talking about? The primary server name?

I also noticed that SCCM is not getting the FQDN from winsock. This one is new to me. Any help is greatly appreciated. Wes

Please cancel this. I found the answer....typo in one of the hosts files. Thanks for your forum.

Hi, Glad to hear the issue resolved. Also, if you have any further concerns, please do not hesitate to let us know and we are happy to be of further assistance. Thanks,Yog Li -- Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.