1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Setting up RV016 as PPTP server, cannot see network machines

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by crackers8199, Jul 23, 2007.

  1. crackers8199

    crackers8199 LI Guru Member

    created myself a username, can connect to the router from home via the XP VPN client - however, while i can see and ping the main router and can access the router's web utility thru http://192.168.1.1, i cannot see or ping any of the other computers on the network.

    where should i be looking for problems? the vpn connection assigns me 192.168.1.201.
     
  2. ifican

    ifican Network Guru Member

    Firewall on the hosts that you are trying to connect too.
     
  3. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Are you looking for or pinging other PCs using IP address or netbios names? Just use their IP address.
     
  4. crackers8199

    crackers8199 LI Guru Member

    Firewall is turned off on the machine I'm trying to access.

    Also, I'm using IP addresses not names...still nothing. Cannot ping.

    The only other thing I can think of is that my home network is running MSHOME as the workgroup, my work network workgroup is the company name...would that cause a problem?
     
  5. crackers8199

    crackers8199 LI Guru Member

    A few other things:

    - I can still access the other machines on my home network, but none of the machines on the work network

    - as was mentioned, home workgroup is MSHOME while work workgroup is the company name

    - both are using 192.168.1.xxx

    - home network is using ipx/spx/netbios for file/printer sharing, while work network is using tcp/ip (although binding tcp/ip on the home machine to file/print sharing didn't work either)
     
  6. ifican

    ifican Network Guru Member

    You need to have each network on a different ip range, Im surprised it even connects. Since you have no control over your work ip range, change your home range and you should be good to go.
     
  7. t4thfavor

    t4thfavor Network Guru Member

    Exactly, change your ip range to 192.168.x.yyy where x is not eaqual to 1.
     
  8. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Workgroup name means absolutely nothing. People often thing because computers are in different workgroups, that they cannot access each other. Not true at all, workgroups are just a visual organization. You can still access PCs in different workgroups by drilling up, across, and down another layer in network places. Or the easier method..start==>Run ==> \\computername\sharename or \\ipaddress\sharename

    Networks that I have VPN tunnels with...I always keep them on separate IP addresses. Many home users run on a 192.168.0.xxx or 192.168.1.xxx network...so I"ll usually make the office network something like 192.168.10.xxx. Various VPN setups don't like having the same IP range on each side...as the router may not know which way to go!
     
  9. crackers8199

    crackers8199 LI Guru Member

    OK, actually got the office network changed to 192.168.0.xxx. Still able to connect from home, still able to see the router, still not able to see anything else on the work network from home...are there any other settings I should be checking?
     
  10. crackers8199

    crackers8199 LI Guru Member

    an interesting development - i am now able to RDP and access network shares across the vpn connection. however, i cannot ping the machines on either side of the network from the other side. what gives with that?
     
  11. Toxic

    Toxic Administrator Staff Member

    can you ping the remote PCs from the router? (diagnostics page)
     
  12. crackers8199

    crackers8199 LI Guru Member

    Using 192.168.0.195 (the IP that the PPTP server assigned it), yes I can ping that from the router's diagnostic page...I cannot from within windows.

    Also, an interesting note -- while I can see the files via file sharing, I cannot seem to RDP in from remote to a computer on the office network...
     
  13. Toxic

    Toxic Administrator Staff Member

    you need to be on the same subnet as the local machines. is PPTP server assigning the remote pc an IP address within the same subnet as the LAN PCs?
     
  14. crackers8199

    crackers8199 LI Guru Member

    Yup...assigning in the 192.168.0.195-204 range.
     
  15. crackers8199

    crackers8199 LI Guru Member

    anyone? can see the network shares for machines on the LAN side and transfer files, but cannot ping or RDP to any of them...

    however, i can rdp out from the lan side to a remote machine that is connected via vpn
     
  16. crackers8199

    crackers8199 LI Guru Member

  17. ifican

    ifican Network Guru Member

    Ok lay down the specifics again. From what i get from this you are creating a pptp tunnel from a home machine to work and getting an ip on the home machine of 0.x as you are suppose too. Now from what machines are you trying to do all of the access on and too? The machine that is terminating the tunnel should have access to your work, however no other machine on your network is going to have the same access or vice versa.
     
  18. crackers8199

    crackers8199 LI Guru Member

    Sorry for taking so long to reply, was on vacation...

    - Anyway, creating a PPTP tunnel from home to office, yes
    - Using the XP VPN client
    - RV016 acting as the PPTP server (office router)
    - connects just fine, am assigned an IP in the range of 192.168.0.195-192.168.0.204 by the RV016

    It's at this point that the oddities start...

    - CAN see both home and office machines via Windows network file sharing
    - CAN use RDP to connect from office machine to the home machine that is connected via VPN
    - CAN ping the home machine connected via VPN from the office machines (using the 192.168.0.19x IP address)

    - CANNOT ping any of the office machines from the home machine that is connected via VPN
    - CANNOT use RDP to connect to any of the office machines from the home machine that is connected via VPN

    My goal is to turn the two CANNOTs into CANs, while keeping everything else the same.
     
  19. crackers8199

    crackers8199 LI Guru Member

    OK, now I CANNOT (just today) ping the home machine that is connected via VPN from within the office...
     
  20. crackers8199

    crackers8199 LI Guru Member

  21. ifican

    ifican Network Guru Member

    Any changes? And what is the subnet mask of the home machine that has created the tunnel? Also the subnet mask of the internal network, I am assuming as toxic mentioned earlier that they are all the same and on the same network internal and pptp machines?
     
  22. crackers8199

    crackers8199 LI Guru Member

    subnet mask for both home and office is 255.255.255.0

    office machines are on 192.168.0.xxx
    home machines are 192.168.1.xxx
     
  23. ifican

    ifican Network Guru Member

    Actually i was not clear what is the subnet mask that is given via the pptp tunnel? When the home machine logs into the server it is given an address and mask in the 192.168.0.x network what is that? And and change since your last post?
     
  24. crackers8199

    crackers8199 LI Guru Member

    OK, just connected and here's what I've got for the PPP adapter for the VPN:

    IP Address: 192.168.0.196
    Subnet Mask: 255.255.255.255
    Default Gateway: (blank)
    DNS Servers: 192.168.0.1

    No changes made since last post...
     
  25. ifican

    ifican Network Guru Member

    And at this point you are still seeing the same functionality as expressed in previos posts?
     
  26. crackers8199

    crackers8199 LI Guru Member

    Yes, except that now I CANNOT ping from the internal machine to the home one...file sharing still works, just no ping and no RDP.
     
  27. ifican

    ifican Network Guru Member

    You know at this point i would put ethereal or wireshark on the work machine and watch what is happening when you send out ping and rdp traffic. Once you have a better idea at exactly what is going on we can better figure out how to fix it.
     
  28. Toxic

    Toxic Administrator Staff Member

    Is Remote Access on all the Office PCs enabled? can you RDC from one Office PC to another Office PC? can you Ping from one office PC to another Office PC?
     
  29. crackers8199

    crackers8199 LI Guru Member

    It is on the ones we need to connect to via RDP (certain machines don't need this ability)...

    Yes.

    Yes.
     
  30. crackers8199

    crackers8199 LI Guru Member

    I already have ethereal installed, but not quite sure how to use it. What do you need me to do? I'll post whatever results necessary, this is really frustrating...
     
  31. crackers8199

    crackers8199 LI Guru Member

  32. Witchaven

    Witchaven LI Guru Member

    I think part of the trouble you are having might be due to the fact that you don't have a gateway assigned along with that narrow subnet mask when you connect to the VPN.

    Can you connect again via the VPN, then go to a DOS prompt and run the command ROUTE PRINT and post the results. This should indicate if your PC has a proper route defined, to reach the work subnet.
     
  33. crackers8199

    crackers8199 LI Guru Member

    Code:
    ===========================================================================
    Interface List
    0x1 ........................... MS TCP Loopback interface
    0x2 ...00 16 76 df 74 bc ...... Intel(R) 82562V 10/100 Network Connection - Packet Scheduler Miniport
    0x20004 ...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.1   192.168.1.100	  20
          74.94.35.29  255.255.255.255      192.168.1.1   192.168.1.100	  20
            127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1	  1
          192.168.0.0    255.255.255.0    192.168.0.195   192.168.0.195	  1
        192.168.0.195  255.255.255.255        127.0.0.1       127.0.0.1	  50
        192.168.0.255  255.255.255.255    192.168.0.195   192.168.0.195	  50
          192.168.1.0    255.255.255.0    192.168.1.100   192.168.1.100	  20
        192.168.1.100  255.255.255.255        127.0.0.1       127.0.0.1	  20
        192.168.1.255  255.255.255.255    192.168.1.100   192.168.1.100	  20
            224.0.0.0        240.0.0.0    192.168.0.195   192.168.0.195	  50
            224.0.0.0        240.0.0.0    192.168.1.100   192.168.1.100	  20
      255.255.255.255  255.255.255.255    192.168.0.195   192.168.0.195	  1
      255.255.255.255  255.255.255.255    192.168.1.100   192.168.1.100	  1
    Default Gateway:       192.168.1.1
    ===========================================================================
    Persistent Routes:
      None
    
     
  34. Witchaven

    Witchaven LI Guru Member

    Ok, even though you were not assigned a default gateway for the work network, it looks like there is a route there for 192.168.0.x network. So it looks like the routing table on your PC is fine.

    Unfortunately, I don't have access to an RV016 so can't test this further.
     
  35. DocLarge

    DocLarge Super Moderator Staff Member Member

    Okay,

    at this point, "too many" adjustments have been made. I'd say "strip it all down" meaning erase whatever configuration you have running after office hours and start all over again and "document" your settings. After having read this thread, you've got a wildcard setting somewhere that's restricting access (that's my guess) but it'd be of benefit to take this act from the top once more... :)

    Jay
     
  36. crackers8199

    crackers8199 LI Guru Member

    I don't understand what you mean by "erase whatever configurations you have made"...the router is basically stock, I haven't made any config changes really.
     
  37. DocLarge

    DocLarge Super Moderator Staff Member Member

    Let's get some info first...

    1) What type of modem connection (i.e., dsl, cable) do you have at home and at work?
    2) What type of routers do you have at home and at work?
    3) What is your LAN ip segment behind the router at work and the one behind your router at home?
    4) Are your connections at work and at home dynamic or static? (Gee whiz stuff that sometimes causes problems)
    5) Do you have systems at home and at work running software firewalls? If so, what brand are they?
    6) What are the MTU settings on both of your routers?

    This type of info is good for establishing a baseline to work from...

    Jay
     
  38. crackers8199

    crackers8199 LI Guru Member

    1) cable on both ends (actually, comcast on both ends)

    2) rv016 at the office, linksys befsr41 at home

    3) work: 192.168.0.xxx, home: 192.168.1.xxx

    4) work is static, home is dynamic

    5) no software firewalls that i know of on either end...windows xp firewalls are turned off

    6) default on both (1500 i believe)
     
  39. ccb056

    ccb056 Network Guru Member

    Is there a space in the PPTP username?

    If there is, thats whats screwing everything up, there is a bug in the RV042 RV082 and RV016 thats breaks PPTP when you have spaces in usernames.
     
  40. crackers8199

    crackers8199 LI Guru Member

    there is a . in the username, but i doubt that's causing an issue - when you say "breaks" PPTP, it sounds like you mean all traffic. i'm able to connect to the router and see all the machines on the inside through windows file sharing, just can't ping or rdp

    i can ping the router, but none of the internal machines

    on edit: confirmed this is not the issue - changed the username to include only letters and still the same problem
     
  41. cfinic

    cfinic LI Guru Member

  42. crackers8199

    crackers8199 LI Guru Member



    I'm still not sure I understand - all you did was reset the DSL modem to fix this? How exactly could that help? Which end did you need to reset, the one connected to the RV016 or the one you're connecting in from?
     
  43. cfinic

    cfinic LI Guru Member

    Well it seems to be intermittent, but what I did was setup the network as such

    Work: 10.x.x.x
    Home: 192.168.x.x

    I seem to be able to access my shares, but I'm still doing some testing. You might want to try that and see if it solves your issue.
     
  44. crackers8199

    crackers8199 LI Guru Member

    weird thing is that i can now see my shares again, but i still can't ping or rdp. i'm wondering if there's a route missing somewhere.

    a quick glance at the route print output from xp shows no route to 192.168.0.0 (there is however one to 192.168.0.196, which is the ip address i'm given on the vpn, using the loopback interface)...
     
  45. crackers8199

    crackers8199 LI Guru Member

    dooby dooby doo...anyone home?
     

Share This Page