brokernetworkMemberSep 05, 2007 at 9:47 am #127599
We have roughly 30 clients connecting in via OpenVPN to a windows 2003 AD domain. On our side of the network there is the following equipment:
Server 2003 PDC (x64)
Exchange 2007 (running on Server 2003 x64)
All clients are laptops running the following:
Windows XP Pro
Office 2007 Standard
OpenVPN GUI Client (http://openvpn.se)
When a user attempts to connect to our AD domain via VPN the following may occour:
connection to remote resources fails (e.g network shares)
connection to the exchange server fails
After further investigation the issue seems to lie with remote clients not resolving machine names (Although pinging the IP address works ok). On the second (virtual) adaptor (which OpenVPN creates) we have specified the active directory DNS servers. Windows XP seems to be using the DNS server addresses on the physical network connection instead of the servers specified on the virtual network adaptor. However an NSlookup will report that it is using the dns servers specified on the second adaptor.
If the machine is left ~30 minutes it seems to revert to using the DNS servers specified on the virtual adaptor – and hence resolving names works & connection to remote resources works.
How does windows XP behave when you have two “active” network connections, both with different DNS servers specified (via DHCP on one adaptor and manually on the second)?
We spent time building a WINS server and specifying this on the second network adaptor to no avail.
Can anyone suggest anything else?
You must be logged in to reply to this topic.