No domain controller available after SP3
A colleague and myself installed SP3 on our work PC's. However, after the install we both had problems accessing network shares and printers. A look in the event log revealed the following problem, which I guess is the cause :
No Domain Controller is available for domain **** due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.
Event 5719
My colleague has uninstalled the service pack and the problem has disappeared.
Any suggestions?
Cheers,
Lee
Alle Antworten
- Hi,
It seems its a know issue this might be the fix
open regedit after installing service pack 3 and make these changes.
Before making any changes make sure you backup the registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters
Add Value name MaxDgramBuffering as a type REG_DWORD and set the data value to 0x40000 (256K), using the Hex radix. The default for this Value Name is 0x20000 (128K) and the range is 0 - 0xFFFFFFFF.
Restart the netlogon service.
Regards
Deepak Hi Deepak,
Thanks for the quick response. I have made the change you suggested but I'm still getting the error in the event log after the NetLogon service is stopped and started. Below is the addition as shown in RegEdit just so you can check it's correct.
Name : MaxDgramBuffering
Type: REG_DWORD
Data : 0x00040000 (262144)
Also, in the days since the upgrade, the following two issues have started to appear in the event log
The Security System detected an attempted downgrade attack for server cifs/*****. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)". EVENT 40960
The Security System could not establish a secured connection with the server cifs/*****. No authentication protocol was available. EVENT 40961
Regards,
Lee
- Hi,
Did you restart the computer after making changes to the registry. Check the file and print sharing protocol is installed.
Do you have any security software on the computer.
Also during upgrade process was the security software on or disabled.
and the last question ????
Do you have norton? Yes, the PC was restarted after the registry change. At the beginning of this issue, I thought my network password had simply expired so I had it changed. However, when logging onto my machine, the new password isn't accepted and I continue to log onto the machine using my original (presumably cached) password.
File and print sharing protocol is installed and running. No third party firewall software installed on PC, just local e-trust anti-virus software. No Norton apps on the machine. Very simply build, just XP, Office, IBM Sametime & Lotus Notes.
I wasn't sure in the beginning if the service pack was to blame, but when my colleague was experiencing exactly the same problems, but then had none once the pack was removed, it became apparent what was causing the issue.
Lee
- .
LeeRichards wrote: Yes, the PC was restarted after the registry change. At the beginning of this issue, I thought my network password had simply expired so I had it changed. However, when logging onto my machine, the new password isn't accepted and I continue to log onto the machine using my original (presumably cached) password.
Is the machine under correct domain check that . Can you check whether services are started.
Check this kb
http://support.microsoft.com/kb/314861
nltest /dsgetdc:domainname Thanks for all the advice Deepak. However, before reading your last reply I decided my best course of action would be to uninstall SP3. Upon doing that, my new password was immediately recognised upon logon, and my network drives and network printers were all immediately available to me again. I'm pretty certain all my domain information was correct as it worked fine prior to the SP3 installation, and after now that I've removed it again.
Removing the service pack also resolved another quirky problem. On SP2 I was able to connect to my IBM Sametime chat client either connected directly to the 3rd party company whose network I'm directly connected to, and when connected via VPN to my own company network. With SP3 loaded, I could ONLY connect when I was connected to my company network via VPN even though my Sametime client should be accessible via any internet connection. After removing SP3, I now no longer need to be connected via VPN for Sametime to connect. Weird.
Thanks again,
Lee
- Hi,
Sorry buddy the issue is still not resolved but someone else might have a resolution for your issue. Hi Lee,
Your machine must be part of say Domain X before you install SP3.right??
so..after installation are you unable to access shares in Domain X??
or the problem is only with accessing other domains??
Thanks,
Ram
Hi Ram,
Some of our tech guys have identified the problem as being : There is an issue with SP3 and the DHCP server suppling DNS / WINS / Gateway information. It appears that this is an issue with QIP (Lucent) and SP3. The temp fix is to manually enter the appropriate DNS / WINS / Gateway information, although I haven't tried it myself yet as I haven't had an opportunity to re-install SP3.
Thanks,
Lee
Hi Lee,
Also try "nltest /dsgetdc:[Domain Name]".
nltest comes along with Windows XP Support Tools.
You can download it from http://www.microsoft.com/downloads/details.aspx?familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en
nltest overview: http://technet2.microsoft.com/windowsserver/en/library/ea7f8494-ee1e-4d99-b28f-8f2fd8a72df21033.mspx?mfr=true
Regards,
Ram
Hi Lee,
I had an XP SP2 box joined to a Domain.
And i am able to access the shares.
Now i installed XP SP3.
And still i am not seeing any problem w.r.t accessing shares.
I am not using QIP.
Apart from QIP, What could be difference in our setups??
Regards,
Ram
Hi Lee,
Guess I may be of some help. Please provide the scenario details as below:
a) Is the file share present on Sp3 box?
b) What is the OS on the machine from which the share is being accesed?
c) Are the machines joined to Windows Domain or are part of Workgroup? If both are joined to the Domain, is there a trust between the two Domains?
d) What credentials you want to access the shares from ( as local user on the machine having the share or domain user?)
Cheers!!
