We have run into an issue with some Windows 2000 clients using a single tunnel VPN, (Nortel).
We have an Intranet where some pages have a public address for accessibility over the Internet, and also resolve internally to a private address. The namespace is the same internally and externally, ie. myserver.mydomain.com.
We have Windows 2000 clients that connected to various ISP’s, both cable modem and DSL. When using certain providers, while tunneled in to our network the intranet page is requested through the ISP’s DNS server rather than the internal DNS server. The same system can be taken to another location using the same ISP and the query is only sent to the internal DNS server, as it should.
For example, take the system and hook it up to a roadrunner cable modem here in the HQ, connect VPN, ping myserver.mydomain.com. The query is sent to the internal DNS server and resolves to the internal IP.
Take the same system and connect it to a roadrunner cable modem 5 miles away, do the same procedure, but this time the query is sent to the ISP’s DNS server which of course resolves to the public IP address, however while tunneled in the clients cant get to that address due to the VPN tunnel.
This is happening withvarious systems, across multiple providers (both DSL and cable). We’ve looked at subnets, IP assignments of these problem clients and can see nothing which conflicts with our internal IP addressing scheme.
Has anyone run into this? Regardless, any ideas?