Hi I created a domain behind a router xxxxxxx.com, but still is not working perfectly. I'm new to using/creating domains. I created a domain on a W2K server and 'm currently running 1 windows 2000 proffesional machine on the domain, everything is working fine, except for internet. So the client computer is getting a dynamic IP from DHCP which i configured on the server and DNS is working. I can ping the server and vice versa. But connecting to the internet does not work for the client, the server can conenct to internet. Already tried to add ip routing, and configured the server with the dns provided by my Internet provider, but still no luck. The router is using ip adresses in the range of 10.0.0.x the server is behind the router. Ip gave the server (DC) 2 IP's. I have an IP scope of 192.168.0.1-12. The server has the follwing ip adresses: 10.0.0.153(external network => internet IP which the router uses), and 192.168.01 (for the network behinh the router = internal network). But the client cannot access the internet through the server with the following ip adress: 192.168.0.2 ,it can ping to the server, and when using the name of the server to ping, it does resolve the name, so DNS is working. When i try ti ping a internet ip adres it says: unknown host I hope this is clear. Can anyone provide me with an anwser? did I miss anything What do I have to check?

You either need to have just one network connection to the server (ie, its connected to the switch like everything else) or you'll need to set up a proxy server on the 2k server - eg - http://www.janaserver.de/start.php?lang=en or 2k server may have its own feature to do this. The problem is the internet is obviously not on the same network as the LAN (I'm not an expert in this - but a school I look after has a 2k3 server set up this way, with a proxy server enabling internet and email access - in fact I'm using the one linked above).

You need to designate roles. Either the router is just a firewall or it's going to do your DHCP and NAT as well. Or you can have your server do the DHCP and NAT. Having said that...the simplest solution is to allow the router to do all the above and forward your DNS to your ISP's. Then have the clients point to the DC (your server) for their DNS so they can authenticate to the domain properly. Forwarding your DNS means that requests outside the local zone will be forwarded to your ISP's DNS server for resolution. This allows your clients to browse the web.