Question : Configuring/setting-up DSL connection/service with router onto a Windows 2000 Server Network with AD, DHCP.

---Currently in the process of replacing a pre-existing network with workgroup environment which consists of a "server" running Windows NT 4.0, 12 workstations running Windows 2000 Pro and a DSL modem connected to a router wich is configured with DHCP service. The workstations and server were recieving their IP addresses and Gateway from the router which in turn came from the ISP.
--- I have replaced the server with a Windows 2000 server configured with AD and DHCP, (Originally, when I first installed the server and got the 'Configure Your Server' wizard it wouldn't let me have it as a stand-alone server -reason bieng that it thought there was another server running on the network, disconnected the router from the switch and took care of that issue.) Now, all the workstations and network printers are getting their IP addresses from the Win2000 server and are part of the domain. All the settings are the defaults when you first install Win2000 Server.   The Problem is how do I get my users to get internet service from the DSL Service -- or -- How do I configure the router and server so that it is part of the network and people can use the internet. below is a rough schematic of how things are set-up.

DSL MODEM
       |
NETOPIA ROUTER
       |
  SWITCH_____________
       |                             |
SERVER(AD & DHCP)      WORSKSTATIONS


I'm still relatively new to this but know enough to be dangerous, so if I miss something let me know please!!

Answer : Configuring/setting-up DSL connection/service with router onto a Windows 2000 Server Network with AD, DHCP.

Sci....not trying to beat a dead horse, but I would have to argue that a real "router" isn't any easier to set up for routing than a windows box is for DHCP, regardless of the person's experience!  These little personal home routers/NAT devices are pretty easy for a person who's not a professional tech, and that "reset" button is a handy option, but it's still not a substitute for being able to effectively set up the options you are wanting.......going back to the "default" isn't always the best solution, imo.  (i.e. If I simply go back to the default settings on most of these "home" routers, my security is pretty weak.)  Therefore, the question seems to be, is it better to go with the simple solution that magically makes things work (but maybe not optimally) or is it better to learn what the real problem is and simply fix the problem at hand?  I would choose the latter unless things are just so screwed up that it's better to start at the beginning.

That being said, rosendo, from the way you've described your problem, the first two things I would look at are the DNS server and Default Gateway entries on your workstations.  Here's a brief explanation......

DNS - The DNS server entries should contain the AD server's address and possibly the router's address (depending on your setup)......if your workstations can't resolve domain names (i.e. www.espn.com) to IP addresses, then your machines aren't going to be able to surf the internet very well.......DNS is what resolves those names, so it's important to have those machines point to a DNS server that will be able to help them.  

Default Gateway - The Default Gateways should all be pointing to the router's address.....that is how your machines are going to get to the internet......a Default Gateway tells your machines where to send packets that are destined for addresses outside of your network/subnet.  

You can find this information on each machine by doing an "ipconfig /all" from the command line.  If you find a problem with one or more of these entries, then check your DHCP scope options on your W2K server.  That should be where you have set the values for the DNS server(s) and Default Gateway to be given out to the DHCP clients.

Post your ipconfig results if you have problems (You can "xxx" you MAC addresses for security, if you want.)

Keep us updated!