asked on

DHCP Issues - Windows Server 2003

Well, we are trying to set up DHCP on a new server in one of our buildings, but it doesn't seem to be working. It will not hand out any requests (we are tying to give 10.44.x.x addresses). We have tried to simplify it down by hooking a client directly to the server through a network cable. The client still gives itself a 169.x.x.x address. We tried changing the IP address of the server to 169.x.x.x with the same subet mask (255.255.0.0) but it will still not give out any addresses. Any ideas?

Netman66

Did you Authorize it in AD?

khyer123

ASKER

We right-clicked on the scope and clicked on "Authorize". The option now says "Unauthorize". I would assume that this means that it is authorized.

Netman66

Yes.

Now put the proper IP back on the server and setup the scope.

If you need help let me know.

khyer123

ASKER

What would be the proper IP? Would it be anything I want? We were trying to make the ip 10.42.1.1 and hand out scopes of 10.44.x.x. Would this work?

ASKER CERTIFIED SOLUTION

Netman66

membership

This solution is only available to members.

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

Start Free Trial

khyer123

ASKER

It worked!! We set all addresses to 10.44.10.x with subnet masks at 255.255.255.0, I think we screwed up the subnet masks before.

We are going to work towards working with different VLANs. This is for a school district, and we are trying to keep teachers/administration and students on seperate VLANs (students would be 10.43.x.x and teachers would be 10.44.x.x, with the server as a 10.42.10.1). That will be a totally different story.

Thank you for your time and help