RRAS configuration questions

  • Thread starter Thread starter LL
  • Start date Start date
L

LL

Hello,

We have W2K domain, DC with DNS and RRAS server has static IP address
192.168.1.90. All other pc's in our network are DHCP clients. Linksys
router works as DHCP server with starting IP address 192.168.1.100.

I use static address pool for VPN clients - let it be
192.168.1.20-192.168.1.30, so internal VPN interface got address
192.168.1.20.
All our VPN clients can connect successfully, can see all computers in
Network Place or Network Neighborhood (depends of clients OS). The problem
is :
clients have access to share resource on RRAS server, but all attempt to get
access to all other computers in the network are ended with message "The
network path is not found" or "You don't have right..." or something about
network error. We resolved this problem for Windows 98 clients by adding
them gateway for 192.168.1.20 (VPN interface). It works perfect, all network
is fully accessible for them, but I would like to ask you, gurus: what wrong
in this VPN configuration, is it better to use static pool for VPN clients
or dynamic pool and why? And another question is about XP clients: I
didn't find the way to add gateway, so should I add entry to routing table
to fix this problem?
Thank you very much for all reply.
L.
 
quoted form 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.

--
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.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Back
Top