Win2K Server and Modem Router

[axslinger]

Hello, I have a Win2K Server that is a DC for a single domain network. I also have Active Directory Services installed.&nbsp;&nbsp;This is a<br>small network with a single subnet and an 8-port switch.&nbsp;&nbsp;5 workstations.<br><br>Due to fact that I am running ADS, I have DNS running also.&nbsp;&nbsp;For internet access I have a Netgear Modem Router.&nbsp;&nbsp;Its basically a 4-port<br>hub with a built in 56K fax modem.&nbsp;&nbsp;It also acts as a DHCP server,although I am using a static address on the server.&nbsp;&nbsp;It is plugged into the main 8-port switch with a cross-over cable.<br><br>I am a little confused as to how the DNS on the clients should be setup.&nbsp;&nbsp;Normally the ISP DNS is dynamically assigned when connecting.&nbsp;&nbsp;I do however know the addresses that are used.&nbsp;&nbsp;Should I enter the Win2K<br>address as well as the ISP address in the DNS settings on the clients or just the Win2K address?&nbsp;&nbsp;Also, how should I configure the client side at the Win2K Server?&nbsp;&nbsp;I know that normally, if a Win2K server is a DNS server, it should point to itself.&nbsp;&nbsp;But do I need to enter the IPS's DNS addresses on the client of the Server also?&nbsp;&nbsp;The&nbsp;&nbsp;modem router can also be setup to use dynamic or static IP and DNS.<br><br>The reason I am asking in the first place is because workstation requests don't consistantly trigger the dialer like they should. But if I go into the client TCP/IP settings on the server and change<br>the order of the DNS addresses, then save the changes, it will sometimes cause the<br>dialer on the modem router to start working.&nbsp;&nbsp;But it doesn't stay that way. Typically, the next day, the modem router is hung again.<br>Sorry to be so long winded.&nbsp;&nbsp;I just didn't want to leave anything out. Any help here would be greatly appreciated.<br><br><br>Brian Witowski<br><br>