Question

  Asked: Jul 6 2007   8:32 PM GMT
  Asked by: calitech


Server 2003 network - 2 NICS


NIC, OS, Servers, SQL Server, Security, Desktops, Management, Microsoft Windows, Networking, Hardware, Routers, Switches, Hubs, Cabling, Network testing, Network protocols, Networking services, DHCP, DNS, Network security, Firewalls, VPN, Intrusion management, Incident response, Forensics, Wireless, Tech support


I have a server 2003 with 2 nics
internal
192.168.10.1
255.255.255.0
no gateway
192.168.10.5 DNS

external
10.1.10.5
255.255.255.0
10.1.10.1 gateway
68.87.76.178 dns

Internal nic handles the DHCP 192.168.10.150-190 it has the scope options with the gateway 10.1.10.1 that is the comcast modem. and the DNS of 192.168.10.5

The internal network works. WS's can access the server. But they cannot access the internet. I can ping the 192 number but not the 10.1 numbers. If I want internet i have to mannually add the ip on the workstation with a 10.1.10 number.
What could be blocking this?
RRAS? I tried uninstalling it and that didn't work.

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
+1
Click to Vote:
  •   1
  •  0



*** Improved by Wrobinson on 12/22/07 ***

You need to configure DHCP to include a default gateway of 192.168.10.1 for the workstations and enable routing on the server for network traffic from the internal network to be forwarded to the external gateway and out to the Internet. Chances are that you will have to also setup a static route of 0.0.0.0 to the external gateway.

*** End update ***


I may be wrong on this, but if your internal NIC receives a request for something not 192.168, etc related, it would send that request to the gateway, which you do not have configured on the NIC.

try configuring the gateway
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Networking, Channel and DataCenter.

Looking for relevant Networking Whitepapers? Visit the SearchNetworking.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

Buddyfarr  |   Feb 21 2008  5:25PM GMT

I do believe that you need to change the gateway for the workstations’ NICs in DHCP to the IP address of the internal NIC, not the comcast router. once they get directed to the internal NIC then the internal NIC will pass it onto the external NIC and then onto the comcast router.

 

Jlees  |   Feb 27 2008  6:40AM GMT

Buddy is correct after you enable routing or internet connection sharing on your windows server. (Routing and Remote Access will do the same thing.)

 

Rbittel  |   Apr 30 2008  11:50PM GMT

Yes, you need to route traffic from the internal NIC to the external NIC. At a command prompt type in “Route’ for more info.. I’m not sure of the exact command syntax.