XP computers can't ping other computers on other side of VPN

[goombawaho]

In the same office and connecting to the same VPN at another office. The XP computers cannot ping or connect to computers on the other side of the VPN while the Windows 7 computers can. There is a difference - the IPCONFIG. What do I need to change in XP to allow communication to the other side?

XP computer - static IP address
Ethernet Adapter
192.168.1.48
255.255.255.0
gateway 192.168.1.5
dns 192.168.1.5
netbios over tcpip is not listed

PPP adapter
192.168.50.3
255.255.255.255
no gateway listed
dns 192.168.1.1
dns 192.168.1.1
primary wins 192.168.1.1
secondary wins 192.168.1.1
netbios over TCPIP - disabled

------------------------------------------------------------
Windows 7 computer - DHCP
Wifi Adapter
192.168.1.219
255.255.255.0
gateway 192.168.1.5
dhcp 192.168.1.5
dns server 192.168.1.5
netbios over TCPIP - enabled

PPTP
192.168.50.4
255.255.255.255
Gateway 0.0.0.0
DNS 192.168.1.1
primary wins server 192.168.1.1
netbios over tcpip - enabled

"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.

 

[edfair]

for starters, netbios over tcpip.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[goombawaho]

NETBIOS has nothing to do with PINGing by ip address though, right. I'm trying to do VNC, RDP via IP but I can't even get ping to work from the XP machines to the far end of the VPN. Why is it only the XP computers? The Win 7 machines have no problem pinging, VNCing, RDPing.

I tried this: not the answer Link

The thing is, and I know this is not good, the subnets are the same on both sides (192.168.1.x) but there are no IP address conflicts, so I was golden until I got to these XP machines.



"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.

 

[Beilstwh]

Try this

http://answers.microsoft.com/en-us/...e/df2a921d-18e1-4197-a214-08142330f17b?auth=1

Bill
Lead Application Developer
New York State, USA

 

[goombawaho]

That's not the issue or solution. I have zero connectivity to the other side even though the VPN is established. The Windows 7 machines have no problems connecting to a computer via VNC, RDP or getting ping responses back when they establish the VPN connection.

So - just XP is affected. I even took my old XP computer out there and the same thing happened.

"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.

 

[xwb]

Are the machines on the other side of the VPN W7 or XP?

It might be a W7 to XP problem. Have you tried things like
1) changing the encryption on W7 to 40/56 bit (it defaults to 128). W7 to W7 is OK since they are both 128.
2) Change the setting from “Send NTMLv2 response only” to “Send LM & NTLM – use NTLMv2 session if negotiated”
3) HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size Set to 3 (maximize throughput for file sharing and networks)
4) You will also probably need to increase the size of the cache

 

[edfair]

Would be curious if wireshark would see traffic on the far side when you attempt connection or pinging. Of if the traffic is getting corrupted or throttled at the interchange.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[goombawaho]

All PCs on remote end of VPN are all Windows 7 and one Server 2011 Small Business Essentials

Realize that my personal Windows XP computer at my house connected to their VPN can ping all computers no problem. When I took that same XP computer to their office (with the problem XP computers), it did NOT work. So, shouldn't that rule out any of the issues you mentioned?

The real problem on the network is that both of the subnets are 192.168.1.x but then logically the Windows 7 computers should have a problem as well unless there is something different about the routing table between XP and Windows 7 when the VPN is established.

"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.

 

[xwb]

What about the subnet mask? (netsh interface ip show config)
Is it the same on all the machines?

Have you tried playing with tracert

1) From XP at home, see what tracert to the machines on the other side of the VPN returns
2) From W7 on site, see what tracert returns
3) From XP on site, see what tracert returns (this will probably fail)

Are they all returning the same hops?

 

[goombawaho]

I'll try those ideas next time there!! I'll try anything. Right now I'm planning on changing one end of the VPN to a different subnet, but that's going to cause a lot of re-configuring and I'm not even sure that will solve the problem. This customer is dubious about IT people and I need to have all the right answers and nail everything the first time or he will be dubious about me. This issue is killing me right now.

"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.

 

[goombawaho]

So, I changed my HOME network over to the same IP addressing scheme as the network where the XP computers cannot connect, even down to the router IP address. Router = 192.168.1.5. I was able to duplicate the problem exactly. So, if anyone wants to look through the following IPCONFIG /ALL and ROUTE PRINT for both XP and Win 7 PCs and see what might be causing the XP computers to fail communications across the VPN, I would be very grateful. This is over my head!!

