Re: VPN routing - single NIC
- From: "Bill Grant" <not.available@online>
- Date: Wed, 29 Nov 2006 11:00:40 +1100
There are two distinct things to look at here. They are routing and name
resolution.
Check to see if you can ping a LAN machine by its IP address. If you
can, routing is working, so adding static routes won't change anything. You
need to look at name resolution. If you are using DNS, check that the client
has the correct DNS server address and also the correct DNS suffix. If you
are relying on Netbios for name resolution, check that the client has the
correct WINS address.
If you cannot ping by IP it may be a routing problem. What IP subnet are
you using on the LAN? Does the remote client receive an IP address in this
subnet?
<Jordan> wrote in message news:kudpm2dm2r9802c39lteonknn02v7894s7@xxxxxxxxxx
Hi
Have used the RAS wizzard (custom choice, had to use this one because
of one NIC) to configure a RAS VPN connection.
This is a single NIC w2k3sp1 server.
The VPN client can map local drives at the server.
But can't map drives and shares on other servers on the local network,
which I want.
Do I have to "route -add" something?
Any clue?
Regards
Jordan
.
- Follow-Ups:
- Re: VPN routing - single NIC
- From: Jordan
- Re: VPN routing - single NIC
- References:
- VPN routing - single NIC
- From: Jordan
- VPN routing - single NIC
- Prev by Date: Re: Adding a DHCP Scope to Windows 2003 Server
- Next by Date: Re: VPN setup question
- Previous by thread: VPN routing - single NIC
- Next by thread: Re: VPN routing - single NIC
- Index(es):
Relevant Pages
|
Loading