Hard Light Productions Forums

Off-Topic Discussion => General Discussion => Topic started by: Kosh on September 15, 2006, 05:08:30 pm

Title: Windows 2000 Server question
Post by: Kosh on September 15, 2006, 05:08:30 pm
Ok, I just recently installd and attempted to configure Windows 2000 Server. Although I am something of a n00b when it comes to servers, I was able to get the DNS working ok. The problem is with the DHCP (and also netlogon).


Once I was able to get it to release an IP address (and I am still not sure how I did that), and so I tried to login on a workstation with the network account I created (and yes, the computer is in the Active Directory). However, it wouldn't work and in the event viewer I got an error message saying that the computer "failed to authenticate. access is denied". I'm not really sure what the deal is with that.

But when I restarted the workstation, it requested an IP address from the DHCP service, but one was never released. Why is it ignoring these requests?
Title: Re: Windows 2000 Server question
Post by: karajorma on September 15, 2006, 05:13:18 pm
Is the DHCP Server authorised? If not you'll never get an IP address out of it. Run the DHCP control panel and check.
Title: Re: Windows 2000 Server question
Post by: Kosh on September 15, 2006, 06:40:59 pm
Ok, I think I've gotten it to work. Appearently AD just got a bit fubared earlier.


Different question: How do I up the limit on how many accounts I can create on one domain, or is that possible? I thought Windows 2000 Server had an unlimited client limit, yet now that my client number is 10, everytime I try and add more I get that error. What's the deal?
Title: Re: Windows 2000 Server question
Post by: karajorma on September 17, 2006, 06:59:16 am
Unless you're running into client or server licensing issues I have no idea what could be causing you that problem. What error are you getting?
Title: Re: Windows 2000 Server question
Post by: Kosh on September 17, 2006, 07:31:59 am
I found the problem. There is a limit of 10 clients on Windows 2000 Server, but it is not hard coded. It's just a default setting, and after doing some research I found a way around it. Next project, getting the clients to use the internet.........
Title: Re: Windows 2000 Server question
Post by: karajorma on September 17, 2006, 07:42:18 am
Are you talking about RAS connections? Cause I don't recall running into that problem myself on standard networked AD connections.
Title: Re: Windows 2000 Server question
Post by: Kosh on September 17, 2006, 09:17:48 am
No, it's not a remote server, it's just a standard setup. There is actually something in the Knowledge Base about this, but I can't be bothered to find it right now.