Server 2003 I have DHCP server running on one of my Domian controllers.....when usinf the MSC snapi all looks OK.....but no on that uses DHCP gets and address doled out they all end up with the famous APIPA address and of course the ycant do anything where do I start into troubleshooting this issue I had events logged earlier stating there were no credentials to permit DNS updating so I used the netsh dchpsever credential process giving the domain administrators username and then the doamin name and then the user passord ..I got the confimation thatthe credentials we accepted....... I did this step in orderto start to address this current problem...meaning the problem existied before I put these credentiasl in ...funny though that I never saw this alert about not having the necessary credentials

To troubleshoot this, we have to start with the obvious.. 1) If the server is a member of the domain, have you authorized the DHCP service? 2) Is the DHCP server service running? 3) Is your scope active? 4) Is this DHCP scope for a remote subnet or a local subnet that the DHCP server is plugged into? If it is for a local subnet, the scope subnet ID MUST match the NIC settings and DHCP server service Binding. In other words, if the server is on the 192.168.1.x/24 subnet servicing local clients, you can not issue IP addresses from a scope that is not in that subnet range like 192.168.2.x/24. 5) If this scope is servicing a remote subnet, then you will need to have a DHCP relay agent on that remote subnet to pass the DHCP broadcast packets through the router and directed to the DHCP server. The DHCP Relay Agent: Guide | VideoGuides and tutorials, visit ITGeared.com.

The server is a domain member its a Domain controller The DHCP service is running The Scope is active the scope is defined on the same physical network as the server itsself (192.168.50.0) the scope = 192.168.50.235 --> 192.168.50.254 Server = 192.168.50.48 thanks

Make sure that the DHCP service's binding is correct. Open the admin console, expand server object, right click IPv4, properties, advanced tab, binding. If that checks out OK, the next step is to check the DHCP logs and take a packet capture to see if the DHCP packets are making it on the wire and if so, what happens to the response. More resources: The DHCP Process: Negotiating a Lease: Guide | VideoGuides and tutorials, visit ITGeared.com.

you mean the DHCP snap in ? (admin console) server oject? I see the what appears to be a SQLserver icon with a green arrow on it ...is that the server object? I dont think I am folowing your lead here where do I find the logs ?

Yes, the admin console (dhcpmgmt.msc). If you launch that, you can add a DHCP server, then view the scopes. If you right click IPv4, general tab, you can enable Audit logging. This will give you more information regarding the leases. If the requests are being rejected, you would see them in the log but as NACKs (negative acknowledgements). The logs are written daily and located: \%systemroot%\system32\dhcp. If more detail is needed, the best approach is to run a packet capture. If you do not know how to do this, it could be quite challenging until you learn how packet captures are performed and analyzed. The packet capture provides the best insight because you are looking at the "conversation" in detail between the clients and server. Guides and tutorials, visit ITGeared.com.

I launch it I already see a server ico that has a green arrow on it so this is my server? on the rioght side its listed there also and it says "running" back over to left side there is the scope (looks like a folder) If I right click the scope folder icon Idont get anyhting called IPv4 I get another contect menu that says Display Stats Reconcile Deactivate Delete refresh Properties Help very confusing that my interface does not follow what you indicate

all hit hits in google about this ipv4 binding are related to server 2008.....you see I am on 2003 ?

I apologize, i missed that in your original post about 2003. So the 2003 admin console has a slightly different layout, but all of the concepts I have been discussing up to this point are the same. So, I assume then that when you click on the scope folder, you can see different items. One of them being related to the Active Leases. Since you indicated that none of your clients are able to negotiate leases, this folder should be empty. In any event, your focus should be on whether the packets are making it to the DHCP server. Since you mentioned that the server is on the same subnet as the clients, no DHCP relay agent is required. By the way, Have you validated network connectivity with a simple test? Such as on one of the clients, configure it with a static IP address. Then just open a command prompt and see if you can PING the DHCP server. If you cannot, you may have a network connectivity issue, or firewall settings are interfering. If network connectivity check is OK, we still need to figure out if packets are getting to the DHCP server. If they are and the server is rejecting them, you would see this in the DHCP logs. If they are not, then why is that? Are they leaving the clients? We need a packet capture to determine this.Guides and tutorials, visit ITGeared.com.

I apologize, i missed that in your original post about 2003. So the 2003 admin console has a slightly different layout, but all of the concepts I have been discussing up to this point are the same. So, I assume then that when you click on the scope folder, you can see different items. One of them being related to the Active Leases. Since you indicated that none of your clients are able to negotiate leases, this folder should be empty. In any event, your focus should be on whether the packets are making it to the DHCP server. Since you mentioned that the server is on the same subnet as the clients, no DHCP relay agent is required. By the way, Have you validated network connectivity with a simple test? Such as on one of the clients, configure it with a static IP address. Then just open a command prompt and see if you can PING the DHCP server. If you cannot, you may have a network connectivity issue, or firewall settings are interfering. If network connectivity check is OK, we still need to figure out if packets are getting to the DHCP server. If they are and the server is rejecting them, you would see this in the DHCP logs. If they are not, then why is that? Are they leaving the clients? We need a packet capture to determine this.Guides and tutorials, visit ITGeared.com.

Hi, Thank you for the post. Please elaborate more about when the issue happened? After server migration or server rebuild? Try to perform steps to troubleshooting: 1.Check the DHCP cable connection. Set static ip address on one computer and ping your DHCP server ip address. 2.Run command "ipconfig /release" and "ipconfig /renew" on your client. 3.Post your DHCP server and one DHCP client computer "ipconfig /all" result to us for analysis. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.Rick Tan TechNet Community Support

I alway use the various permutations of the IPCONFIG COMMAND on th workstation I getthe APIPA address I release/renew ...no change still get APIPA indows IP Configuration for DHCP server all address detials are operationall correct correct mask/gateway/dns servers Host Name . . . . . . . . . . . . : ml350g5bpm Primary Dns Suffix . . . . . . . : administration.eriecou Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : administration.eriecou thernet adapter Local Area Connection 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : HP Network Team #1 Physical Address. . . . . . . . . : 00-1F-29-62-8B-B4 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.50.48 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.50.10 DNS Servers . . . . . . . . . . . : 192.168.50.45 192.168.50.48 :\Documents and Settings\administrator.ADMINISTRATION>

RESOLUTION: The root of the problem was HP SIM issued a critical update for this server...this server not only hosts my DHCP service but is also the AD replication partner for my Domain Controller and both services were failing after hese updates are applied the HP initiated update pushed a new NIC driver.....on this server I had employed an "adapter team" and this new driver implemented in an "adapter teaming scenario" according to Microsoft would not support these services (not sure what underlying protocol was hosed) They double checked the setup and all ws OK so they went on to NETMON and the result was the clients would initiate the request (for dhcp or to replicate ) and that was that the server acted as if he just did not get the request's... not sure if it was something like SMB packets being dropped or what So I disolved the team and all worked fine .......... I guess its one of those time when you apply an update that maybe was not really needed ....... anyhow when it gets to using and interpreting NETMON that is When I call Microsoft in ...case closed.....