Browsing a remote network

[Guest]

I am running Windows 2000 Advanced Servier behind a NetGear router which
serves up the DHCP and runs a firewall. Because I have a mixed client
environment, I am running TCP/IP and NetBEUI on the LAN.

I have set-up RAS and a VPN which I can access from any remote client. When
the client has NetBEUI installed on the VPN connection I can remotely browse
the network. I can not get my remote Windows XP clients the ability to
browse the network. They can VPN in OK, but are denied access to browse the
network, ( or are constannly user-id/pswd challenged) even when they try to
specficially connect to a share.

I have not found a way to get the NetBEUI protocol to be an option to insall
on the VPN connectoid, but can get it to be an option and have installed it
on the hard-line LAN connectoid.

What can I do to get my Windows XP remote clients to VPN in and browse the
network remotely?

 

[Robert L [MS-MVP]]

Since you have windows 2000 server, I would install WINS.

--
For more and other information, go to http://www.ChicagoTech.net

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.

 

[Guest]

WINS is running on the W2K Server. What's next?

 

[Guest]

THE ANSWER IS:

In a typical home network environment, the IP sub-net is 192.168.X.X,
assigned using DHCP from the router/hub. As many small office environments
has now install small networks using similar routers/hubs, the IP sub-net is
also 192.1668.X.X. When setting up RAS and using IP static address settings,
assign the starting point to be 192.169.0.1 and the problem goes away.

Admittedly, I was led to this conclusion following the link listed in the
reply from Robert L to the www.chicagotech.net/vpn.htm site.

THANKS FOR YOUR HELP........