Windows

Assuming your remote client is a W9x/NT machine, you will need to enable WINS resolution in the TCP configuration and add your Wins server to the server list there. If on the otherhand you don't use Wins on your domain or you don't have a windows client you will have to use DNS for host name resolution. Or just use the UNC naming convention to locate the resources you need. IE: \\server1\shared\files etc.

You should have netbeui turned on in the vpn connection.

If you are using WINS you may have a problem, since your vpn client will not check in with WINS. In this case you may want to have an LMHOSTS entry for your domain controller, with the #DOM: tag set.

Try pinging a computer on your network from the dialed-in vpn client. If you get a ping, try mapping a drive using an ip address.

If you do not get a ping, check the IP number that the vpn server is giving to the client, and make sure that the ping target has a route back to the client. (If the target server has a default gateway other than the vpn server, that gateway router should have a static route for the subnet which the vpn server is using, pointed at the vpn server.) Tryadding a route on the target server:
ROUTE ADD <vpn-net-address> MASK <vpn-address-mask> <vpn-server-address>
If a ping to that target server starts working, that was your problem.

Good luck.

Use LMHOSTs and NetBEUI only as a last resort. LMHOST files on the clients are cumbersome, and you have to make sure you make appropriate changes to them if you make any changes to your network. As for NetBEUI, your VPN should work fine with TCP/IP- mine does; additionally, adding NetBEUI to your client would mean having to add it to your LAN. You want your LAN to use only TCP/IP for best performance. Try the following on your 9x machines:
1. Make sure the workgroup name on the RAS client is the same as the workgroup name or domain of your LAN.
2. If you are using DHCP, make sure you have configured the DHCP scope to provide WINs addresses. You may even have to go as far as manually inputting the WINs server IP address on the clients (In the Network Neighborhood -> Properties -> TCP/IP (VPN Support) -> Properties, and in the VPN DUN properties). You definitely need to do this if your clients have static IP addresses.
3. Your WINs server should not be multihomed (two NICs in one server, each connected to a different network).
4. Verify that you selected the "Allow RAS clients to access entire network option on the NT RAS server" if you want the clients to be able to see other network resources other than the RAS server (This is an option in NT Server 4. I don't know if it exists in 2000).
5. If the remote client is a laptop that was recently connected via a LAN connection, allow enough time for the browse list to drop the machine before dialing in. Otherwise, a conflict can occur.
6. For your Win95 clients, download and install the the Dial Up Networking patch:
http://www.microsoft.com/downloads/release.asp?ReleaseID =12646 (there should be no spaces in this link)
7. Download and install RASUPD.EXE for95 OSR1 clients. Install RAS2UPD.EXE for OSR 2 and 2.1 clients. You'll find them at the MS Knowledge Base under article Q154434.

Hope that helps.

This question was closed by the author