DHCP Win2k

[tohare1985]

I'm trying to switch DHCP Server. I had no problems enabling DHCP on the new server but I cannot get the old DHCP server to keep offering IP's. I've disabled the service, stopped DHCP in the registry and uninstalled the component but it keeps offering Ip's.

 

[lhuegele]

Have you tried turning it OFF?

 

[tohare1985]

Can't leave it turned off. Using it for things besides DHCP.

 

[TheMisio]

tohare1985,

If it's a new server, it will not lease any addresses until it has been authorised in Active Directory.
Have you authorised the server?
Or is it a standalone server in a workgroup?

Regards,

Michael

 

[tohare1985]

The problem isn't the new server issuing IP's. It's that the old server keeps issuing IP's after I disabled DHCP.

 

[TheMisio]

Sorry, misunderstood it.

Have you tried unauthorising the old server in AD?

Regards,

Michael

 

[tohare1985]

Yes, I de-authorized it from the AD. I removed it completely from AD. I uninstalled the DHCP component. Nothing worked.

 

[TheMisio]

OK.

How do you know the old server is still offering IP addresses?. If it has been disabled / uninstalled there is no way it can offer address leases.
Are you looking at the client machine or the server?
Remember, that if the lease length is set to for example two weeks, a client machine will report DHCP server even if the server is down.
You need to release the IP config from client machine and renew the lease.

Regards,

Michael

 

[tohare1985]

I have a tool called DHCP find. It shows 2 DHCP servers on the network.

 

[lhuegele]

Ok, so a tool is telling you there are 2 DHCP servers on your network, but have you done anything to confirm that the old server IS or IS NOT giving out addresses?

Turn off your old DHCP server (not for good) and then run your tool again. If it still shows 2 DHCP servers, then at least you know that the tool is finding yet ANOTHER server that you knew nothing about!

Got any wireless access points in your environment?

Good luck,

 

[netometer]

Hi,

I would suggest a different approach.
Stop for a couple of minutes the new DHCP server.
Run the following at a DHCP client Command prompt:

ipconfig /release
ipconfig /renew
ipconfig /all

Normally running the commands should tale less than a minute. Examine the output of "ipconfig /all" - it should be something like this:

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : WorkGroup
        Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
        Physical Address. . . . . . . . . : 00-0F-B0-64-79-74
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.2.111
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.2.1
[highlight]
        DHCP Server . . . . . . . . . . . : 192.168.2.1
[/highlight]
        DNS Servers . . . . . . . . . . . : 192.168.2.10
        Primary WINS Server . . . . . . . : 192.168.2.10
        Lease Obtained. . . . . . . . . . : Friday, April 18, 2008 9:40:18 AM
        Lease Expires . . . . . . . . . . : Friday, April 18, 2008 9:55:18 AM

Don't forget to turn on back the new DHCP server after running ipconfig /all

Regards,

Dean

http://www.netometer.com

Online Screencasts and Video-Tutorials