Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Fixed: Vista VPN name resolution issue

RRAS, VPN, TS/RDP, Routing and remote Access.

Fixed: Vista VPN name resolution issue

Postby guest » Tue Apr 08, 2008 3:23 pm

We have been using XP to access via cisco VPN for many years. It works great. Recently, we added some new Vista computers. We can establish the Cisco VPN, ping and access the remote computers using IP. However, we can't use the office servers using host name or FQDN. All XP computers don't have this issue. All XP and Vista clients use the same VPN client version and same settings.

1. The VPN server assigns WINS to the VPN client. Why doesn't the Vista access the office server using host name? (see the ipconfig /all below)

2. The nslookup displays Vista uses local DNS while XP uses the office DNS (see below).

3. The routing table displays Vista VPN metric higher than LAN's metric while XP VPN lower than LAN Metric.

Vista VPN

C:\Users\blin>route print
===========================================================================
Interface List
9 ...00 0e 35 39 4f d3 ...... Intel(R) PRO/Wireless 2200BG Network Connection
12 ...00 05 9a 3c 78 00 ...... Cisco Systems VPN Adapter
8 ...00 12 79 56 50 a7 ...... Broadcom NetXtreme Gigabit Ethernet
1 ........................... Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.102 25
10.0.0.0 255.255.0.0 192.168.254.1 192.168.254.7 100
x.x.x.194 255.255.255.255 192.168.10.1 192.168.10.102 100
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
172.16.252.0 255.255.255.0 192.168.254.1 192.168.254.7 100
192.168.10.0 255.255.255.0 On-link 192.168.10.102 281
192.168.10.1 255.255.255.255 On-link 192.168.10.102 100
192.168.10.102 255.255.255.255 On-link 192.168.10.102 281
192.168.10.255 255.255.255.255 On-link 192.168.10.102 281
192.168.254.0 255.255.255.0 On-link 192.168.254.7 281
192.168.254.7 255.255.255.255 On-link 192.168.254.7 281
192.168.254.255 255.255.255.255 On-link 192.168.254.7 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.10.102 281
224.0.0.0 240.0.0.0 On-link 192.168.254.7 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.10.102 281
255.255.255.255 255.255.255.255 On-link 192.168.254.7 281
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.10.1 Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
1 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None

C:\Users\blin>nslookup
Default Server: usr8200.chicagotech.local
Address: 192.168.10.1:53

> exit

C:\Users\blin>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : nc4010
Primary Dns Suffix . . . . . . . : chicagotech.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : chicgaobotanic.org
chicagotech.local

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : chicagotech.local
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network Conn
ection
Physical Address. . . . . . . . . : 00-0E-35-39-4F-D3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.10.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, March 12, 2008 7:40:09 AM
Lease Expires . . . . . . . . . . : Tuesday, April 22, 2008 11:40:19 PM
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Primary WINS Server . . . . . . . : 192.168.10.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : chicgaobotanic.org
Description . . . . . . . . . . . : Cisco Systems VPN Adapter
Physical Address. . . . . . . . . : 00-05-9A-3C-78-00
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.254.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.0.0.29
10.0.0.19
Primary WINS Server . . . . . . . : 10.0.0.29
Secondary WINS Server . . . . . . : 10.0.0.19
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-12-79-56-50-A7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


C:\Users\blin>nslookup
Default Server: usr8200.chicagotech.local
Address: 192.168.10.1:53

> exit

XP VPN
C:\Documents and Settings\blin>nslookup
Default Server: cbgdc.chicagotech.net
Address: 10.0.0.29
C:\Documents and Settings\blin>ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : cbg001383
Primary Dns Suffix . . . . . . . : chicagotech.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : chicgaobotanic.org
chicagotech.net

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0D-9D-8C-FE-AC

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : chicagotech.local
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network
Connection
Physical Address. . . . . . . . . : 00-0E-35-0B-F1-5B
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.104
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.1
Primary WINS Server . . . . . . . : 192.168.10.1
Lease Obtained. . . . . . . . . . : Wednesday, March 12, 2008 8:48:58 AM

Lease Expires . . . . . . . . . . : Wednesday, April 23, 2008 12:48:58 AM

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : chicgaobotanic.org
Description . . . . . . . . . . . : Cisco Systems VPN Adapter
Physical Address. . . . . . . . . : 00-05-9A-3C-78-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.254.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.0.0.29
10.0.0.19
Primary WINS Server . . . . . . . : 10.0.0.29
Secondary WINS Server . . . . . . : 10.0.0.19

C:\Documents and Settings\blin>


