Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN on W2K issue

Status
Not open for further replies.

drhixson

MIS
Aug 6, 2000
71
US
greetings all... I have a Windows 2000 Server, with VPN installed. Our DNS setting all point to our ISP's DNS (we do not have a DNS server locally) I can configure my client to connect to the VPN server, everything connects and everything is dandy, only thing is I cannot resolve any names and cannot see anything on the network. Would this be a problem because I do not have a local DNS server?
 
You need either a DNS server internally or a WINS server that the VPN client can use for name resolution.
 
We do have a WINS server... Where do I go to tell the VPN server to use WINS? .... sorry if its a dumb question
 
Hello drhixson... I am having the same problem also
...we have both internal DNS and WINS servers.
However, when clients VPN in they resolve names or IP using their ISP's DNS. As a result the ISP cannot see our private DNS thus unable to resolve IP/names correctly.
Any one out there with any suggestions??
...The VPN as been set to overide all incomming DNS
Help!!!!
 
Hmm, makes sense... wonder if it is a client setting?
 
I think client setting would not make a difference
as the ISP's DNS takes priority, then our local DNS should take priority over the ISP's which it is not doing
What do you think?
 
Yea I'm not sure... I have RAS and VPN on the same server and RAS works fine so your right it would have to be the ISP's DNS overidding the local DNS and\or WINS when the VPN tunnel is established... Wonder if putting a LMHOSTS file on the client would help?
 
Yes,LMHOST will work... but we have over a thousand clients
and , also that would be defeating the purpose of a DNS server.
I wonder now if it is a hardware / software issue at the VPN level
 
Yes, I agree.... I'll keep hammering away at it and I'll let you know what I come across
 
Same here drixson Ill keep you posted.
Anyone else out there with similar issues
or possible solutions?

HELP!!!! [dazed]
 
If you are using PPTP, the settings are configured under the TCP/IP properties for the PPTP connection. If you are using an IPSec solution, the method may vary.

Also make sure you have "Use default gateway on remote network" checked.
 
okay, mine are all set to use DHCP, and my scope and global options are all correct, but the problem still occurs
 
Have you verified on the client machine after connecting that these settings are correct?
 
Hey drhixson... Any Luck?
I saw what ntrop wrote yesterday.
and mine are all set to use DHCP also as well as scope and global options being correct.
 
that is how mine is set too.. I think I need to enable DHCP relay on the DHCP server... our IP range is 10.1.2.x but when I connect via VPN my ip on the client is 10.0.2.x with a diferent subnet
 
Hi,

If you connect to your VPN server then all traffic (including WINS and DNS request) is sent to that server and does not cross your network outside the tunnel. To prevent the client from not being able to resolve WINS and DNS request (because it simply can’t reach these servers) you should uncheck “Use default gateway on remote network” ip property. This prevents the machine from sending any traffic other than traffic for the vpn server (actually the 10.0.2.x network) through the VPN. Doing this it should be possible to at least reach the provider DNS server. Hope this helps a little.
 
I am not replayng to this post! instead I would like to know where do I go to post one?
 
I think I'm having the same problem. When using win98 clients I can connect to the VPN and browse the inital directory. But from there it won't go to any other nested directory and terminates my connection when I try. What's really driving me crazy is that my XP clients work great! They can even print on the network printers. I'm sure this has something to do with WINS resolution but not quite sure where to start.
 
I've found a solution to this - well it works for me anyway on Win2K.

Find the VPN connection in your dial-up-networking (Network and dial up or whatever it is called these days). Right click the icon and choose properties.

Along to the network tab and select TCP/IP and press properties. In the DNS bit add the internal IP address of the DNS server.

As I say, this has worked for me - you're milage may vary.

Bryan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top