Need Help Setting Up DHCP Server

[detroit]

I'm setting up a DHCP server but am having problems.....

Currently, everyone has a static IP in the range of 130.100.100.x

I've added the DHCP service and activated the service. I have also added a scope of 192.168.100.1 to 192.168.100.254

If I set my PC to obtain IP address from DHCP server, I do not get one. I have tried flushing the cache on the DNS server and registering it, with no luck.

Any guidance and help would be very much appreciated....

Detroit

 

[hewissa]

Set the PCs to Obtain address automatically.

Run ipconfig /renew to renew an address with the DHCP Server.

Also make sure the DHCP has started. If it is an AD domain, authorize the Server in AD.

Hewissa

MCSE, CCNA, CIW

 

[detroit]

Have done all of that, and I get the following error when I do the ipconfig /renew

An error occurred while renewing interface Local Area Connection : unable to contact your DHCP server. Request has timed out.

 

[RRoth]

I ran into this exact problem and the solution was that you need to authorize the DHCP server with in the DHCP manager, otherwise it wont start dishing out addresses. You do this by right clicking on the server name withing DHCP manager and on the menu Authorize this server or something to that affect will be there. Click that and viola, addresses will flow. Also, you need to make sure you added all the workstations to the AD as well otherwise I don't think it will give it an address.

 

[NortonES2]

What is the IP address of your DHCP server?

-------------------------------

If it doesn't leak oil it must be empty!!

 

[detroit]

The DHCP Server is authorized and the scope is enabled.....

Any other ideas would be greatly appreciated.

Detroit

 

[detroit]

The IP address of the DHCP server is 130.100.100.251

Detroit

 

[bbyes]

Check to see if the static ip is still listed. If so try ipconfig/release first, then " "/renew.
When you release the old address you should have 0.0.0.0 as an address.(check it).
You can also just restart your PC after releasing the ip address and it should grab a new one from your dhcp server.

 

[detroit]

The client does release the address when I set TCP/IP to obtain address from DHCP Server. When I do the /renew, I get the error mentioned above.

Detroit

 

[NortonES2]

So you are trying to run 2 IP networks (130.100.100.x and 192.168.100.x) on the same LAN?

-------------------------------

If it doesn't leak oil it must be empty!!

 

[detroit]

Correct. I have all my users setup with static IP's of 130.100.100.x and want to slowly move them to DHCP using the range of 192.168.100.x

Detroit

 

[NortonES2]

I don't believe you can run 2 IP networks on the same LAN!!!

-------------------------------

If it doesn't leak oil it must be empty!!

 

[NortonES2]

You can try changeing the IP address of the server to 192.168.100.x and see if the workstation gets an IP address OK.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[bbyes]

One of the reasons for a DHCPNACK is "the ip address is invalid because the client computer has been moved to a different subnet". If your DHCP server is on the 130.100.x.x network, I'm not sure that your DHCP service can successfully hand out and acknowledge 192.168.100.x addresses.

 

[brontosaurus]

correct. the only way that's going to happen is if you've got dhcp helper set up on your routers or if you've got vlan's for these subnets running through the same switch with a routing brain.