My question boils down to "Under Windows Server 2003, how can you stop a Network Adaptor registering it's address with DNS".
We're running the "software" VPN Service, Hamachi (www.hamachi.cc
) on one of our Domain Controllers/File/Print Servers within an 2003 Active Directory domain.
Hamachi is on the DC purely to allow someone at a regional office access to Files - it is not used to tunnel any AD services such as Domain Authentication.
However, despite turning off the "Register this connection with DNS" option on the Hamachi adaptor, the 5.82.x.x address of the Hamachi Adaptor keeps registering itself in the AD integrated DNS zone.
The result of this is that other DC's in other sites try to use the 5.82.x.x address, and AD replication problems occur.
Once I've manually deleted the 5.82.x.x DNS entry - things spring back into life, but it's a pain constantly having to do this.
The DNS Server itself is only registered to serve addresses on the 192.168.10.2 range. It accepts all Dynamic Updates.
Can anyone suggest how to prevent Hamachi from registering it's details in DNS, so the Adaptor is simply used as a VPN tunnel for the sites that wish to use it?
I also have a thread running at the Hamachi Forums (http://forums.hamachi.cc/viewtopic.php?p=41547#41547
) but the Hamachi folk are stumped on this, so I thought I'd turn to the good folks at EE for help. :-)