VPN Networking

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Windows 2000 SP3 server behind a Linksys VPN router.
2 satellite offices have the same VPN router.
I want the satellite offices to be able to map drives at the main office
(server).
I can ping the server and other IP addresses but I can't see the Server in
Explorer under network neighborhood to map drives.
I don't know if I need to start a service?
If I use a command prompt and enter //servername/directory I get a login
error.
My main office network has the VPN router running DHCP with a IP of
192.168.1.1 and the remote offices 192.168.2.1 and 3.1
I'm very new at this.
Can anyone lend a hand?
Or point me toward a good book/reference source?

Thanks.
 
sounds like name resolution issue, this how to browse over vpn may help, http://www.howtonetworking.com/VPN/browsingovervpn0.htm

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

I have a Windows 2000 SP3 server behind a Linksys VPN router.
2 satellite offices have the same VPN router.
I want the satellite offices to be able to map drives at the main office
(server).
I can ping the server and other IP addresses but I can't see the Server in
Explorer under network neighborhood to map drives.
I don't know if I need to start a service?
If I use a command prompt and enter //servername/directory I get a login
error.
My main office network has the VPN router running DHCP with a IP of
192.168.1.1 and the remote offices 192.168.2.1 and 3.1
I'm very new at this.
Can anyone lend a hand?
Or point me toward a good book/reference source?

Thanks.
 
You should rethink that. Mapped drive are very ineffiecient over a slow
link, people even have nightmares with them over normal Ethernet links for
that matter. They maintain a constant connection (until they timeout) which
is bad for a slow link. Use "shortcuts" to UNC paths instead. To the user
they just will look like a folder with a slightly different Icon.
 
Back
Top