XP computer
Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : hsd1.mi.comcast.net.
Description . . . . . . . . . . . : Linksys Wireless-G PCI Network Adapter with SpeedBooster
Physical Address. . . . . . . . . : 00-XX-XX-XX-XX-9A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.5
DHCP Server . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 75.75.76.76
75.75.75.75
Lease Obtained. . . . . . . . . . : Monday, February 01, 2016 2:57:39 PM

Lease Expires . . . . . . . . . . : Tuesday, February 02, 2016 2:57:39 PM


PPP adapter VPN-NAME:

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


C:\Documents and Settings\Owner>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 XX XX XX XX d4 ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
0x3 ...00 XX XX XX XX 9a ...... Linksys Wireless-G PCI Network Adapter with Spee dBooster - Packet Scheduler

Miniport
0x80005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.5 192.168.1.101 26
0.0.0.0 0.0.0.0 192.168.50.3 192.168.50.3 1
50.76.xxx.xx 255.255.255.255 192.168.1.5 192.168.1.101 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 25
192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 25
192.168.50.3 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.50.255 255.255.255.255 192.168.50.3 192.168.50.3 50
224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 25
224.0.0.0 240.0.0.0 192.168.50.3 192.168.50.3 1
255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 1
255.255.255.255 255.255.255.255 192.168.50.3 192.168.50.3 1
255.255.255.255 255.255.255.255 192.168.50.3 2 1
Default Gateway: 192.168.50.3
===========================================================================



=================================================================================================================
Windows 7 computer -

PPP adapter VPN-NAME:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VPN-NAME
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.50.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : hsd1.mi.comcast.net.
Description . . . . . . . . . . . : Qualcomm Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller
Physical Address. . . . . . . . . : C8-XX-XX-XX-XX-FE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, February 01, 2016 2:31:37 PM
Lease Expires . . . . . . . . . . : Tuesday, February 02, 2016 2:31:37 PM
Default Gateway . . . . . . . . . : 192.168.1.5
DHCP Server . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 75.75.76.76
75.75.75.75
NetBIOS over Tcpip. . . . . . . . : Enabled


C:\Users\Bubba>tracert 192.168.1.52

Tracing route to OFFICEMGR [192.168.1.52]
over a maximum of 30 hops:

1 21 ms 18 ms 18 ms router.asus.com [192.168.1.1]
2 20 ms 18 ms 21 ms OFFICEMGR [192.168.1.52]



C:\Users\Bubba>route print
===========================================================================
Interface List
21...........................VPN-NAME
11...c8 XX XX XX XX fe ......Qualcomm Atheros AR8161/8165 PCI-E Gigabit Ethernt Controller
1...........................Software Loopback Interface 1
14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.5 192.168.1.100 4245
0.0.0.0 0.0.0.0 On-link 192.168.50.2 21
50.76.xxx.xx 255.255.255.255 192.168.1.5 192.168.1.100 4246
127.0.0.0 255.0.0.0 On-link 127.0.0.1 4531
127.0.0.1 255.255.255.255 On-link 127.0.0.1 4531
127.255.255.255 255.255.255.255 On-link 127.0.0.1 4531
192.168.1.0 255.255.255.0 On-link 192.168.1.100 4501
192.168.1.100 255.255.255.255 On-link 192.168.1.100 4501
192.168.1.255 255.255.255.255 On-link 192.168.1.100 4501
192.168.50.2 255.255.255.255 On-link 192.168.50.2 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 4531
224.0.0.0 240.0.0.0 On-link 192.168.1.100 4502
224.0.0.0 240.0.0.0 On-link 192.168.50.2 21
255.255.255.255 255.255.255.255 On-link 127.0.0.1 4531
255.255.255.255 255.255.255.255 On-link 192.168.1.100 4501
255.255.255.255 255.255.255.255 On-link 192.168.50.2 276





"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.

 

[rclarke250]

on the xp is that right? under vpn it says gateway 192.168.50.3 and on the win 7 machines it is 0.0.0.0? also the dns on the xp vpn has 192.168.1.51? but the win 7 dns is 192.168.1.1?

 

[goombawaho]

I screwed up. I had been experimenting and forgot to set things back. I guess I'll have to replicate the situation again and get the corrected output. The 192.168.1.51 was the "experimentation" mistake.

"Living tomorrow is everyone's sorrow.
Modern man's daydreams have turned into nightmares.