VPN-Gateway nicht erreichbar
Meldung: Unable to contact.... Remote peer no longer responding
Ursache: Routingprobleme bei Endgeräten, die durch vorhergehende DHCP-Adressvergabe verursacht werden.
Resolving Microsoft Routing Problems on Cisco VPN Clients
Microsoft routing problems can occur when a Cisco VPN Client (VPN 3000 Client, Cisco Secure VPN Client, or VPN 5000 Client) gets an IP address from the device terminating the tunnel (Cisco VPN 3000 Concentrator, router, PIX Firewall, or VPN 5000 Concentrator) that is on the same network as the local Network Interface Card (NIC). This can occur if a user has a laptop on the corporate network with a Dynamic Host Configuration Protocol (DHCP) or static IP address (10.50.1.x), brings the laptop home, dials into an Internet Service Provider (ISP) and connects using the VPN Client. If the terminating device sends the VPN Client an IP address that is on the same network (10.50.1.x), the user cannot send any data over the client connection. The packets are sent to the NIC, instead of over the VPN connection, because the traffic is still routed out of the NIC. This problem occurs on Microsoft Windows 95, Windows 98, and Windows NT 4.0. Symptoms of this problem are that the VPN tunnel comes up, but the PC cannot pass traffic. A route print command still shows the DHCP or static address, or both. If the IP address was received through DHCP, the DHCP lease can be manually released. The information in this document is based on the software and hardware versions below. Cisco VPN 3000 Client Cisco VPN 5000 Client Cisco Secure VPN Client
Die Lösung: Releasing the DHCP Lease
Microsoft Windows 95 Follow the instructions below to release the DHCP lease on Windows 95: Open an MS-DOS window and type winipcfg. Select Release.
Microsoft Windows 98 Open an MS-DOS window and issue the ipconfig /release_all command.
You can also follow the directions for Windows 95.
Microsoft Windows NT Open an MS-DOS window and issue the ipconfig /release command.