Hey guys Not sure if this is the correct location to ask this question.. if not please feel free to point me in the correct direction. I've seem to be stuck with a particular problem, which I just cant solve. Here is some background info. We are small company with 8 users. We have a shared network drive on the development server (Windows Server 2008 R2) we use to sync our development code/other files. This server is connected to domain (SBS 2008) running. 2 Physical Servers / 4 laptops and 4 desktops (7 Hyper V machines) All the machines are running Windows 7 Pro 64x (The problematic PC is running Ultimate 64x) All our machines are running Symantec Endpoint Protection The problem I have is the following, all our users can sync (Beyond & Compare) files without any issues to the server, apart from 1. When he used Beyond and Compare to sync files, it would start and just hang. And manually coping would work then. This problem started about 2 weeks ago. But today even if he tries manually copy files to the server, it will start, then just hang after 3-4 seconds. Now, this is the things I've tried to do. I took away his folder permissions on the shared drive, and re-added him. I've deleted his DNS records on SBS, recreated it and gave him a fixed IP address. I connected him to the wireless router and disabled his local network adapter and visa versa. Tested his network jack/cable with my own laptop (and it works fine on my machine) so its not the network itself. Disabled his Firewall/Anti-Virus And none of these helped. Its quite frustrating to him, because now he has to put his code on a external drive, and bring it to me each time he has to sync his files. Maybe I'm just missing something simple and somebody will be able to help me. Any help would be appreciated. I'm just a programmer, not a Server Admin (even thou I maintain the servers lol, but I have a basic understanding on how it works.) Thanks

Dear marnus, Very simple just go to your server machine STOP or uninstall Network Threat Prtection and Let the magic Happen. this problem happened with my few days back and this solution works. Cheers! Rehman Ghani

Thanks for the suggestion. I guess I should clear some things up quickly. Server 2008 R2 is only used for Hyper-V's. And doesn't have any antivirus installed. Also no shares on this server. Its only role is to host the Hyper-V's. Its running five, Windows 7 Pro x64 machines we use for testing/development and general things. But, I did disable network thread on the machine which is having issues. I'll get back to you. *Edit Nope, problem persists.

Hi, According to your current status that you have only one Windows 7 computer encounter the slow copy, I think it may be related to the application such as the third-party. So please try doing the Clean Boot and Safe Mode on this problematic Windows 7 to see if the problem still persists: Clean Boot ================== Note: In a Clean Boot, all the 3rd party services and startup programs are disabled. If the server can start normally in Clean Boot, we can be sure that the issue was caused by some 3rd party service or application. a. Click Start, click Run, type "msconfig" (without the quotation marks) in the Open box, and then click OK. b. In the Startup tab, click the "Disable All" button. c. In the Services tab, check the "Hide All Microsoft Services" checkbox, and then click the "Disable All" button. d. Click OK and restart your computer. Safe Mode ================= If the Clean Boot cannot resolve the issue: Please try to take a safe mode test. In this mode, we can totally get rid of the problem caused by the 3^rd-party in your computer. To do this, a. Restart your computer, and before the system boot, press F8. b. Select "Safe Mode with Networking", and then press ENTER. c. After the computer startup, check if the problem persists. Please let me know the result of this. Thank you. Best regards, Annie Gu

Hi Sorry for the late reply. After some troubleshooting and installing wireshark, we determined that the main problem was faulty drivers. When I reinstalled the network drivers, the issue went away.