We have been running a Win2003 server for a couple of months now, it replaced an NT4 server.
We had some problems after install with DNS, which were resolved at the time by pointing the DNS server
in the Win2003 TCP/IP settings to ISP DNS.
We are not too interested in running DNS for a network of 20 computers, but now I'm hearing it's
mandatory for Active Directory. Therefore, is it wrong to have Win2003 point to ISP on TCP/IP settings
and not DNS Forwarders? We have a private network, so there are no addresses visible to the Internet
(connection through NAT).
These problems came apparent when our ADSL connection failed. Now this should only affect outgoing
traffic, but now OUR INTERNAL SERVICES HAVE SLOWED TO A CRAWL! It takes forever to log on, it
takes forever to browse files on the server and opening them fails most of the time.
I can only think of this has something to do with us pointing the Win2003 server TCP/IP settings DNS to
ISP DNS server, which is now unavailable until the connection is fixed.
So how do we configure this 'properly'? The Win2003 server doesn't need to be visible to the Internet,
in fact, better if it isn't. It just needs to download updates from the Internet (so a connection is needed),
distribute them to the private network, as well as provide AD services for this one isolated site.
And file sharing.
Thanks for your help!