W7 VPN connected but cannot access network or map network drive

Page 8 of 10 FirstFirst ... 678910 LastLast

  1. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #71

    I have only added the one route that I listed in my reply 3 hours ago
    Destination IP Address: 192.168.11.22
    Subnet Mask:255.255.255.0
    Gateway: 192.168.1.67
    Interface: LAN
    What is 192.168.11.22? why 192.168.11.22? It must be 192.168.11.21
      My Computer


  2. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #72

    On remote side pc (any other than vpn server): that computer has tcpip address 192.168.1.* for example 192.168.1.50
    Please do on that computer:
    Code:
    tracert  192.168.11.21
    Post output. The traffic should go to 192.168.1.1, then 192.168.1.67, then 192.168.11.21

    That proves remote server's ip subnet can access the vpn-tunnel
      My Computer


  3. Posts : 181
    64 bit Win 7 Ultimate
    Thread Starter
       #73

    VPN connected. Use gateway on remote host ticked.
    Access to server fine.


    On another PC on same LAN as server

    C:\Documents and Settings\Rincewind>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : DEAN-M5
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Broadcast
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Wireless Network Connection 2:

    Media State . . . . . . . . . . . : Media disconnected
    Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
    k Connection
    Physical Address. . . . . . . . . : 00-13-02-1C-05-33

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connect
    ion
    Physical Address. . . . . . . . . : 00-0E-7B-43-F8-78
    Dhcp Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.1.69
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 192.168.1.1

    C:\Documents and Settings\Rincewind>ping 192.168.11.21

    Pinging 192.168.11.21 with 32 bytes of data:

    Reply from 192.168.11.21: bytes=32 time=1ms TTL=127
    Reply from 192.168.11.21: bytes=32 time<1ms TTL=127
    Reply from 192.168.11.21: bytes=32 time=1ms TTL=127
    Reply from 192.168.11.21: bytes=32 time<1ms TTL=127

    Ping statistics for 192.168.11.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

    C:\Documents and Settings\Rincewind>tracert 192.168.11.21

    Tracing route to 192.168.11.21 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 * * * Request timed out.
    3 1 ms <1 ms <1 ms 192.168.11.21

    Trace complete.




    I've lost the plot here and am rapidly losing the will to live!!!

    BTW your #71 asked "Why 192.168.11.22
    Because to asked me to in #53!!
    I can change it if required?
      My Computer


  4. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #74

    Wow!! 192.168.1.69 (a computer on same LAN as server) can ping the vpn tunnel 192.168.11.21 . You can see the tracert output that it goes to the remote router 192.168.1.1 and then a timeout (must be 192.168.1.67 not responding temporary for a reason) then vpn tunnel. Tunnel responses back... so knows the route back as well.

    Can client ping 192.168.1.1 ? if not... tracert 192.168.1.1
    Can client ping 198.211.122.92?
    Can client ping kaktussoft.nl?

    192.168.11.22 doesn't even exist... was a typo!
      My Computer


  5. Posts : 181
    64 bit Win 7 Ultimate
    Thread Starter
       #75

    Yes to all of these (going via VPN tunnel and gateway on remote server)


    192.168.11.22 doesn't even exist... was a typo!
    So should I change this route in the router to .11.21?
      My Computer


  6. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #76

    On vpn-client: tracert 198.211.122.92 . Does it go through 192.168.1.1 (so remote router)? It first goes throus 192.168.11.21 the vpn tunnel

    hopefully for the last time. Post route -4 print output from server and client. And post a screenshot of the static route you created on the remote router
      My Computer


  7. Posts : 181
    64 bit Win 7 Ultimate
    Thread Starter
       #77

    On vpn-client: tracert 198.211.122.92 . Does it go through 192.168.1.1 (so remote router)? It first goes throus 192.168.11.21 the vpn tunnel
    YES
    C:\Users\Rincewind>tracert 198.211.122.92

    Tracing route to 198.211.122.92 over a maximum of 30 hops

    1 30 ms 32 ms 33 ms PONDER [192.168.11.21]
    2 31 ms 63 ms 30 ms 192.168.1.1
    3 * * * Request timed out.
    4 115 ms 115 ms 56 ms ip-84-38-37-52.easynet.co.uk [84.38.37.52]
    5 146 ms 150 ms 60 ms ae-1.r00.londen01.uk.bb.gin.ntt.net [83.231.199.161]
    6 282 ms 340 ms * ae-6.r02.londen03.uk.bb.gin.ntt.net [129.250.3.2]
    7 64 ms 72 ms 60 ms ae-4.r23.londen03.uk.bb.gin.ntt.net [129.250.5.40]
    8 77 ms 66 ms 73 ms ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.198]
    9 66 ms 67 ms 62 ms 198.211.122.92

    Trace complete.


    The timeout is where it has a go via .67? (before popping off to easynet)
    Why would it go to .67 after hittitng .1.1 (the router)?


    hopefully for the last time. Post route -4 print output from server



    and client.


    And post a screenshot of the static route you created on the remote router

    is the only route I have created in response to your #53

    So it was the .21 that was the typo, not the .22?
    Should I leave this / Change this / Delete This route?
      My Computer


  8. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #78

    the screenshot on router: 192.168.11.22/255.255.255.0 means 192.168.11.* so also 192.168.11.21. No need to change
    --------------------------------
    Client throws all traffic except 192.168.0.* to the vp tunnel! Great! No static routes needed at all
    Router on Server side knows where vpn tunnel is.... great. Even if it was possible to have more 19.168.11.* tunnels.

    On server: nslookup
    Post screenshot.
    On server: ping -a 192.168.1.69 (so ping the other comoputer on server side)
    Post screenshot.

    What is NOT working?
      My Computer


  9. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #79

    The timeout is where it has a go via .67? (before popping off to easynet)
    Why would it go to .67 after hittitng .1.1 (the router)?
    My fault...
      My Computer


  10. Posts : 181
    64 bit Win 7 Ultimate
    Thread Starter
       #80

    Well I think the whole VPN thing is working as well as it can. Thank you for you perseverance.

    the screenshot on router: 192.168.11.22/255.255.255.0 means 192.168.11.* so also 192.168.11.21. No need to change
    Oh I just hate this sort of thing. WHY does 192.168.11.22 mean 192.168.11.*?
    Why do you not enter 192.168.11.* if that is what you want?
    And why is 255.255.255.0 significant? - or is this too difficult?!
    Last edited by Rincewindwiz; 12 Mar 2014 at 17:29. Reason: Update
      My Computer


 
Page 8 of 10 FirstFirst ... 678910 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:49.
Find Us