Does it have an SiS900 NIC?
When I reinstall XP on diffrerent computer everything works correctly - internet, printers, network drives - except group policy. This happens everytime and is not a problem on any other machine that haven't been reinstalled.
Event ID: 5719
"No Domain Controller is available for domain CCDOMAIN due to the following:
There are currently no logon servers available to service the logon request."
Event ID: 1054
"Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted."
Any suggestions ?
Does it have an SiS900 NIC?
Flush the DNS resolver?
we had this problem with some new machines we bought. installed windows xp, everything went fine, they were great but group policy didn't apply when our users tried logging on to them. Exact same error message as you are getting.
Two weeks of hair pulling and desk thumping ensued then *blam* the problem went away by itself and has never resurfaced.
i suspect dns caching issues of some sort, but it's still a mystery. i'd love to know what causes this though, as several weeks of usenet trawling turned up nothing useful.
I had just this problem with a load of Viglen PCs (which had the SiS 900 NIC). I had to make the following registry change...
reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v GpNetworkStartTimeoutPolicyValue /t REG_DWORD /d 60
I had a similar problem. I had to delete the computer from the AD, as it seemed to remember the NIC belonged to a computer with a different name.
(Thats how I interpreted it!!)
Yes it is a SIS900 NIC.
The reg key kinda worked, I still get the error messages but it says applying network settings now (well sometimes, not always) and also the software is being pre installed before login which wasn't happening before
I've tried to flush dns and deleting the computer name from active directory and deleting ip from dchp and dns before taking it off the network. then adding it back on with a totally different name but it still happens.
I have had a similar problem with a marvell yukon NIC. As far as I could work out, it is a driver issue. The NIC driver was starting tcpip too late for windows, causing this error. A driver update fixed the issue on all the affected machines. It might be due to the order in which windows starts the relevant services.
Does a susequent manual gpupdate /force complete sucessfully? You can always try the latest drivers for the card.
Roll back to the W2K or NT4 drivers. I have found this work for unstable NICs before.
Sounds like a driver issue. We have some RM all in ones with those NICs. Ghost runs like a dog with them 10Mb - 15Mb transfer rate.
Also, look closely at the date/times of events in the system/application log. when I had this problem, the events recorded had time stamps which appeared to be out of sequence!!!
There are currently 1 users browsing this thread. (0 members and 1 guests)