Discussion Locked

Microsoft DHCP to Lucent QIP DHCP

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having a problem converting one of our branches from Microsoft DHCP to Lucent's QIP DHCP.
On other branches, basically a DHCP relay agent is setup on the server to point towards a regional QIP server which hands outs addresses as required. These other branches were all originally configured with static addresses for the clients and have all picked up the new scopes successfully. However a branch that is currently on Microsoft DHCP seems to be reluctant to switch over. As a test I have stopped the Microsoft DHCP server service and cleaned all the DNS/DHCP server settings (I think) out of the client's registry but it still wont pick up the new scope addresses. I can ping the regional server from the NT server in the branch and the dhcprelay agent service is running. Im thinking possibly there might be a problem with dhcp traffic passing through the local router. Any ideas would be appreciated

3 replies

by paulp

Have there been enough I.P. addresses allocated for either this location or all the branches?

by paulgking

Yes sufficient scopes have been created. I think the problem was some details were missing off the subnet profiles. Thanks.

This discussion is closed to new replies.