Win2k Domain Controller problem
Discussion
Anyone ever had a problem with the printer pruning service on a Win2K domain controller?
We have 8 DC's 7 of which are fine, one of them however is constantly deleting all the published printers out of AD, the event logs show this occuring (event ID 50's source print) & suggest the printers/server publishing these cannot be contacted.
Thing is nobody here can see any reason at all why this should be happening as the print servers & printers can all be reached without problems from the problem domain controller when we test the connection, we can find no DNS issues, WINS or network connectivity issues so cant explain why this is happening.
Microsoft seem to have never had the problem before judging by the total lack of any sort of documentation or article refering to a similar problem, all they have is a worthless article that suggests the DC has been disconnected which is certainly not the case as all other services on it are running flawlessly.
Disabling the spooler on the problem DC stops this occuring but it would be nice to have an explanation & a fix for it.
Anyone seen this before?
We have 8 DC's 7 of which are fine, one of them however is constantly deleting all the published printers out of AD, the event logs show this occuring (event ID 50's source print) & suggest the printers/server publishing these cannot be contacted.
Thing is nobody here can see any reason at all why this should be happening as the print servers & printers can all be reached without problems from the problem domain controller when we test the connection, we can find no DNS issues, WINS or network connectivity issues so cant explain why this is happening.
Microsoft seem to have never had the problem before judging by the total lack of any sort of documentation or article refering to a similar problem, all they have is a worthless article that suggests the DC has been disconnected which is certainly not the case as all other services on it are running flawlessly.
Disabling the spooler on the problem DC stops this occuring but it would be nice to have an explanation & a fix for it.
Anyone seen this before?
Do a search in the PH archives, I posted link to a Technet article about this previously.
IIRC, you can disable this feature (Domain Controllers will automatically delete published printers if they cannot resolve their names/see them on the network by default).
It won't be an AD replication problem as such, though I'd attempt doing some basic tests from the domain controller which is logging the events (like attempting to connect to the printer using whatever path is published from the DC itself as a starting point).
D
IIRC, you can disable this feature (Domain Controllers will automatically delete published printers if they cannot resolve their names/see them on the network by default).
It won't be an AD replication problem as such, though I'd attempt doing some basic tests from the domain controller which is logging the events (like attempting to connect to the printer using whatever path is published from the DC itself as a starting point).
D
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff