Krista, it's pretty late right now so forgive me if I miss something.
W2K3 can most certainly share an internet connection. You do it through RRAS. As for IP addresses, DHCP is probably the easiest long term answer and no you don't have to have an Active Directory domain in order to do it but you can only have one DHCP server on your subnet. All your computers and routers/gateways need to be in the same subnet. What do you mean the gateway is hardwired to 192.168.2.1? Can you not change the address or configure the gateway to use a dynamic IP address? If not, you will have to make sure all other equipment has IP addresses on the 192.168.2.0 subnet. From what you said it sounds like that is what is happening. If your gateway and laptop are on the same subnet they can see each other. However, if the server is on a different subnet it won't see them and they can't see it.
1) Make sure every computer and router/gateway has an address such as 192.168.2.x with a subnet mask 255.255.255.0. You can do this with either DHCP or static addresses.
2) Configure RRAS on your server to route traffic to the internet.
3) Point the default gateway of each computer to the W2K3 Server. You'll also have to point your computers to a DNS server in order to browse the internet. Both these can be done through DHCP or statically.
That should do it. Of course there's another solution, use your gateway as a gateway. Connect it to the internet, connect the hub to the gateway, connect the server and all clients to the hub. By doing this you could use the gateway's DHCP server and eliminate the need to set up RRAS on your W2K3 Server.
I'd recommend you stay away from RRAS unless you feel like studying MCSE material. RRAS and RADIUS are powerful tools but can be tricky to implement.
You are also complicating your life by multi-homing your server. Just connect all computers to your hub unless you're trying to isolate some of the computers. In that case you will have to configure RRAS for the NIC that those computers access.
Hope this helped. Take it one step at a time. Get DHCP working and you're almost done.
PolarOrbit
14 Posts
0
February 6th, 2004 08:00
Krista, it's pretty late right now so forgive me if I miss something.
W2K3 can most certainly share an internet connection. You do it through RRAS. As for IP addresses, DHCP is probably the easiest long term answer and no you don't have to have an Active Directory domain in order to do it but you can only have one DHCP server on your subnet. All your computers and routers/gateways need to be in the same subnet. What do you mean the gateway is hardwired to 192.168.2.1? Can you not change the address or configure the gateway to use a dynamic IP address? If not, you will have to make sure all other equipment has IP addresses on the 192.168.2.0 subnet. From what you said it sounds like that is what is happening. If your gateway and laptop are on the same subnet they can see each other. However, if the server is on a different subnet it won't see them and they can't see it.
1) Make sure every computer and router/gateway has an address such as 192.168.2.x with a subnet mask 255.255.255.0. You can do this with either DHCP or static addresses.
2) Configure RRAS on your server to route traffic to the internet.
3) Point the default gateway of each computer to the W2K3 Server. You'll also have to point your computers to a DNS server in order to browse the internet. Both these can be done through DHCP or statically.
That should do it. Of course there's another solution, use your gateway as a gateway. Connect it to the internet, connect the hub to the gateway, connect the server and all clients to the hub. By doing this you could use the gateway's DHCP server and eliminate the need to set up RRAS on your W2K3 Server.
I'd recommend you stay away from RRAS unless you feel like studying MCSE material. RRAS and RADIUS are powerful tools but can be tricky to implement.
You are also complicating your life by multi-homing your server. Just connect all computers to your hub unless you're trying to isolate some of the computers. In that case you will have to configure RRAS for the NIC that those computers access.
Hope this helped. Take it one step at a time. Get DHCP working and you're almost done.