Home | Recovery | Cisco How To Net How To | Blog | Search | Forums | Services | Setup Guide | Chicagotech MVP | IT Exam Practice  |  About Us | Contact Us|

Chicago Area Laptop for rent: $35 per day plus $10 for additional day
rental

 

Case Study - Can't browse over VPN because the inside NIC is disabled

Situation: One of our clients setup Windows Server 2003 with two network interface cards as a router. They also enabled VPN on the server.

Problem: They believed the Internet was working because they could establish the VPN from outside and the server could access the Internet. However, the VPN client could not browse the remote resources. And the internal clients could not access to the Internet.

Troubleshooting:

Since the server could access the Internet and VPN client could establish the connection, the problem must between the server and the LAN. We checked these settings.

1. They didn't setup filtering.

2. The NAT had PPTP enabled and no inbound and outbound blocking.

3. No other firewall running on the server or inside computers.

4. Finally, we found the inside NIC was disabled. The internal clients can access the Internet and the VPN clients can browse the resources after enabled it.

Note: By default, the NAT assign 127.0.0.1 as private IP fro the VPN server (see picture). If the VPN private IP is inside NIC's IP and the NIC is disabled, the VPN client would not be ale to establish the VPN. Case Study - Can't establish VPN because the private NIC is disabled and Can't browse over VPN because the inside NIC is disabled

Related Topics

Previous Page   Next Page
 

 

Bob Lin Photography services

Real Estate Photography services 

 

 

  This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.