04-27-2009 11:16 AM
We have a company where we all work out of our homes, but need to sync to the master database, which is, unfortunately at a location that cannot get a static IP address.
After MANY go-arounds with Act Support trying to get Internet Sync working (this seems like a very "new" method to them that they haven't quite worked out all the kinks from), they switched us to Network Sync using the IP address. This works fine, except for the fact that the IP address changes on the master database all the time. A real pain.
So... we got a domain name using no-ip.com's free service, that allows a static domain name to always be able to find our dynamic ip address on the master database machine.
Unfortunately, again, ACT! doesn't seem to support entering a domain name in the Network Sync windows.... or so it seems.
Has anyone else done this (used a domain name) succesfully? The reason I say "so it seems" is that our first attempt on one of the client machines seems to have disabled the remote database. Synchronize Now is grayed out and when we did try syncing the first time it said "Remote Database is Disabled". Huh??
04-28-2009 02:18 PM
It was strange... we had everything working in terms of networking, but the sync would always fail, no matter what we did.
We could telnet in to all the ports that needed to be open (80, 65100), but the thing just would not sync. Clients always failed on attempts to sync.
As soon as they (Act Support) switched us to Network Sync using IP addresses, BAM! Worked like a charm... except for the dynamic IP issues, but that's workable, even if slightly painful. :-)
04-30-2009 10:22 AM
Hmm... can't remember exactly. It was something like "Unable to sync". That was after maybe a 10 second pause where I assume it was *trying* to connect.
The "progress" window that shows you what steps it's on (at least the one that shows up during Network Sync) never started. I can only assume the same window would appear during Internet Sync, but we never saw it even start.