| Issues or Symptoms |
Article Title & Link |
Description or Resolution |
|
| In certain situations, VPN clients may
not be able access resources on a Windows VPN server with only has one
network adapter. |
Strategies to use if VPN clients cannot access resources
on a VPN server that has one network adapter |
This article describes two strategies that you can use to
configure a VPN server that is running Microsoft Windows Server 2003,
Microsoft Windows 2000, or Microsoft Windows NT 4.0 so that VPN clients
can gain access to NetBIOS resources across a PPTP VPN tunnel or a L2TP
VPN tunnel. |
|
| VPN Tools and Settings |
VPN Tools and Settings |
|
|
| Common VPN issues |
Common VPN problems |
• Connection attempt is rejected when it should be
accepted.
• Connection attempt is accepted when it should be rejected.
• Unable to reach locations beyond the VPN server.
• Unable to establish a tunnel.
|
|
| Troubleshooting remote access VPNs |
Troubleshooting remote access VPNs |
|
|
| Your Windows 2000 VPN are
unexpectedly disconnected from the VPN session after two or three
minutes. |
Disconnected from your VPN session after several minutes in Windows 2000 |
A supported hotfix is now available from Microsoft,
but it is only intended to correct the problem that this article
describes |
|
| Your Windows 2003 VPN connection
unexpectedly disconnects after several minutes. |
Disconnected from VPN session after several minutes in Windows 2003 |
A supported hotfix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. |
|
| Users cannot connect to a Server 2003
domain that is behind a Cisco router by using a VPN connection. |
Users Cannot Connect to a Windows Server 2003 Domain by Using a VPN
Connection |
A supported hotfix is now available from Microsoft,
but it is only intended to correct the problem that is described in this
article. |
|
| RRAS
does not forward packets over the interface that is selected as the
"Internet" interface after you enable VPN. |
Enabling VPN in RRAS Causes Connection Issues to Remote
Networks |
If you select VPN server,
you configure RRAS to accept incoming VPN connections. This secures the
interface you select by implementing filters that only accept PPTP or
L2TP traffic. Then, RRAS does not forward packets on that interface
unless they are PPTP or L2TP. |
|
| After
you use a VPN connection to log on to a server that is running RAS, you
may be unable to connect to the Internet |
You Cannot Connect to the Internet After You Connect to a
VPN Server |
To resolve this issue, configure the client computers
to use the default gateway setting on the local network for Internet
traffic and a static route on the remote network for VPN-based traffic.
|
|
| When
you log on using the "Log on using Dial-Up Networking" option, your
recently created VPN connection may not be listed. |
VPN Connection Is Not Available for Logon with Dial-Up
Networking |
This behavior can occur if you selected the "Only for
myself" option when you created the VPN connection. |
|
| Name resolution and connectivity issues
on a Routing and Remote Access Server that also runs DNS or WINS |
Name resolution and connectivity issues on a Routing and
Remote Access Server that also runs DNS or WINS |
When the Routing and Remote Access server registers
the IP address of its PPP adapter in DNS or WINS, you may receive errors
on the local computers when you try to connect to the server. You
receive these errors because the DNS or WINS servers may return the IP
address of the PPP adapter to computers that query DNS or WINS for the
server's IP address. The computers then try to connect to the IP address
of the PPP adapter. Because the local computers cannot reach the PPP
adapter, the connections fail. |
|
| Event ID: 20111 A Demand Dial Connection
to the Remote Interface |
|
* The transport protocol is disabled on the DOD
interface
-or-
* Your RRAS server is configured to use Dynamic Host Configuration
Protocol (DHCP) to assign remote TCP/IP client addresses and the RRAS
server cannot obtain addresses from the DHCP server.
-or-
* Service Pack 3 was reinstalled on the server, but Update on the
Services tab of the Network tool in Control Panel was not run for the
Routing and Remote Access Service. |
|
