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

VPN Client not listed on DHCP Client Table, but is "Onl

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by HercNav, Apr 1, 2006.

  1. HercNav

    HercNav LI Guru Member

    (Linksys' latest non-beta Firmware to date: 2.37.1)

    I have a VPN Client that is successfully logging on to my WRV54G, but none of my shared resources are showing up in his Network Neighborhood (we're both using MSHOME).

    Using my WRV54G Diagnostics, I can ping the wireless router/modem that he uses to connect to the internet. Of course the IP address assigned to his network adapter (Local Area Connection) was unreachable.

    Although I don't think it's necessary, I had him setup Norton (the only active firewall) to accept an IP range for the WRV54G's local secure workgroup. Should I be using a different value?

    Although it's usually the default setting, I'm having him make sure that his router has IPSec Pass-through enabled in the morning.

    I saw a reference to shutting off the WRV54G's DHCP server, but how would this affect his QuickVPN? I thought that was how QuickVPN was assigned a local address, thus enabling it to work & play among the resources behind the WRV54G. Besides, when I tried that, the computer I was using behind the WRV54G no longer connected to the internet....

    How would a VPN client go about mapping resources without being able to see them in the Network Neighborhood?
     
  2. TazUk

    TazUk Network Guru Member

    Re: VPN Client not listed on DHCP Client Table, but is &quot

    Nope that should be it.

    Shouldn't make a difference as your not passing IPSEC through the WRV54G it's handling the IPSEC packets itself.

    No idea, mines always been on and both site to site and client to site VPN's work fine. Where did you see this mentioned?

    Can you access them by IP address, if so then add them to the PC's LMHOSTS file.
     
  3. HercNav

    HercNav LI Guru Member

    I see DocLarge promoting it in places such as this:
    http://www.dslreports.com/forum/remark,15406503
     
  4. TazUk

    TazUk Network Guru Member

    Can't see any reference to disabling DHCP in that thread :unsure:
     
  5. HercNav

    HercNav LI Guru Member

  6. HercNav

    HercNav LI Guru Member

    Also, please explain this process:

     
  7. TazUk

    TazUk Network Guru Member

    The LMHOSTS file resides in C:\Windows\System32\Drivers\Etc for XP or C:\WinNT\System32\Drivers\Etc for NT/2000. The format for it is similar to the HOSTS file i.e. ip_address space machine_name but there are some additional parameters such as #PRE to preload the entry into the cache and #DOM:domain_name to specify the domain. If the PC you want to connect to has an IP address of 192.168.1.100 and is called BobsPC then the entry would look like this :-

    192.168.1.100 BobsPC #PRE

    When you try and access BobsPC Windows will look in the LMHOSTS file for an entry, if one is found it will use that instead of resorting to WINS, broadcasts etc.

    Once you've created/edited the LMHOSTs file you either have to reboot the PC or use the NBTSTAT -R command to referesh the cache.
     
  8. HercNav

    HercNav LI Guru Member

    How do you open a *.SAM?

    I can ping computers behind the remote VPN, but I can't pull up their shares from explorer....
     
  9. russwmc

    russwmc Network Guru Member

    Copy the lmhosts.sam file to just lmhosts in the same directory.

    Then edit the lmhosts file with notepad

    Save it.

    You're done.

    I typically just use the hosts file instead of lmhosts and get the same results, for the most part.
     

Share This Page