Hi there,
Firstly apologies if I've put this in the wrong forum.
We have a small Windows Server 2003 AD network of about 15-20 PCs and up until 2 weeks ago everything was running fine.
Then, the server delegated with the task of DHCP crashed, and although booted up fine and the service reported to be running fine it would no-longer delegate IPs to all the devices on the network. In the short term we went about manually setting the IP settings for each PC and that solved that issue, and since then we have installed a new device which has taken over the role as DHCP and is functioning fine.
However, since that crash a number of PCs have been unable to validate with the AD controller and log on to the network with cached credentials.
1) Initially I thought it might be corrupted TCP stacks so downloaded the Winsock fix but that made no difference.
2) Secondly I tried removing devices from the network and re-adding them, interestingly when adding them back on to domain the event log reported successful appliction of group policies, but then on reboot and attempting to log in again it would report that no logon servers were available to service my request (even on the administrative account that I used to authorise the computer to join the network).
3) I then tried "Reset account" by logging on the AD machine, going in to the computers tree and right-clicking the named machine (and then re-adding the computer to the network).
4) Finally I tried physically deleting the device from the computers tree and re-adding it.
No success on any of these.
The AD and DNS machines all have static IPs that are reserved by the DHCP device, so it will not delegate those IPs to any other machine on the network, and the DHCP device also successfully passes this information to all machines it dishes out IPs to.
Furthermore, on the machines that are failing, pinging the AD machine and DNS machines by both IP and name results in a response (and I can remote desktop on to the machines).
I'm a bit baffled by it; about 40% of the machines in the office are affected by this issue and there's nothing about these machines that makes them different from the ones that are working - all are of the same spec and have the same OS (XP Pro) and applications installed.
I'm not near the computers right now but I can post event log information if need be (though it's the usual "No logon servers available at this time" and the AD machines are not reporting any errors), but I've already gone through the arduous task of reading people's comments on eventid.net and attempting their solutions.
Does anyone have any immediate thoughts on other solutions I can try?
Thanks for any help.
Firstly apologies if I've put this in the wrong forum.
We have a small Windows Server 2003 AD network of about 15-20 PCs and up until 2 weeks ago everything was running fine.
Then, the server delegated with the task of DHCP crashed, and although booted up fine and the service reported to be running fine it would no-longer delegate IPs to all the devices on the network. In the short term we went about manually setting the IP settings for each PC and that solved that issue, and since then we have installed a new device which has taken over the role as DHCP and is functioning fine.
However, since that crash a number of PCs have been unable to validate with the AD controller and log on to the network with cached credentials.
1) Initially I thought it might be corrupted TCP stacks so downloaded the Winsock fix but that made no difference.
2) Secondly I tried removing devices from the network and re-adding them, interestingly when adding them back on to domain the event log reported successful appliction of group policies, but then on reboot and attempting to log in again it would report that no logon servers were available to service my request (even on the administrative account that I used to authorise the computer to join the network).
3) I then tried "Reset account" by logging on the AD machine, going in to the computers tree and right-clicking the named machine (and then re-adding the computer to the network).
4) Finally I tried physically deleting the device from the computers tree and re-adding it.
No success on any of these.
The AD and DNS machines all have static IPs that are reserved by the DHCP device, so it will not delegate those IPs to any other machine on the network, and the DHCP device also successfully passes this information to all machines it dishes out IPs to.
Furthermore, on the machines that are failing, pinging the AD machine and DNS machines by both IP and name results in a response (and I can remote desktop on to the machines).
I'm a bit baffled by it; about 40% of the machines in the office are affected by this issue and there's nothing about these machines that makes them different from the ones that are working - all are of the same spec and have the same OS (XP Pro) and applications installed.
I'm not near the computers right now but I can post event log information if need be (though it's the usual "No logon servers available at this time" and the AD machines are not reporting any errors), but I've already gone through the arduous task of reading people's comments on eventid.net and attempting their solutions.
Does anyone have any immediate thoughts on other solutions I can try?
Thanks for any help.