Tuesday, February 27, 2007 2:35 PM
I've set up the WHS and have tried to back up 2 different pcs, the first is running Windows XP and is connected via wireless to the network and this backed up with no problem at all. The second PC running Windows Vista is wired to the network and I am unable to complete a successful backup. The Message "TCP Connection between Client and Server Lost" appears after about 1hr 40 Minutes.
The Vista machine has had the firewall disabled and I've changed the power saving features but all to no avail at present. Any help would be much appreciated
Tuesday, February 27, 2007 3:54 PMModeratorCraig, do you have more than one network interface installed in the machine that's having issues? If so, you can try disabling all but one and see if that helps.
Tuesday, February 27, 2007 9:14 PMI have only one network card in my machine. The next thing I have tried is to unselect ipv6 against the network connectors and just use the ipv4 protocol to see if this has any effect
Tuesday, February 27, 2007 10:09 PMModeratorAha! That's a known issue under Vista. See the bottom of this thread.
Craig Durose wrote: I have only one network card in my machine. The next thing I have tried is to unselect ipv6 against the network connectors and just use the ipv4 protocol to see if this has any effect
Friday, March 02, 2007 2:24 PMI've read the thread that you provided and this hasn't provided an answer. I disabled the ip6 protocol and it made no difference at all. The backup usually get to around 80% and then fail with a lost connection.
Monday, March 05, 2007 3:33 AMMine appears to fail with the same problem on both my XP machines shortly after the backup starts.
Friday, March 09, 2007 9:08 PM
I have the same problem. I am dual booting Vista and XP SP2. I start the backup and it determines what clusters have been changed and then starts to send data to the server. I can see from my Microsoft Wireless router where my computer and Server are plugged in that data is passing but the server connection keeps dropping. I also noticed that the network utilization tab in Task Manager states that I am getting 50% utilization but not steady. It will drop to 2% then up to 50 and back down ect. ect.
I also noticed that when I copy a file to the server from XP and Vista that it takes a while longer than it does to copy it from the server to the client. Server has a Linksys PCI NIC set to 100 full duplex and the client has a SIS on board NIC.
Wednesday, March 14, 2007 1:40 AM
Hmmm, I'm getting this problem too.
Backup makes it to somewhere around 30% and stops. Server says the backup failed because, "TCP Connection between client and server lost." Running XP SP2. I originally noticed this on a wireless connection, so I disabled the wireless card and ran a cable to the server. Same error.
Wednesday, March 14, 2007 2:21 AM
I have some further information:
For me, once the backup fails, the server seems to lose it's network connection. My client machine still seems to work normally, can access the internet, and can ping my router. The server machine cannot ping the client or the router. Rebooting the server restores it's network connection, but if I run a backup again, it fails the same way and needs to be rebooted again.
Wednesday, March 14, 2007 3:53 AM
It's a stretch, but it's not too hard to try: I had NetBIOS name resolution issues on my systems and had to 'hard code' the SERVER's IP address on each of my clients. Could it be possible it's forgetting the IP? I know this sounds weird, but I've had Windows sessions drop MID-SESSION because of name resolution problems.
Article on TCP/IP Host Name Resolution Order here: http://support.microsoft.com/kb/172218
There are also several posts on host file editing.
Give it whirl?
Thursday, March 15, 2007 5:11 PM
Thanks for the tip. I told my router to always assign the same IP to the server, then I entered the server name and IP address into the clients host file and the backup completed successfully.
If this was a dropped session because of a name resolution issue, it still seems odd that it would take down ALL networking on the server and force me to reboot the server to get networking working again.
Anyway, I've had 1 successful backup so far, I'll keep watching it.
Thursday, March 15, 2007 8:37 PMMy issue was fixed. It was the nic on the server that was causing issues. I had to set it to 100 half in order to get it to work. I need to get a new one...lol.