Hyper-V Virtual guest server fail to login domain every time
Operating System: Windows 2003 Enterprise R2
Virtualization Role: Virtual Guest
Virtualization Technology: Hyper-V
Issue:
Each time login to the server prompt an error domain not available or Not enough storage is available to process this command.
Upon checking in event log i found below info:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
User: N/A
Description:
This computer was not able to set up a secure session with a domain controller in domain due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
Virtualization Role: Virtual Guest
Virtualization Technology: Hyper-V
Issue:
Each time login to the server prompt an error domain not available or Not enough storage is available to process this command.
Upon checking in event log i found below info:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
User: N/A
Description:
This computer was not able to set up a secure session with a domain controller in domain due to the following:
Not enough storage is available to process this command.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
How many HD space left on the boot drive?
ASKER
Used space: 14.7 GB
Free space: 18.2 GB
Even we tried apply the fix as :
http://support.microsoft.com/kb/312362. Stll having the issue
Free space: 18.2 GB
Even we tried apply the fix as :
http://support.microsoft.com/kb/312362. Stll having the issue
ASKER
The issue will resolve when each time we reboot the server, then we able to login the server without any issue...... seems the server in roduction we cannot reboot the very frequest......... any solution to fix this permanenet.........
Hi,
How many DCs are in network? Please post Ipconfig /all from your DCs (unedited).
Also make sure that:
1. Each DC / DNS server points to its private IP address as primary DNS server and other internal DNS servers as secondary ones
2. Each DC has just one IP address
3. Contact your ISP and get valid DNS IPs from them and add it in to the forwarders, Do not set public DNS server in TCP/IP setting.
4. Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.
Regards,
Abhijit Waikar.
How many DCs are in network? Please post Ipconfig /all from your DCs (unedited).
Also make sure that:
1. Each DC / DNS server points to its private IP address as primary DNS server and other internal DNS servers as secondary ones
2. Each DC has just one IP address
3. Contact your ISP and get valid DNS IPs from them and add it in to the forwarders, Do not set public DNS server in TCP/IP setting.
4. Once you are done, run "ipconfig /flushdns & ipconfig /registerdns", restart DNS and NETLOGON service each DC.
Regards,
Abhijit Waikar.
Also post,
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)
Regards,
Abhijit Waikar.
dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)
Regards,
Abhijit Waikar.
ASKER
Hi Abhijit, i quite not understand on the second command ( repadmin /showrepl dc* /verbose /all /intersite) and thrid command ( dnslint /ad /s "DCipaddress" ). Can you provide with some examples. What did means dc* and "dcipaddress"
ASKER
Dear Abhijit, so far for the DNSLint output result, i got below result. meanwhile i deleted those ip which is confidential for my company.
DNSLint will attempt to verify the
DNS entries used in AD replication
Using 127.0.0.1 for LDAP
Starting with for DNS
This process may take several minutes to complete.........
LDAP query to speficied LDAP server on TCP port 389 failed
Server Down
LDAP query to speficied LDAP server on TCP port 389 failed
LDAP server specified appears to be down
Specify a different LDAP server and run the command again
DNSLint will attempt to verify the
DNS entries used in AD replication
Using 127.0.0.1 for LDAP
Starting with for DNS
This process may take several minutes to complete.........
LDAP query to speficied LDAP server on TCP port 389 failed
Server Down
LDAP query to speficied LDAP server on TCP port 389 failed
LDAP server specified appears to be down
Specify a different LDAP server and run the command again
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Excellent troubleshooting method provided