Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can Connect to VPN Server From Home but cannot access files

Status
Not open for further replies.

cranebill

IS-IT--Management
Jan 4, 2002
1,113
US
This forum was started in the 2000 Server Forum but am looking for other ideas...

Home:
WinXP Pro
Cable Internet
No Firewall
No Router

Work:
2000 Advanced Server (Domain Controller)
Fractional T1
Cisco 1720 Router (firewall)

Ok now I can connect and login to the VPN server from home but cannot map drives etc. The mappings i am trying to perform are the same as a workstation at work so i know they are valid. I have tried :

\\server\share

and also

\\x.x.x.x\share

neither work.

Any Ideas?

Bill
 
Can you ping the IP address of the W2K DC at work once you're connected via VPN?
 
Well i tried pinging both ip's when connected and not connected... i get request timed out on both. My router may not allow pinging... i dunno... seems weird but it connects so i have to be hitting the IP.

Bill
 
Describe your network connection from home to work, including all hardware and IP addresses you are using.
 
quoted from
Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN server, and you attempt to connect to a computer using a PPTP/VPN client, you may experience following problem: 1) The NetBIOS name of the computer to which you are attempting to connect is not resolved. 2) You may receive an error message similar to the following error message: "System error 53 has occurred. The network path was not found" when using net view or opening Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you attempt to connect to a computer using a PPTP client, you may be able to connect to computers on your local area network (LAN), but you may be unable to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server and clients.
2. If this is domain network and the WINS server is on the same computer as the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try to enable UDP ports 137 and 138 and TCP port 139 across all routers and firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use UNC to connect to the remote LAN, for example, use the net use h: \\servername\sharename command.
For more information, go to
Robert Lin, MS-MVP, MCSE & CNE
Windows, Network and How to at
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top