VPN problem

  • Thread starter Thread starter hm
  • Start date Start date
H

hm

I have created a VPN server to accept incoming connections in Vista
Business, also set routing and remote access service to automatic. But when
I am trying to connect from a client (Vista Business) computer I am getting
"Registering your computer on the network, Registered". and the Media State
shows Connected, but IPv4 connectivity says Limited. I have configured the
server to give IP address in 192.168.0.x range and the client gets
192.168.0.2.

I am able to ping 192.168.0.2 from the client but unable to ping 192.168.0.1
from the client with firewall disabled.
The sent bytes counter increases but the received reaches around 330 and
then doesn't increase.

Any solution is appreciated
 
Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

PPP adapter VPN Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VPN Connection
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-09-43-5F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::fd2c:b704:ace0:2109%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.61(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 202.62.224.2
202.62.224.9
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.2%15(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{BFC3A549-CB63-4932-9BB3-072E9BCFE
450}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.61%14(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 202.62.224.2
202.62.224.9
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4136:e388:407:252e:3f57:fec2(Prefe
rred)
Link-local IPv6 Address . . . . . :
fe80::407:252e:3f57:fec2%11(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
 
Assuming VPN server IP is 192.168.0.1 and client is 192.168.0.2, do you have
firewall on VPN server to block ping? Or use tracert command to find out
where the traffic go.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
 
The firewall is disabled but there is no communication between the computers
though both of them can access the wireless network. The 192.168.0.x range
IPs are assigned by DHCP but there seems to be some problem with the TCP.
Tracert says destination host not reachable.
 
Back
Top