Good morning fellow techies,
I am having VPN issues that I never had before I upgraded my nt 4.0 PDC to a win2k DC.
Here is my setup for my remote users:
They dial into AOL or whatever ISP they use. They connect to my firewall, via a PPTP VPN connection. The firewall gives them an IP address from our external (public) block of IP's, such as 207.190.36.x. With that IP address, they are (were) able to access all our internal network resources. Our internal subnet is 192.168.x.x. There were never any issues before, they could hit our mail server, browse via network neighborhood, ping by dns name etc.
Now, for some reason, they can no longer browse using dns names. DNS is just not working through the vpn connections. They can still hit network neighborhood and browse by machine name, and they can ping every machine on the network with the exception of the DC which is also running AD dns. When I run an ipconfig on a laptop connected via vpn, I get the proper IP of the DNS server.
I cant tell if this is 2 separate issues or not. Is there something that has to be set on the win2k DC that allows pinging from outside the local subnet? I don't have this disabled on my firewall.
Is there some sort of routing entry I have to set up to allow DNS to work? I am at a loss!
Sharyn
I am having VPN issues that I never had before I upgraded my nt 4.0 PDC to a win2k DC.
Here is my setup for my remote users:
They dial into AOL or whatever ISP they use. They connect to my firewall, via a PPTP VPN connection. The firewall gives them an IP address from our external (public) block of IP's, such as 207.190.36.x. With that IP address, they are (were) able to access all our internal network resources. Our internal subnet is 192.168.x.x. There were never any issues before, they could hit our mail server, browse via network neighborhood, ping by dns name etc.
Now, for some reason, they can no longer browse using dns names. DNS is just not working through the vpn connections. They can still hit network neighborhood and browse by machine name, and they can ping every machine on the network with the exception of the DC which is also running AD dns. When I run an ipconfig on a laptop connected via vpn, I get the proper IP of the DNS server.
I cant tell if this is 2 separate issues or not. Is there something that has to be set on the win2k DC that allows pinging from outside the local subnet? I don't have this disabled on my firewall.
Is there some sort of routing entry I have to set up to allow DNS to work? I am at a loss!
Sharyn