We have 10 different locations connected through VPN, but they all on different subnets. For example: our main location is 192.168.0.xxx, location 1 is 192.168.111.xxx, location 2 is 192.168.112.xxx and so on. We have ADNM running on main location, but when I try to run installation task on other location it fails to install client. If I create .msi installer and run on remote location computer it installs fine, but in event log I get errors that it can’t communicate with ADNM. What do I need to do to make it work?
They use different subnet masks - so they can’t see (=address) each other?
How about your mail server, for example? Do you have a mailserver in each location, or it’s somehow connected from the branches?
Well, thing is that all subnets are bridged. Meaning that I can see computers on remote locations without any problems. I can log into shared drives, transfer data and do other things I need. However, all remote locations are on child domains. For example: main location domain is abc.local, remote locations are remote1.abc.local, remote2.abc.local and so on. I think problem is with authentication somewhere. Does ADNM read FQDN addresses from DNS or it is using something else?
Yes. I can telnet into server without any problems on ADNM ports. But still can’t get client to connect to AMS. I even decided to try multi-AMS setup. I set AMS at remote1, then subscribed to main location AMS. Everything went fine until I decided to do replication. Task runs without error on main AMS, but remote1 AMS did not receive any replication data. Now, how would I unsubscribe remote1 AMS? I didn’t see any information how to do it anywhere.
Multi-AMS setup shouldn’t be necessary in your case (to “undo” it, just delete the new server object in the Management Servers folder in the ADNM console connected to the “root” AMS).
Anyway, if you can telnet to the AMS, it should really work OK. Could you please send me the files \data\error.log and warning.log from any of the machines that experience the connection problems?