routing and remote access No network access

I setup routing and remote access (VPN), but when I VPN in the status window
shows:
IPv4 Connictivity: No network access
IPv6 Connictivity: No network access
Media State: Connected
Duration: (timer counting up)

I don't have access to anything on the internal side of the routing and
remote access server.

What do I need to do to be able to Remote Desktop to computers on the
internal network.
--
Harolds

"Harolds" <(E-Mail Removed)> wrote in message
news:EBA7EDD0-516F-4318-8978-(E-Mail Removed)...
>I setup routing and remote access (VPN), but when I VPN in the status
>window
> shows:
> IPv4 Connictivity: No network access
> IPv6 Connictivity: No network access
> Media State: Connected
> Duration: (timer counting up)
>
> I don't have access to anything on the internal side of the routing and
> remote access server.
>
> What do I need to do to be able to Remote Desktop to computers on the
> internal network.
> --
> Harolds


How did you setup VPN in RRAS? Did you allow IP routing in the properties?

Does the server have one or two NICs?

Is the server a DC? If so, and it has more than one NIC (multihomed), it can
cause problems with AD, unless it is SBS. Is this server an SBS?

See if the following help:

How to setup VPN server on 2003 server
"http://www.chicagotech.net/vpnsetup.htm#How to setup VPN server on 2003
server"

How to setup VPN and NAT on Windows Server 2003 as a router (follow
instructions respectively whether one or two NICs but disregard the NAT
portion)
http://www.howtonetworking.com/VPN/2003vpn1.htm

---
As for using RDP, Remote Desktop must be enabled on each workstation and
server (Right Click on My Computer, choose Properties, remote access tab).

Once you believe the VPN is connect, try testing the connection as follows:

Test by pinging the workstations by computer name (machinename). If that
doesn't work, then it's either there is no NetBIOS name resolution support
(no WINS), or the VPN is not configured properly.

Try pinging by FQDN (machine.domain.net). If FQDN doesn't ping, then it's a
DNS resolution issue possibly by using the wrong DNS addresses in DHCP,or
the VPN is misconfigured.

Try pinging by the private IP of the workstation. If that works, and the two
above do not, then DNS is misconfigured in your domain, as well as there is
no NetBIOS name resolution support (not using WINS).

If pinging by IP doesn't work, then VPN is misconfigured.

---
Keep in mind, if the RRAS server is internal, then you'll need to port remap
TCP 1723 and Protocol ID# 47 to the RRAS server to allow inbound PPTP VPN
requests.


---
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
(E-Mail Removed)
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.