Computer can't get to internet

[jamin123]

I've 3 computer on a home network.
2000 Advance sever w/AD can access the internet but 2k prof. workstation can't.
Sever has 2 NIC, NIC 1 gets IP from ISP, NIC 2 hard-code with 10.x.x.x. The workstation get thier IP's from the sever and can access all share on the domain and ping each other.

What do I need to do to get the workstation to access the internet? Do I need to turn on routing on the sever? How I do that?

I don't want to buy a router I want to use the resource I've.

 

[somebigguy]

Open up the Routing and Remote Access wizard under Administrative Tools, it should walk you through exactly what you're trying to do.

 

[jamin123]

Thanks I'll try that tonight.

 

[dholbrook]

Put a router between the systems and the ISP, and give the hard address to the router and let the router provide all systems with the internet access, plus provide the DHCP addresses for all your systems. Without routing, or a router, your local systems have 10.x.x.x addresses and will not get to the internet, but will see each other.

Why are you using the hard address on one nic of the server when all the other systems get their addresses from your server? Just because the workstation receive IP addresses does not mean they can even see the ISP (and with 10.x.x.x addresses,they do not). The DHCP will give them an address to be able to communicate with each other, but unless they can also connect with the ISP and provide proper credentials, the ISP will ignore their requests for Internet access..

Use your server as a router: Connect the single server NIC with fixed address to the ISP, turn on routing in the server, and assign fixed local compatible IP addresses to the workstations and the second NIC with the server. With only three addresses, set them manually, do not use the DHCP function the server. Put the workstations and the local server NIC all on the LAN, and then point all workstations to the server local NIC IP address as the gateway. The server local LAN nic MUST NOT have a gateway address assigned, and the server NIC connected to the ISP WILL have the gateway address assigned by your ISP, and it MUST BE the ONLY gateway address on the server to correctly forward all requests to the ISP.

HTH,

David

 

[jamin123]

Thanks David, I'll try that this weekend.

 

[vbrocks]

On the workstation setup the server as your default gateway in tcp/ip properties.
Enable RRAS on the server.

 

[quake11]

You cannot route 10.x.x.x packets over the public network regardless of how you setup ip on workstations. You require the use of NAT (Network Address Translation). Here's info you need: Microsoft Knowledge Base article Q299801