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

VPN File Sharing Problems

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by compdocs, May 26, 2006.

  1. compdocs

    compdocs LI Guru Member

    I am setting up an RV042 router in a warehouse which is directly connected to my DSL modem, with a STATIC IP. A switch is connected to my RV042, which currently has one lonely workstation on the other end.

    I am trying to establish a VPN connection into the RV042 from a remote location in an attempt to have central access to a Quickbooks database.

    The RV042 has the most up to date firmware. I am trying to connect using PPTP using Windows clients. I have configured both PPTP clients and VPN Client Access for QuickVPN.

    I am able to establish a connection using BOTH, PPTP & QuickVPN. I am able to ping both sides of my network, FROM both sides of my network. . .including routers, workstations, etc.

    My problem rests with me not being able to connect to any of my shared files on any computer attached to the network., in either direction. I have disabled ALL firewalls, including Windows firewalls, and router firewalls on both sides.

    Quick notes:

    - Different subnets on each side (192.168.1.x & 192.168.2.1)

    - QuickVPN & PPTP connections establish perfectly

    - Able to ping workstations from both ways, to both ways

    - All firewalls disabled

    - Latest & Greatest firmware (1.3.7.4)

    Hopefully someone has some advice for this dilemma!
     
  2. TazUk

    TazUk Network Guru Member

    Does accessing it via it's IP not work, i.e. \\192.168.1.100\share_name ?
     
  3. compdocs

    compdocs LI Guru Member

    It's crazy that you responded so quickly. . . .and what's crazier, is that I have been trying to access it in that fashion this whole time, and now. . . it just worked. I have no idea why. . . how frustrating, yet relieving is that?
     
  4. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Don't rely on netbios names. If you NEED to use netbios name..you can edit your host file, but if you need to access a share on a PC, when doing VPNs..without a DNS server or WINS server to resolve netbios names across networks...well...lets just say netbios with peer to peer networks (no domain controller) takes some work.

    instead...just use IP addresses. Click on Start==>Run \\192.168.1.11\quicken

    where you'd substitute the IP address of your Quicken host machine in there...and assuming you shared out the Quicken folder under that name.

    However...next point...you'll find most programs run agonizingly slow through a skinny VPN connection. Quicken will corrupt on you over time with that thin of a connection also. Tis much better to use remote desktop. Hopefully you host computer is Windows XP professional. If not..and if you plan on remoting in often..I highly recommend you spend the hundge something and upgrade your OS to XP Pro.

    Various flavors of VNC, my favorite is UltraVNC, will work for light use...but the keystrokes lag is quite a bit more..Remote Desktop Connection in XP is a far more pleasant work experience..it almost feels like you are in front of the actual machine.
     
  5. compdocs

    compdocs LI Guru Member

    How would I be able to have it lookup by the actual computer name? \\computername\sharefolder ? it still doesn't want to do it that way
     
  6. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    To access it via computer name..you need name resolution. For name resolution..you need netbios. Won't want to flow over a VPN. If you had a domain controller on the main site..you could query that for your DNS.

    For peer to peers..you'll want to set your host machines on a static LAN IP..then you'll want to edit you hosts file...
    IP address <tab> computername

    Located in
    C:\WINDOWS\system32\drivers\etc
    Edit it with notepad
     
  7. TazUk

    TazUk Network Guru Member

    You'll want to add it into the LMHOSTS file as well ;)
     
  8. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    You don't necessarily need both. I pretty much just use hosts file these days..since Windows 2000 came out..as it's more DNS. lmhosts was more of a poor mans WINS..and Win9X leaned on WINS first. But 2K/XP lean on DNS first.

    Certainly harmless, as long as you have no typos, to toss an entry in each though.

    Neither are needed if you do the IP approach, or better yet...Remote Desktop Client approach.
     
  9. TazUk

    TazUk Network Guru Member

    I thought NetBIOS used the LMHOSTS files to resolve names whereas SMB would use the HOSTS file :unsure:
     
  10. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    The way I look at it..lmhosts is a poor mans WINS...used it back in the days of Win9X clients when a WINS server wasn't on the network.

    Win2K and up...turned to DNS for local name resolution, associated more with the hosts file.

    Either will do the job..not really any right or wrong to it.
     

Share This Page