asked on

Windows 2000 server and NO DNS

I came across a network today where the 2000 server is running active directory but no dns service.
Clients and server are both getting their ip from the router.
The machines logging in are mostly win98, but several 2000 wkstns are naturally taking forever to boot.
The current solution given to the client is to unplug the network cable until it boots, then plug it back in.

This network is in a golf pro shop and it's set up to record handicap scores.

Anyone comes across anything like this?
Anyway to get the 2000 wkstn to have the proper dns?

Thanks.

ASKER CERTIFIED SOLUTION

Lee W, MVP

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

FL6

ASKER

I know that would fix it, but I'm wondering if there is a solution without having to do that, or why it was configured this way in the first place.
Would there be any reason for configuring it this way?

mikeleebrla

>>why it was configured this way in the first place
not trying to be a smart azz, but the only answer to this is simply 'whoever set it up didn't know what they were doing'

DNS is REQUIRED for a windows domain to run.

take leew's advice and install DNS and DHCP on the server.

FL6

ASKER

>>not trying to be a smart azz, but the only answer to this is simply 'whoever set it up didn't know what they were doing

that's what I figured, I'm wondering why they just didn't leave it as a workgroup.

Pber

Is it the only server there? If not, the TCP/IP settings might be pointing to another server that has DNS running on it. As leew and mikeleebrla mentioned, you should be running DNS on the DC.

FL6

ASKER

It's the only server.
Originally the dns setting was pointing to the isp's dns server.