i'm using one win2k server machine for my dns, dhcp, & ad. this machine has a pci modem which i use to dial-up to the internet. upon enabling ics, my ip is set to 192.168.0.1, & i have configured my dhcp scope accordingly. the current scope options are pointing the "router" (default gateway) option to 192.168.0.1, pointing the "dns server" option to the same ip, & defining my domain name. on-demand dialing is enabled for ics & my dialup connection is configured for dhcp. as it is merely a home lan, & i am not constantly connected to the internet, i have not registered my domain.
dns is configured with one fwd & one rev lookup zone. they are both ad integrated, & the server is a root server, which doesn't allow me to enter forward'ers or root hints thru the gui.
a check with ipconfig & nslookup both confirm that all options that i have currently enabled are working. pinging back & forth across the network is possible & both files & printers are successfully shared.
the problem is that attempting to access the internet via a win2k client machine will always bring up error msg's. no outside internet content is available to any machine on the network besides the server; however, pinging my isp's dns server (or any other internet ip) from the client machine is possible.
the only reason i've setup dns on my server is because it is "recommended" for best ad performance. previously, under a different installation (w/out dns), internet content was served to the entire network (which consists of not only win2k, but win98, linux & unix machines) without problems.
have tried adding the ip address of one of my isp's dns servers to my dhcp scope options & configuring dns to note that server as a 2ndary server for the zone; with no luck.
any help would be appreciated.
<snip> the problem is that attempting to access the internet via a win2k client machine will always bring up error msg's. no outside internet content is available to any machine on the network besides the server; however, pinging my isp's dns server (or any other internet ip) from the client machine is possible.
the only reason i've setup dns on my server is because it is "recommended" for best ad performance. previously, under a different installation (w/out dns), internet content was served to the entire network (which consists of not only win2k, but win98, linux & unix machines) without problems.
have tried adding the ip address of one of my isp's dns servers to my dhcp scope options & configuring dns to note that server as a 2ndary server for the zone; with no luck.
any help would be appreciated.
Make your ISP's DNS name server first in your list - Win2k "stops looking" if the first nameserver it finds doesn't return an error - in other words, even if your name server doesn't resolve the reference, Win2K won't automatically look at the secondary server. The secondary servers are only used when the primary name server is down.