Home All Groups Group Topic Archive Search About
Author
31 Jul 2006 5:57 PM
bkboudreau
Hello everyone,

Here is an interesting delema I am facing.  I am running a VPN server
on a windows XP Pro box which is sitting behind my linksys WRT54GL
router.  I have all the needed ports forwarded and people can connect
to my VPN and get a valid IP (192.168.1.160-170).  The VPN server shows



on the .160 address.  I have one friend that when connected we can't
ping each other.  He is behind a linksys BEFSX41 v2 router.  Then I
have another friend who is not behind any router and when they are
connected, they can ping me but I can't ping them.  They have the
windows firewall turned off and have no other firewall software to
their knowledge.


Here are the ipconfig /all results from both the VPN server and the
friend who can ping me but whom I cannot ping:


Server:


PPP adapter RAS Server (Dial In) Interface:


        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Internal RAS Server
interface for dial in clients
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.160
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . :


Ethernet adapter INET:


        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : SiS 900-Based PCI Fast
Ethernet Adapter
        Physical Address. . . . . . . . . : 00-E0-18-74-E0-39
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.200
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.5
                                                    192.168.1.1


Client:


Windows IP Configuration


        Host Name . . . . . . . . . . . . : *****
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Local Area Connection:


        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
        Physical Address. . . . . . . . . :


Ethernet adapter Local Area Connection 2:


        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Marvell Yukon Gigabit
Ethernet 10/100/1000Base-T Adapter, Copper RJ-45
        Physical Address. . . . . . . . . :
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 24.231.81.38
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 24.231.81.1
        DHCP Server . . . . . . . . . . . : 24.139.0.21
        DNS Servers . . . . . . . . . . . : 216.104.96.18
                                                   216.104.96.19
                                                   216.104.96.10
        Lease Obtained. . . . . . . . . . : Thursday, July 27, 2006
7:25:04 PM
        Lease Expires . . . . . . . . . . : Saturday, July 29, 2006
5:31:37 PM


PPP adapter RoB:


        Connection-specific DNS Suffix  . :


        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.161
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . : 192.168.1.161
        DNS Servers . . . . . . . . . . . : 192.168.1.5
                                                    192.168.1.1


I just tested again and they can ping and connect to shares on my
network but I can't ping them.  They is not behind a firewall and is
connected directly to the internet.  As for my other friend, I believe
that his router is stopping the traffic along the VPN since if he moves

his PC directly to the internet we can communicated using the VPN but
when he goes back behind the router we can't ping eachother.  If anyone

can help with either/both of these issues I would really appreciate it.

