Slow Synchronization
I moved my users from a server running Exchange 2003 sp1 to a server running Exchange 2003 sp2. I simply turned off the old server. Everything runs great except the synchonization process. Whenever a user clicks on "send/receive", the process gets to 50-52% complete before hanging up on the sychronization process. I have read just about every article, and can not find a solution. It seems the client might be looking for the old server, times out, then finishes after contact with the new server. I'm at a loss. What is causing the sychronization process to run slow on the server running sp2? Is this a known issue? Are there effective ways around this, short of turning off "cache" mode?
August 9th, 2007 6:38pm

Is name resolution working for the new server? Go to the command prompt for one of your servers and type PING ServerName (where ServerName is the name of your server). See if it comes back right away and starts pinging and if the ping response times are short (less than 50ms)
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2007 1:39am

I don't think WINS/DNSis theissue. C:\Documents and Settings\scote>ping cnetmail Pinging cnetmail.convergentnet.com [192.168.228.6] with 32 bytes of data: Reply from 192.168.228.6: bytes=32 time=1ms TTL=127Reply from 192.168.228.6: bytes=32 time=1ms TTL=127Reply from 192.168.228.6: bytes=32 time=1ms TTL=127Reply from 192.168.228.6: bytes=32 time=1ms TTL=127 Ping statistics for 192.168.228.6: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms
August 10th, 2007 5:26pm

I don't know why a client would look for the old server after its been homed to another server. Unless..... the client had never attempted to connect to the old server before your shut it down. In such case it should fail to connect altogether. I don't think I would see anything along those lines in the issue... are the clients running in cache mode? If so delete the cache file on one and see if fixes the issue? Just my 2 cents
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2007 10:38pm

seems like a name resolution problem. Have you replicated all System Public Folders, such as OAB, Free/Busy folder to the new server
August 10th, 2007 11:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics