Quote:
Originally Posted by whydoIneedatech
The computer is Autoconfiguring its own IP so it is not able to talk to the internet or it would get a 192 IP or a public IP.
|
Too little information to say anything for deffinate. I wouldn't say that the PC can't talk to the network, more that the DHCP server hasn't replied to a request, now that could be because 1) It's never been asked for anything 2) It has replied but the client device isn't recieving the replies. 3) It won't reply because the device isn't allowed to request an IP.
Easiest way of proving this would be to give one of the affected machines a static IP address outside of the DHCP scope, and then try and ping the DHCP server by it's IP address, if the ping times out, you may wantt to try pinging another statically adressed device on your network, if this works then you have basic IP unreachability issues on your DHCP server.
If pinging the DHCP box works, then I would strongly sugesst that you look at the configuartion of your DHCP server for any mac exclusions that may have been set, or maybe it's set to only hand out IP's to domain PC's and the PC's requesting the IP aren't on the domain. Also, have you authorised the DHCP server, have you accidentally got two DHCP servers on you network set to the same IP scope.