Name: 0perand Date: May 11, 2008 at 20:52:21 Pacific Subject: Windows Server 2003 as a Router? OS: Windows Server 2003 CPU/Ram: 4GB Model/Manufacturer: HP
Comment:
I have a server running Windows Server 2003. It has 2 nics. One nic is dedicated for internet the other is plugged into a switch for the lan. The server is running DHCP,DNS,WINS,AD,IIS,Sharepoint and File/Print sharing. I have run the RRAS wizard multiple times, but have not been able to get the LAN online.
I have the DNS,DHCP,Default Gateway on the LAN all pointing to the server's interal LAN IP address. The LAN nic has a static ip, subnet mask, but an empty default gateawy. It has static DNS as well.
I am sure I am missing something stupid. Thanks for the help in advance.
You can save yourself a lot of trouble if you used a router for a router and the server for the server.
Dual homed servers can be a real pain. I would place a router behind the modem and connect ALL PCs including the server to it. All machines will have the internet and still be able to access files. That will also add an extra layer of protection to your LAN.
I have the DNS,DHCP,Default Gateway on the LAN all pointing to the server's interal LAN IP address. The LAN nic has a static ip, subnet mask, but an empty default gateawy. It has static DNS as well.
I have to agree with guapo on this one. A router after the modem with your switch plugged into it will be your best idea. All you would need to change is the default gateway IP of the clients. They would need to point at the router to access the internet.
I think you may have not forwarded your DNS server to your ISP's DNS server(s) from the sounds of it. Ensure it's properly forwarded and your clients should be able to access the internet.
It's worth noting that should you put a router in, you wouldn't have to (or want to for that matter) change your DNS settings as your clients still need to point at your DC for DNS no matter what (so they can authenticate upon login).
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE