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?
LVL 4
khyer123Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Netman66Commented:
Did you Authorize it in AD?

0
khyer123Author Commented:
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.
0
Netman66Commented:
Yes.

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

If you need help let me know.

0
Acronis Data Cloud 7.8 Enhances Cyber Protection

A closer look at five essential enhancements that benefit end-users and help MSPs take their cloud data protection business further.

khyer123Author Commented:
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?
0
Netman66Commented:
It would, but the clients wouldn't be on the same network as the server.

You're best to use private addressing internally.

You could give the server 192.168.20.2/255.255.255.0
The router could be 192.168.20.1/255.255.255.0
Your scope would then be 192.168.20.1 - 192.168.20.254/255.255.255.0
You would have an exclusion range of 192.168.20.1-192.168.20.10 (we will include 8 extra addresses for you to use in the future for static devices.  This will save you recreating it later.)

Your scope options would be:

003 - 192.168.20.1
005 - 192.168.20.2
006 - 192.168.20.2

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
khyer123Author Commented:
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.