Member Avatar for cguan_77

Hi guys, if DHCP server failing to assign IP Address to the workstation, what could be the problem? any idea is greatly appreciated...

I tried IPCONFIG /RENEW on a workstation but it fails..

If i tried to manually configure the IP settings on TCP-IP workstation can connect to internet..

But if I set the TCP-IP settings to "Obtain Automatically IP Address" it fails...

OS:WIN2K3

  • 3 Contributors
  • 2 Replies
  • 121 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by bilbus

Dani AI

Generated

Given that a manually configured IP on the workstation works but "Obtain an IP automatically" fails, the problem is almost always DHCP traffic not being completed — either the client’s DHCPDISCOVER never reaches a server, or the server refuses/has nothing to offer. ’s pointer to client-side checks and ’s suggestion about using discovery tools are sensible first steps. The following checklist shows the high‑value checks that were not yet covered.

  • Scope and leases: verify the server’s DHCP scope has free addresses and no overly broad exclusions or mistaken reservations that would prevent issuing a lease.
  • Server status and authorization: on Windows Server 2003 confirm the DHCP service is running and, in an AD environment, that the DHCP server is authorized to issue leases.
  • Network path / relay: if the client is on a different VLAN/subnet, ensure the router has a DHCP relay (helper) to forward broadcasts to the server; without it the server won’t see the request.
  • Rogue servers and packet capture: use a packet capture (Wireshark or Microsoft Network Monitor) on the client or server to watch for DHCPDISCOVER and any DHCPOFFER. No offer seen on the server side = request never arrived; unexpected offers = rogue DHCP.

Also check UDP ports 67/68 aren’t blocked by firewalls between client and server, inspect DHCP-related events in both client and server Event Viewer, and confirm there are no MAC reservations or conflicts. If you suspect DHCP database corruption on the server, back up the DHCP configuration before attempting repairs.

A sensible troubleshooting sequence: confirm scope availability → verify server is running and authorized → verify relay/router path → capture traffic to see who answers → review event logs. That sequence quickly narrows whether the fault is server configuration, network path, or a rogue/third‑party device.

Recommended Answers

All 2 Replies

Member Avatar for freshfitz

disable the card and re-enable it, bad cable, is dhcp client turned on in services?

Member Avatar for bilbus

download dhcpfind and troubleshoot it

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.