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

WRV54G and QuickVPN, it connects but can't see my network

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by PDaddy, Apr 20, 2005.

  1. PDaddy

    PDaddy Network Guru Member

    Hello everyone,

    I am very new at VPN and what a way to start out on the WRV54G. It’s probably not the router someone should try and learn from with all its problems but I am glutting for punishment I guess. After reading everything I could in this forum regarding the WRV54G I was successful in getting the QuickVPN to connect from my home computer to the office network (using DSL type internet services on both ends). The WRV54G is at the office which has no server, just a workgroup of 10 computers. When QuickVPN is connected I can ping every computer on my office network (all have static IP’s) from home. The problem is I can’t see my office network from my home computer under “My Network Places†of explore. I assume that this is where shared files, folders, and printers from my office network would show up through the VPN tunnel, but there is nothing other than my homes local network which consists of 3 computers behind an older linksys BEFW11S4 router. Any ideas why I can log onto my work computer using QuickVPN and ping the individual office computers but can’t see their shared files, folders, and printers? BTW, I have the latest Firmware 2.37. I was able to get QuickVPN to connect after putting in a fictitious name in the “Domain Name†box on the Basic Setup screen.

    Thanks for any input
     
  2. ipcdmatt

    ipcdmatt Network Guru Member

    Im new at this too but just for starters, ... the two workgroups need to advertise to each other across the span.

    Despite the two networks within arms reach and pingable, .. thats just because the two subnets are routed between each other.

    But Windows on each side knows nothing of the other goup mutually.

    Within each of your workgroups , the NETBIOS is typically responsible for advertising computer names, mappings, etc, ... but NETBIOS is non-routable unless you explicitly enable it , like NETBIOS over TCP optioning on both ends.


    Or you can explore using a WINS server, or using STATIC associations via LMHOSTS (Allright for small networks).

    If you google these it should shed more light on it.
     
  3. PDaddy

    PDaddy Network Guru Member

    Matt, thanks for the reply. I was able to see the network if I use the office machines local IP address, so I think you’re on the right track. I will put google to work and get more info regarding NETBIOS. So does it kind of do the same thing as DNS and does a server usually do this job? Thanks for the input and I will let you know what I find out. Thanks again!
     
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Ideally, by configuring the host file on one computer that has information regarding the other computers in your workgroup (i.e., ip address, netbios name) you can copy that file to all of the computers thus aiding in recognition on the network because they'll all know where each other resides. The best implementation of this would be through a wins server...
     

Share This Page