22 replies
From the symptons you are describing it's something local on those pc's.
Do you have a current antivirus running on the servers (dhcp, emailserver if you have one) as well as on the clients ?
Leopold
by pheonix11
by vh_s
by pheonix11
by ebob
by pheonix11
by alciur22
All good answers. I would check the DHCP Server scope and subnet addresses. I would restart the DHCP service on server while all other workstations are logged off. Second, on each workstation I would remove any protocols that are unecessary to your network. Meaning, remove all but TCP/IP. check to make sure that all workstations are set to obtain and reboot. Make sure you have enough IP leases available.
AL
by pheonix11
by @lberto
That is a problem with your DHCP Server.
Check your scope if it has enough addresses and if it is a valid range.
After that, Log off all the workstations, stop the DHCP service on the server, take it down, start it up again, then start up the workstations. That should make it.
@lberto
by pheonix11
by vh_s
I am looking carefully at your question. Now I wonder, what do you mean by 'reimage'?
Did you mean that once WINIPCFG grayed out, they refused to work for always, or is it the case that WINIPCFG only now-and-then refused to work ?
vh_s
by pheonix11
by pheonix11
2 problems may lead to that situation.
1.- The dhcp scope is full. Check the dhcp server in order to find the scope if full. If yes, just extend it.
2.- When bringing machines to live from a ghost image, I recommends you to have the ghost image "PC NAME" and "Workgroup" to something like "GGHOST" and "GGGHOST". When booting a pc for the first time go to the pc properties and change the pc name and workgroup to something different. When many machines appears "illegally" with the same name in the network, the dhcp may reports that machine as registred.
Hope it helps!!
by pheonix11
by scviking
Sounds like your TCP/IP stack may be corrupted, not only on the computers, but possibly even on the drive image you're using to reimage the machines.
I work for a DSL provider, and the usual fix for this is to uninstall and reinstall the NIC drivers and all necessary protocols (sometimes just updating the NIC drivers works). Hope it helps- it's a lot faster than reimaging the machines.
by pheonix11
by vh_s
If that the case, I would check the TCP/IP.
Install NetBEUI just to retain network setting, remove TCP/IP from computer, restart, reinstall TCP/IP and remove NetBEUI, restart again.
The above wouldn't resolve the problem though, since the cause must be found externally (something like virus-activity).
by pheonix11
by drew_lgca
by pheonix11
by pheonix11
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending