VPN with Server 2003 not able to resolve internal DNS

[bobcpg]

I have setup a Windows Server 2003 Standard server. In this server i have configured RRAS for VPN connections. I can VPN into the server from an external client and Remote Desktop and ping internal workstations by IP address only. When I try to use DNS names of internal clients it does not resolve.

How can i configure it so when i VPN into the server i can use the DNS names of the internal clients?

Thanks for your time.
Bob

 

[her209]

Two things to check:

1. When your VPN client connects, is it getting the IP address of the internal DNS server on the VPN connection?
2. When you ping, are you using the fully-qualified domain name?

 

[LightninTrip]

If you have name resolution issues when using VPN, check the PPTP filtering on the server. If you disable UDP ports 137 and 138 or TCP port 139, NetBIOS packets can't pass through the network. You also need to enable these ports on all firewalls and routers that are between the client and the server for unicast (point-to-point) traffic.

 

[RebateMonger]

An "IPConfig / all" printout from the Command Prompt would be useful to see where your DNS Server is located for your VPN Interface.

It should look something like this, but you'll likely have DHCP enabled (I've having IP addresses assigned from a pool provided by the RRAS Server).

PPP adapter RebateMongers VPN:

Connection-specific DNS Suffix . : rebatemonger.local
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.18
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.16.2
192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2
Secondary WINS Server . . . . . . : 192.168.16.2

 

[bobcpg]

Ok sorry for the late reply but, here is my ipconfig /all output from my home computer when i am VPN into the WorkVPN.

Windows IP Configuration

Host Name . . . . . . . . . . . . : luke
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : hsd1.mn.comcast.net.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.mn.comcast.net.
Description . . . . . . . . . . . : ULi PCI Fast Ethernet Controller
Physical Address. . . . . . . . . : 00-13-8F-A1-B2-C3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 68.87.77.130
68.87.72.130
Lease Obtained. . . . . . . . . . : Monday, April 30, 2007 9:50:27 PM
Lease Expires . . . . . . . . . . : Tuesday, May 01, 2007 9:50:27 PM

PPP adapter WorkVPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.10.15
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.1.10.15
DNS Servers . . . . . . . . . . . : 10.1.10.200
68.87.77.130

 

[bobcpg]

Bump....Help??

 

[netsysadmin]

N/M

 

[RebateMonger]

Originally posted by: netsysadmin
The other issue is your subnet mask on the VPN connection.

255.255.255.255 is the normal subnet mask for this Windows VPN.

THIS shouldn't be, though:
DNS Servers . . . . . . . . . . . : 10.1.10.200 68.87.77.130

That public DNS Server is just helping to hide a problem.

 

[netsysadmin]

RebateMonger....You know I never notice that the IP and gateway are the same and the subnet mask is 255.255.255.255.

Doh!!

John

Originally posted by: RebateMonger

Originally posted by: netsysadmin
The other issue is your subnet mask on the VPN connection.

255.255.255.255 is the normal subnet mask for this Windows VPN.

THIS shouldn't be, though:
DNS Servers . . . . . . . . . . . : 10.1.10.200 68.87.77.130

That public DNS Server is just helping to hide a problem.

 

[bobcpg]

If the server's ip addresses are 10.1.10.200 and 10.1.10.201 should i have the first 2 dns servers be these addresses?

 

[netsysadmin]

Yes if they host your DNS for you AD Domain. Also dont include any external DNS server is the VPN settings.

John