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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

After get Connected thru PPTP , i can't see the share folder of ping

Status
Not open for further replies.

winpt

IS-IT--Management
Aug 8, 2004
4
US
After i get connected VPN PPTP to my server i can;t ping any computer or my server side from the client. When i try to browse the network also does not show anything + when i use net use try to map network it show "system Error 53 has occured, the network path wash not found )

Please need some help

I did open port PPTP (1723) and GRE (47)
 
System error 53 is name resolution issue. thi smay help. 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 resources by ip, for example, use the net use h: \\serverip\sharename command.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at
 
# unable to ping is understandable. Your firewall is preventing that. Also you cannot browse the network.

# check the VPN adapter IP address that you got.It should be from the same subnet.

I guess this is an IP address issue. After you resolve this, you can map via \\ip address\sharename, instead of netbios names. You can eliminate this by pointing it to DNS or WINS which will get the IP.
 
I have a similar problem to this - the difference is that the names are being resolved but I just can't connect to or ping any machine other than the VPN server.

If I ping a hostname, it resolves the correct IP address but I get a "Request timed out" message. Our firewall PC crashed recently and I am wondering if there is something that hasn't been set back up. What ports do I need to allow certain traffic through for PPTP connections?

Mighty
 
The port for PPTP is 1723 and you also need to allow GRE protocol to be forwarded through the firewall.

I'm a bit confused by chicagotechnet's comments. My understanding is that everything required for a VPN connection was contained within the PPTP tunnel. What I've read on internet firewalls suggests that opening ports UDP 137 & 138 and TCP 139 is a real security problem. Have I got this wrong?

Currently, in my office I've set up a Win2003 server as both a domain controller and a VPN server behind an ADSL router with firewall enabled. DNS is handled by another server on the same domain. On the LAN side I can log onto the domain and browse all the shares on the domain fine. On the internet side, I can connect to the VPN server from home,it says I've logged in, but I can't see anything. I must be missing something. Any suggestions?

Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top