C:\Documents and Settings\blin>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0d 9d 8c fe ac ...... Broadcom NetXtreme Gigabit Ethernet - Packet Sch
eduler Miniport
0x3 ...00 0e 35 0b f1 5b ...... Intel(R) PRO/Wireless 2200BG Network Connection
- Packet Scheduler Miniport
0x10005 ...00 05 9a 3c 78 00 ...... Cisco Systems VPN Adapter - Packet Scheduler
Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.10.1 192.168.10.104 25
10.0.0.0 255.255.0.0 192.168.254.7 192.168.254.7 1
x.x.x.194 255.255.255.255 192.168.10.1 192.168.10.104 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.16.252.0 255.255.255.0 192.168.254.7 192.168.254.7 1
192.168.10.0 255.255.255.0 192.168.10.104 192.168.10.104 25
192.168.10.1 255.255.255.255 192.168.10.104 192.168.10.104 1
192.168.10.104 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.10.255 255.255.255.255 192.168.10.104 192.168.10.104 25
192.168.254.0 255.255.255.0 192.168.254.7 192.168.254.7 10
192.168.254.7 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.254.255 255.255.255.255 192.168.254.7 192.168.254.7 10
224.0.0.0 240.0.0.0 192.168.10.104 192.168.10.104 25
224.0.0.0 240.0.0.0 192.168.254.7 192.168.254.7 10
255.255.255.255 255.255.255.255 192.168.10.104 2 1
255.255.255.255 255.255.255.255 192.168.10.104 192.168.10.104 1
255.255.255.255 255.255.255.255 192.168.254.7 192.168.254.7 1
Default Gateway: 192.168.10.1
===========================================================================
Persistent Routes:
None

A: As I understand, when your Windows Vista computers connect to the remote
Office through VPN, these computers can't access the remove computers using
host name or FQDN, but they can access the remote computers using IP
addresses. In the meantime, your Windows XP computers can access the remote
offices using both host name/FQDN and IP address.

If I've misunderstood your concern, please don't hesitate to let me know.

By checking the route table and ipconfig information, I notice that the
default DNS servers are different on Windows Vista computers and Windows XP
computers. According to this behavior, this issue is most likely caused by
the binding order of the network adapters on these Windows Vista computers.

I suggest you follow this KB article to modify the registry to change the
Binding Order on the Windows Vista VPN client:

Cannot Change the Binding Order for Remote Access Connections
http://support.microsoft.com/kb/311218/en-us

Note: Before modifying the registry key, ensure the binding order is
correctly configured on the VPN client:

a. Please open Control Panel -> network connections.
b. Click Advanced -> Advanced settings
c. In the adapters and bindings tab, make sure that the Remote connection
interface is on the top.

Modify the registry key:

1. Click Start, click Run, type regedit32 in the Open box, and then click
OK.

2. Click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage

3. In the right pane, double-click Bind.

4. In the Value data box, select the "\Device\NdisWanIp" item, press
CTRL+X, click the top of the list of devices, and then press CTRL+V.

5. Click OK, and then quit Registry Editor.

6. Restart the Windows Vista computer to see if the issue can be resolved.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9593
Joined: Mon Nov 27, 2006 1:10 pm

Postby chicagotech » Tue Apr 15, 2008 10:11 pm

If the regedit doesn't have NdisWanIp, copy and paste it.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 6486
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Postby guest » Thu Jun 05, 2008 12:43 pm

We had a similar case.

Issue
=====
After dialing up a VPN connection on Windows Vista to the remote office, the users cannot access the shared resources which are located in the remote office by using FQDN or host name.

Cause analysis
=============
The route print result shows that it uses the remote office computer is connected by Intel(R) PRO/Wireless 2200BG Network interface rather than the VPN connection interface.

The binding order is problematic.

Resolution
==========
a. Open Control Panel -> network connections.
b. Click Advanced -> Advanced settings
c. In the adapters and bindings tab, make sure that the Remote connection interface is on the top.

Modify the registry key:

1. Click Start, click Run, type regedit32 in the Open box, and then click OK.
2. Click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage

3. In the right pane, double-click Bind.
4. In the Value data box, select the "\Device\NdisWanIp" item, press CTRL+X, click the top of the list of devices, and then press CTRL+V.
5. Click OK, and then quit Registry Editor.
6. Restart the Windows Vista computer.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9593
Joined: Mon Nov 27, 2006 1:10 pm


Return to VPN, TS and Remote Access

Your Ad Here

Who is online

Users browsing this forum: No registered users and 7 guests