03-02-2011 11:25 AM
Our remote users have not successfully synchronised in 2 days. They receive no updates, main db does not receive theirs.
They do not receive any errors. There are no errors/issues/events reported on our server. We've rebooted our server and confirm that all services are running...
Network clients are unaffected.
Is there a usual list of suspects to verify when this occurs? Any further checklist to follow or better directions to troubleshoot would certainly be well received.
03-02-2011 03:14 PM
You say "LAN" sync.. so I take it you are not using ftp or http(s).
LAN Sync requires both the PC and the WIndows user to authenticate to the domain and have "rights" to the synch server Infiles/Outfiles/Failed shared folders.
From the remote you should be able to do:
Start->run \\ServerName\Shared file location of in/out/fail and be able to create/destroy/delete a file there. If that is NOT working, you have found your problem.
03-02-2011 05:58 PM
Thanks once again for the feedback RJ. My 'checklist' is growing.
Ultimately, it was a DNS failure issue and a name resolution opened up the floodgates for all our remote db users.
PS - yes, it was neither ftp nor http(s).
03-02-2011 07:10 PM
I strongly suggest you migrate to http(s) fo rsynch. This eliminates the need for users (or their system) to authenticate w/the domain/server. It's far safer security wise and far more reliable.
We never use "LAN" synch anymore.. have not used it w/clients for at least 3 or 4 years.