Pathping routes via incorrect IP on a multiple nic PC

[stormtrooperofdeath]

Sorry if this is in the wrong forum.

The history...
In my company, i have remote users accessing our network through a VPN. We use a broadband ADSL conenction to get them on the internet, and tunnel in to our network via Intel's Shiva.

By default, Shiva installs 2 Virtual NICs. When a user logs into their PC, the broadband modem/router assigns the physical NIC an IP address (say, 10.7.1.101). When the user tunnels in to our network, the VPN will assign the Virtual NIC an IP address, say 10.7.1.170. The VPN also specifies WINS, DNS etc.

One of my users had no problems accessing all of the company network resources, and then their PC was replaced by a newer one. Since then, the user has been having trouble accessing some of our network resources, highlighted by ping requests timing out. The router recognises the PC and assigns it an IP address, and the users VPN profile hasnt changed, so i think the problem is with the new computer. All the network settings are configured exactly how they were before. The O/S is XP.

The problem.....
I used pathping to ping a resource that the user has not roubles connecting to, and the IP address that pathping used was the Virtual NIC (10.7.1.170).

I then used pathping to try and ping a resource that the user cannot access, and the IP address that pathping used was the physical NIC (10.7.1.101).

So it seems that the user cannot access certain company network resources because certain requests use the LAN IP address which obviously isnt recognised on the VPN. I dont understand why some requests use the correct NIC and others dont - and i'm not sure what to do about it.

Can anyone help at all???

Thanks!

 

[predamarcel]

which are the netmask(s)?
for me looks like 10.7.1.170 and 10.7.1.101 are in teh same subnet (ussualy is a C class - mask 255.255.255.0).


PM

 

[stormtrooperofdeath]

Yeah, the netmask for both is 255.255.255.0.....

 

[predamarcel]

This is an unusual situation.
(probable you have to change the netmask,
or have to change one of the IP).
Are you sure that the prevous computes has had the same settings?

Can you provide us the output of `route print' command, when the VPN is activated.


PM

 

[stormtrooperofdeath]

Thanks for your help so far....

Ok, to add a bit more confusion.....

I unplugged the network cable that goes to the ADSL router and tried getting through to our private network through a dial up connection instead. I couldnt ping the server i wanted, so i added a persistant route and then it worked. when i rebooted the PC and tried using ADSL again, the persistant route remained but i couldnt ping the server again.

The computer is set up exactly how the old one was, although i cant get access to the old one now so i cant see the routing tables. The ADSL modem/router config hasnt changed, and i am able to add new computers to it and they can access all the resources like they should. So the problem is definitely the PC.

Here is the routing table. I took the PC back to my office to try and figure it out. For the sake of this, I was directly plugged into the network and then made another VPN connection to the network. And the behaviour is the same - when I pathping 10.7.1.2, it uses the VPN NIC. When I try to pathping 10.7.2.1, it uses the physical NIC - which is wrong!

H:\>ipconfig /all



Windows IP Configuration



Host Name . . . . . . . . . . . . : MSVAUPTKPC001

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : au.hme.harsco.com

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 00-0D-60-47-45-E4

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : No

IP Address. . . . . . . . . . . . : 10.7.1.110

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.7.1.28

DHCP Server . . . . . . . . . . . : 10.7.1.2

DNS Servers . . . . . . . . . . . : 10.7.1.2

10.7.1.3

Primary WINS Server . . . . . . . : 10.7.1.3

Secondary WINS Server . . . . . . : 10.7.1.2

Lease Obtained. . . . . . . . . . : Thursday, 12 February 2004 10:12:59 AM

Lease Expires . . . . . . . . . . : Sunday, 15 February 2004 10:12:59 AM



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Shiva VPN Client Virtual Adapter #2

Physical Address. . . . . . . . . : 00-C0-45-00-00-02

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : No

IP Address. . . . . . . . . . . . : 10.7.1.170

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DHCP Server . . . . . . . . . . . : 10.7.1.30

DNS Servers . . . . . . . . . . . : 10.7.1.2

Primary WINS Server . . . . . . . : 10.7.1.2

Lease Obtained. . . . . . . . . . : Thursday, 12 February 2004 10:18:34 AM

Lease Expires . . . . . . . . . . : Friday, 11 February 2005 10:18:34 AM



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Shiva VPN Client Virtual Adapter

Physical Address. . . . . . . . . : 00-C0-45-00-00-01

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : No

IP Address. . . . . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . . . . :

DHCP Server . . . . . . . . . . . : 255.255.255.255



H:\>pathping 10.7.2.1



Tracing route to auptknt001.multiservgroup.com [10.7.2.1]

over a maximum of 30 hops:

0 MSVAUPTKPC001.au.hme.harsco.com [10.7.1.110]

1 10.7.1.26

2 ^C

H:\>pathping 10.7.1.2



Tracing route to auwlgnt001.multiservgroup.com [10.7.1.2]

over a maximum of 30 hops:

0 MSVAUPTKPC001 [10.7.1.170]

1 auwlgnt001.multiservgroup.com [10.7.1.2]



Computing statistics for 25 seconds...

^C

H:\>netstat -rn



Route Table

===========================================================================

Interface List

0x1 ........................... MS TCP Loopback interface

0x2 ...00 0d 60 47 45 e4 ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport

0x3 ...00 c0 45 00 00 02 ...... Shiva VPN Client Virtual Adapter #2 - Packet Scheduler Miniport

0x4 ...00 c0 45 00 00 01 ...... Shiva VPN Client Virtual Adapter - Packet Scheduler Miniport

===========================================================================

===========================================================================

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 10.7.1.28 10.7.1.110 29

10.7.1.0 255.255.255.0 10.7.1.110 10.7.1.110 30

10.7.1.0 255.255.255.0 10.7.1.170 10.7.1.170 30

10.7.1.110 255.255.255.255 127.0.0.1 127.0.0.1 30

10.7.1.170 255.255.255.255 127.0.0.1 127.0.0.1 30

10.7.2.1 255.255.255.255 10.7.1.26 10.7.1.110 1

10.255.255.255 255.255.255.255 10.7.1.110 10.7.1.110 30

10.255.255.255 255.255.255.255 10.7.1.170 10.7.1.170 30

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

224.0.0.0 240.0.0.0 10.7.1.110 10.7.1.110 30

224.0.0.0 240.0.0.0 10.7.1.170 10.7.1.170 30

255.255.255.255 255.255.255.255 10.7.1.110 4 1

255.255.255.255 255.255.255.255 10.7.1.110 10.7.1.110 1

255.255.255.255 255.255.255.255 10.7.1.170 10.7.1.170 1

Default Gateway: 10.7.1.28

===========================================================================

Persistent Routes:

None



Im trying to access 10.7.2.1. On another PC, the route is set up and the gateway is the VPN adapter IP. Im concerned about the 3rd entry from the bottom:
255.255.255.255 255.255.255.255 10.7.1.110 4 1

The interface 4 is a VPN NIC. Its associated gateway is the IP address binded to the physical NIC. On another PC that works like it should, the IP for this VPN NIC interface is the VPN NIC. I tried to change the route path for this entry but it says that 255.255.255.255 is a bad destination address?

I don't know what to do! I dont know whether uninstalling TCP/IP and reinstalling will clear these tables so I can start fresh...

Any ideas?

 

[stormtrooperofdeath]

Just figured it out!

I was using Shiva version 6.8, I was sent a copy of the latest 6.9 and installed it on the affected clients and everything works fine now!!

What a relief, I thought I was going crazy.

Thanks for your help anyway!