RRAS and VPN w/ Win'98 Client

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

Guest

I have a Win'98 client that can log into the network using the MS VPN client.
It can ping but not browse; WINS is NOT set up on the network. Both the
client and network are using the same subnet (the server is set up to give
out an address in the same subnet). I was able to net view the server's IP
address and map a drive using the IP one time only. After about 30 minutes
of inactivity I could not view anything on the mapped drive. Got a server
not available error.

Ever since that one time, I cannot net view the IP address of the server (53
error). I CAN ping it, but nothing else.

Do I need WINS on the network and client AND have the server give out
10.x.x.x versus the LANs IP of 192.168.1.x?

TIA

jwkh
 
assuming "Both the client and network are using the same subnet" means the
VPN client, then you do need WINS. alternatively, use LMHOSTS. Or map the
network drive instead browsing in ,y network.

This may help. quoted from http://www.ChicagoTech.net


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.

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
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions, http://www.chicagotech.net/networksolutions.htm
VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis, http://www.chicagotech.net/VPN process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
 
A VPN or RAS connection just gives you an IP link. It does not give you
the things you get on a LAN, particularly broadcasts.

So IP addresses will work, but name resolution will not work unless you
have HOSTS files (or DNS) for DNS -style names, or LMHOSTS files (or WINS)
for Netbios names. Computer browsing in NN or Network Places is even
trickier.
 
I've a hosts file for the client which didn't help. It only uses the "short
names" -- not FQDN (or "server.domain.com").

I guess I need to use FQDN in the hosts files for the Win'98, and/or LMHOSTS
files for the Win'98? And is there no problem with the same subnet issue
between the LAN and the VPN client's IP addresses?

You allude that NN/NP is possible in the VPN environment. Got any ideas
that may help?

I greatly appreciate your help.

jwkh
 
Browsing from a remote doesn't really work without a domain. The client
(W9x or W2k/XP) tries to find the master browser by looking the domain
master browser in WINS. If there isn't one, it just seems to sit there.
There doesn't seem to be a way to make it look for a workgroup name.
 
The LAN is a domain and the client's workgroup name is the same. If I
install WINS, will that help with browsing?

At any rate, my main concern is access to shares...even if I have to map
drives by \\IP\share_name.

Are there any docs you're familiar with that can get me to that level?

TIA,

jwkh
 
Yes, WINS should allow the remote client to browse the LAN if the LAN is
a domain (and the client has the right domain name). When the remote client
looks in WINS for the special Netbios name <domainname 1B> (which is the
domain master browser), WINS should give it the IP address of the PDC. It
should then get a browse list OK.

WINS should also let you use things like net view \\machinename and
net use \\machinename\filename . The remote client will get the WINS
address from the RRAS server when it connects and gets its IP address.
 
Back
Top