Author
31 Jul 2006 6:11 PM
Robert L [MS-MVP]
In the client 192.168.1.161, can your friend ping itself? also use the tracert command to check where is 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
  "bkboudreau" <bra***@shaw.ca> wrote in message news:1154368646.848807.136390@p79g2000cwp.googlegroups.com...
  Hello everyone,

  Here is an interesting delema I am facing.  I am running a VPN server
  on a windows XP Pro box which is sitting behind my linksys WRT54GL
  router.  I have all the needed ports forwarded and people can connect
  to my VPN and get a valid IP (192.168.1.160-170).  The VPN server shows



  on the .160 address.  I have one friend that when connected we can't
  ping each other.  He is behind a linksys BEFSX41 v2 router.  Then I
  have another friend who is not behind any router and when they are
  connected, they can ping me but I can't ping them.  They have the
  windows firewall turned off and have no other firewall software to
  their knowledge.


  Here are the ipconfig /all results from both the VPN server and the
  friend who can ping me but whom I cannot ping:


  Server:


  PPP adapter RAS Server (Dial In) Interface:


          Connection-specific DNS Suffix  . :
          Description . . . . . . . . . . . : Internal RAS Server
  interface for dial in clients
          Dhcp Enabled. . . . . . . . . . . : No
          IP Address. . . . . . . . . . . . : 192.168.1.160
          Subnet Mask . . . . . . . . . . . : 255.255.255.255
          Default Gateway . . . . . . . . . :


  Ethernet adapter INET:


          Connection-specific DNS Suffix  . :
          Description . . . . . . . . . . . : SiS 900-Based PCI Fast
  Ethernet Adapter
          Physical Address. . . . . . . . . : 00-E0-18-74-E0-39
          Dhcp Enabled. . . . . . . . . . . : No
          IP Address. . . . . . . . . . . . : 192.168.1.200
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . . . . : 192.168.1.1
          DNS Servers . . . . . . . . . . . : 192.168.1.5
                                                      192.168.1.1


  Client:


  Windows IP Configuration


          Host Name . . . . . . . . . . . . : *****
          Primary Dns Suffix  . . . . . . . :
          Node Type . . . . . . . . . . . . : Unknown
          IP Routing Enabled. . . . . . . . : No
          WINS Proxy Enabled. . . . . . . . : No


  Ethernet adapter Local Area Connection:


          Media State . . . . . . . . . . . : Media disconnected
          Description . . . . . . . . . . . : NVIDIA nForce Networking
  Controller
          Physical Address. . . . . . . . . :


  Ethernet adapter Local Area Connection 2:


          Connection-specific DNS Suffix  . :
          Description . . . . . . . . . . . : Marvell Yukon Gigabit
  Ethernet 10/100/1000Base-T Adapter, Copper RJ-45
          Physical Address. . . . . . . . . :
          Dhcp Enabled. . . . . . . . . . . : Yes
          Autoconfiguration Enabled . . . . : Yes
          IP Address. . . . . . . . . . . . : 24.231.81.38
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . . . . : 24.231.81.1
          DHCP Server . . . . . . . . . . . : 24.139.0.21
          DNS Servers . . . . . . . . . . . : 216.104.96.18
                                                     216.104.96.19
                                                     216.104.96.10
          Lease Obtained. . . . . . . . . . : Thursday, July 27, 2006
  7:25:04 PM
          Lease Expires . . . . . . . . . . : Saturday, July 29, 2006
  5:31:37 PM


  PPP adapter RoB:


          Connection-specific DNS Suffix  . :


          Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
          Physical Address. . . . . . . . . : 00-53-45-00-00-00
          Dhcp Enabled. . . . . . . . . . . : No
          IP Address. . . . . . . . . . . . : 192.168.1.161
          Subnet Mask . . . . . . . . . . . : 255.255.255.255
          Default Gateway . . . . . . . . . : 192.168.1.161
          DNS Servers . . . . . . . . . . . : 192.168.1.5
                                                      192.168.1.1


  I just tested again and they can ping and connect to shares on my
  network but I can't ping them.  They is not behind a firewall and is
  connected directly to the internet.  As for my other friend, I believe
  that his router is stopping the traffic along the VPN since if he moves

  his PC directly to the internet we can communicated using the VPN but
  when he goes back behind the router we can't ping eachother.  If anyone

  can help with either/both of these issues I would really appreciate it.
Author
1 Aug 2006 3:34 AM
Quaoar
Robert L [MS-MVP] wrote:
> In the client 192.168.1.161, can your friend ping itself? also use the
> tracert command to check where is traffic go.

Robert - your message font size is about 6 points (or possibly even
smaller), making your responses very difficult to read.

Q
Author
1 Aug 2006 3:57 AM
Robert L [MS-MVP]
Thanks

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
  "Quaoar" <qua***@tenthplanet.net> wrote in message news:%23nysntRtGHA.1216@TK2MSFTNGP03.phx.gbl...
  Robert L [MS-MVP] wrote:
  > In the client 192.168.1.161, can your friend ping itself? also use the
  > tracert command to check where is traffic go.

  Robert - your message font size is about 6 points (or possibly even
  smaller), making your responses very difficult to read.

  Q