The system cannot log you on now because the domain is not availab

[Guest]

When I first join this Windows XP Professional SP2 to the Windows 2000 domain
controller it works proprely. After a shut down or restarted it keeps giving
me the following error message "The system cannot log you on now because the
domain X is not available." I have a linksys router handling DHCP so I do not
have DNS or DHCP running on the domain controller. I have searched all over
the internet and I can not figure out why this is not working. All of the
other computers on the network run Windows 2000 and connect.

Please help me!

 

[Robert L [MS-MVP]]

this may help, quoted from http://www.ChicagoTech.net
Event ID 5719 - The system cannot log you on now because the domain "name" is not available."
Symptoms: when attempting to logon a domain, you keep getting an error that "The system cannot log you on now because the domain "name" is not available." Also, Event viewer shows Event ID: 5719. No Windows NT or Windows 2000 Domain Controller is available for domain <domain name>. The following error occurred: There are currently no logon servers available to service the logon request.

Resolutions: One possible cause of this error is that you have run out of buffer space in the NetBT datagram buffer. To resolve this problem, increase the MaxDgramBuffering value from 128 KB to 256 KB. Run Regedt32.exe, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters. On the Edit menu, click Add Value, and then add the following information:

Value Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000


Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

When I first join this Windows XP Professional SP2 to the Windows 2000 domain
controller it works proprely. After a shut down or restarted it keeps giving
me the following error message "The system cannot log you on now because the
domain X is not available." I have a linksys router handling DHCP so I do not
have DNS or DHCP running on the domain controller. I have searched all over
the internet and I can not figure out why this is not working. All of the
other computers on the network run Windows 2000 and connect.

Please help me!

 

[Guest]

Log on Locally
From a DOS promp type 'net view /domain:<your domain name>'
Can the PC see the domain ?

Try putting the PC in a workgroup, reboot and try to join the domain again.

Regards,

TimH

 

[Ron Lowe]

When I first join this Windows XP Professional SP2 to the Windows 2000
domain
controller it works proprely. After a shut down or restarted it keeps
giving
me the following error message "The system cannot log you on now because
the
domain X is not available." I have a linksys router handling DHCP so I do
not
have DNS or DHCP running on the domain controller. I have searched all
over
the internet and I can not figure out why this is not working. All of the
other computers on the network run Windows 2000 and connect.

Please help me!

Your DNS configuration is wrong.

Your win2000 domain MUST have a DNS server.
It's a central pillar of a win2k domain.
Even if you did not set it up explicitly, then the dcpromo wizard
did when you created the domain.

Go to theDomain Controller, and look under Administrative Tools.
You should see the DNS service listed here.

For XP clients to find the domain, they query DNS.
So they MUST point to the domain's DNS server.

Go to the router's DHCP page and configure it to issue the
DC's IP address as DNS server.

The older 2k machines 'work' because they are less sensitive to this
misconfiguration.
They will try NetBIOS name resolution as well as DNS.

Here's my usual lecture on this topic:

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers:

HOWTO: Remove the Root Zone (Dot Zone)
http://support.microsoft.com/default.aspx?kbid=298148

The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202





--
Best Regards,
Ron Lowe
MS-MVP Windows Networking

--