Home | Troubleshooting |  Quick Setup  |  Cisco How to  |  Data Recovery  |  Forums   | Blog | IT Exam Practice | Services  | About Us | Chicagotech MVP  | Search  | Contact Us  |                  Laptop for rent: $35 per day plus $10 for additional day

rental
 

 

Case Study – Client can’t access the Internet through Windows NAT

Situation: The client just installs a Windows Server 2003 as a NAT server. The server comes with 2 NICs, one connecting to the DSL line for the Internet access and another one connecting to the LAN. All clients and server can ping each other. The server can access the Internet.

Problem: No client can access the Internet.

Troubleshooting: 1. All client use the server inside IP as default gateway and can ping the IP.

2. The client can’t ping the outside IP and any public IP like 4.2.2.1.

3. The tracert displays the accessing internet stop in get inside IP and never get to the outside IP.

4. The result of ipconfig /all on the server shows that both NICs’ default gateways point to the DSL modem.

Resolution: in a multihomed server, you should only assign default gateway on the outside NIC and keep the inside NIC gateway blank. The outside default gateway should point to the router. Otherwise, inside computer can't route to the outside.

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

Auto VPN
Browsing over VPN

Enable Terminal Services
Export VPN Client Settings
Setup Windows VPN Client
VPN Setup

Case Study

Previous Page   Next Page
 

 


 

 

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