vpnbrowsing issues

Can access to the mail system but not share

Symptoms: 1) After establishing a VPN, the VPN client can access the mail system to receive/send mails but can't access other network resources. 2) When attempting to access a shared folder, the client may be asked for the username and password. 3) Some of users may not have this issue.

Cause: This is cached credentials issue, especially you use third party VPN. For the consultants, refer to case 0304TL.

Assuming you don't have DNS, WINS or other name resolution option to resolves NetBIOS names, you should use IP to browse the remote computers after establishing the connection. To do this, you need to find the IPs by double-clicking the VPN connection icon>Details. This will give you the "virtual" IP allocated to both machines. Then use net use command to map the remote computer. If you get access denied error, try to add /user:username option to cache credentials.

Unable to access the resources on the network

1) Check the DNS and WINS setting. 2) Verify that either the protocol is enabled for routing or the Entire network option is selected for LAN protocols being used by the VPN clients.

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.