Server Joining to Domain...Urgent

Dear All,

We are facing issue with one of our Windows 2003 member server. The server
is a part of Domain but suddenly we are not able to login to the server using
any of the domain account it gives the error " Domain Controller is either
down or not available".
We have logged in locally to the Server and checked that we are able to ping
the Domain, Netbios over TCPIP is enabled, TCP netbios helper service is
started. Did ipconfig /flushdns, registerdns. Also made static entry for the
Domain Name in the Host file but the problem is still there.
We cannot disjoin and rejoin the server to domain because of Application
constraint.
Please let me know if anything can be done to get it resolved without
disjoining/rejoining it to Domain.

Thanks and Regards,
Sukhwinder Singh

Howdie!

Sukhwinder Singh schrieb:
> We are facing issue with one of our Windows 2003 member server. The server
> is a part of Domain but suddenly we are not able to login to the server using
> any of the domain account it gives the error " Domain Controller is either
> down or not available".

Is the computer account still valid?
If you are sure it is not a DNS issue, I'd start a network trace and see
whether I could gather information from there.

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste

"Sukhwinder Singh" <SukhwinderSingh@discussions.microsoft.com> wrote in
message news:3BE95D80-8B19-473F-8663-906235CF73E7@microsoft.com...
> Dear All,
>
> We are facing issue with one of our Windows 2003 member server. The server
> is a part of Domain but suddenly we are not able to login to the server
> using
> any of the domain account it gives the error " Domain Controller is either
> down or not available".
> We have logged in locally to the Server and checked that we are able to
> ping
> the Domain, Netbios over TCPIP is enabled, TCP netbios helper service is
> started. Did ipconfig /flushdns, registerdns. Also made static entry for
> the
> Domain Name in the Host file but the problem is still there.
> We cannot disjoin and rejoin the server to domain because of Application
> constraint.
> Please let me know if anything can be done to get it resolved without
> disjoining/rejoining it to Domain.
>
> Thanks and Regards,
> Sukhwinder Singh
>
>


I agree with Florian to look at DNS. Specifically, what DNS address is on
the workstation, and what is the IP of the DC?

Do not use hosts entries. They do not work with AD, and neither does
NetBIOS. That was from the old NT4 days.

FYI, AD uses DNS to "find" the domain. It queries for the SRV records to
find this info (The yellow folders with the underscores in the names).

Things that can cause issues:

1. Using your ISP's DNS server IP address, the router as a DNS address, or
some other external DNS server's IP address in any internal AD machine's IP
configuration (DCs, workstations, etc). If the machines have been configured
as such (whether static or DHCP), the machines will be asking those DNS
server, 'Where is my domain controller." Unfortunately, these external DNS
servers have no idea where your domain controllers are in your internal
network, therefore the connection fails.

2. If the domain controllers are multihomed (more than one NIC that are not
teamed, and/or IP adresses), and/or if RRAS is installed, it will cause
problems with AD-client and other domain communications.

Please post an ipconfig /all of the workstation and of your DC, and we can
evaluate the configurations and make recommendations and suggestions as
necessary.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Hello Sukhwinder,

I agree with the others about DNS or maybe multihomed machines. So the ipconfig
/all output is the easiest way to check that everything is really ok.

If you are using the private ip addresses 10.x.x.x, 172.x.x.x or 192.168.x.x
there is no problem to post them here, they are not accessible from the internet.
For domain names/server names you can choose different ones, but make sure
to keep the same format, like DOMAIN or DOMAIN.COM

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Dear All,
>
> We are facing issue with one of our Windows 2003 member server. The
> server
> is a part of Domain but suddenly we are not able to login to the
> server using
> any of the domain account it gives the error " Domain Controller is
> either
> down or not available".
> We have logged in locally to the Server and checked that we are able
> to ping
> the Domain, Netbios over TCPIP is enabled, TCP netbios helper service
> is
> started. Did ipconfig /flushdns, registerdns. Also made static entry
> for the
> Domain Name in the Host file but the problem is still there.
> We cannot disjoin and rejoin the server to domain because of
> Application
> constraint.
> Please let me know if anything can be done to get it resolved without
> disjoining/rejoining it to Domain.
> Thanks and Regards,
> Sukhwinder Singh