Domain '<domain name>' does not exist

  • Thread starter Thread starter Carlitos
  • Start date Start date
C

Carlitos

Hi there,

I have read similar situations in this newsgroup, but I decided to post my
own problem just in case there are details that would make a difference.

I have a Win2k SP4 laptop that was a member of a domain. My laptop has been
working just fine for the past 2.5 years up until recently.

Since a month ago it started to have problems accessing the server's shared
folders (Error msg: "device already in use"). Also, it would not ping the
server ("host unknown") and other machines in the domain when in the past I
could.

However, I still could get into the internet, get my Outlook Express email
and news, and the network card is sending and receiving packets alright, so
I know the network card is ok.

I took it out of the domain and tried to get it back into it again just to
check if that would resolve the problem. Now the problem is worst! I
cannot get it back into the domain!

If I try to join the domain through the Network ID wizard (on My Computer's
Properties) I get this other error: "The domain name '<my domain>' is either
invalid or does not exist"

If I try to join the domain through Properties (on My Computer's Properties)
I get a more elaborated error message (which I believe it must be referring
to the same problem) saying "The following error occured validating the name
'<mydomain>'. This condition may be caused by a DNS lookup problem. For
information about troubleshooting common DNS lookup problems, please see the
following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=5171.
The specified domain either does not exist or could not be contacted."

It might be something related to DNS, as the error messages say, but I am
not quite sure. The reason I am in doubt is because the DNS and Alt DNS
that were specified in this machine and all other machines here point to
some external server (outside the office) that would resolve to access the
internet and all machines, except mine's, work just fine! Also, I have been
told that there are no DNS servers locally in this office and that I do not
need them to get a machine into the domain.

All other machines here are working just fine. They are part of the same
domain, their respective DNS configurations point to the mentioned external
servers, they can ping the office's server and any other machines in the
domain, they can access the server's shared folders, and they do not have
any problems at all. Mine's was working just fine configured this way.

I am desperate! I need help urgently! Thanks in advance!

C
 
Are you on a Win 2k domain or a NT 4.0 domain?
What Operating system are the other computers on the domain running?


DDS
 
Hi Danny,

The domain controller is a Win2k Server box. Mine's Win2k. Others' are
Win2k and WinXP. None here is WinNT 4.0.
 
A Win 2k domain MUST have a DNS server for AD. Is it possible the "external"
DNS server set on all other clients hosts the DNS records for your domain?

Who owns the "external" DNS server?

The DNS server for your domain hosts the SRV records AD clients MUST find in
order to join the domain.
When you boot your Win 2k server it attempts to update the DNS server listed
in the properties of TCP/IP with it's SRV records. *Usually* an ISP will not
allow this. Nor do you want your AD servers registering themselves in a
public DNS server. That is why you would need a DNS server for your AD
domain.
Clients pointing to a DNS server that does not hold the SRV records for the
domain will take a long time to log into the domain. Joining a client to the
domain with it pointing to a DNS server that does not have the SRV records
will result in errors about the domain not being found.
Opening "domain" related MMC consoles will give errors, take extra long time
to open. Group policy will not work.
Clients pointed to their ISP's DNS server instead of the DNS server that
hosts the SRV records for your domain will access the Internet with no
problems.
There are tons of problems associated with clients pointed to the wrong DNS
server. It does not sound like you are having this problem on your domain,
so I can only conclude that the "external" DNS server is owned by your
company and is hosting your DNS zone or there is another DNS server
*somewhere* on your network.
Here are a couple of links on the proper way to set up DNS for an AD domain.

How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



hth

DDS W 2k MVP MCSE
 
To answer your question: Yes, I found out that the DNS server that all
machines here point is to the web server we have, and the Alt DNS points to
our ISP's server.
Click to expand...

This could be your problem. The alternate DNS server pointing to your ISP.
All AD clients should point to your AD DNS server ONLY. To get Internet
access from your clients you should configure your AD DNS servers to forward
requests and list your ISP's DNS server as the forwarder. This is the ONLY
place your ISP's DNS server should be listed on your domain.
See:
How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Having your ISP's DNS server listed on the clients can cause just exactly
what you are seeing.

hth
DDS W 2k MVP MCSE

Carlitos said:
Danny,

Thank you very much for your input. You have answered several questions I
had.

To answer your question: Yes, I found out that the DNS server that all
machines here point is to the web server we have, and the Alt DNS points to
our ISP's server.

So far, I have solved the problem partially. I found out that a firewall
that was supposedly disabled (it was installed long time ago in this
machine) somehow got enabled again (I am still wondering how come that thing
got enabled by itself or who did it) and was preventing the machine to find
the domain controller. I uninstalled the firewall and got the machine back
into the domain.

There is still a problem in the machine, which was the original problem
described in my first message:

1. I cannot ping any of the other machines nor the server (returns "unknown
host").
2. I cannot get into the server's shared folders either (returns "Microsoft
Windows Network: The local device name is already in use.").
3. I cannot get the list of machines in the domain (net view command returns
"System error 6118 has occurred.").
4. I get an error if I try to access the domain through the explorer
(returns "<mydomain> is not accessible. The list of servers for this
workgroup is not currently available").
5. If I ping my machine itself, it returns "Pinging <mycomputername> [IP
address]" but immediately gives "Request timed out" messages.

What could be the problem?!?!? Please help.

Thanks in advance.

C


Danny Sanders said:
A Win 2k domain MUST have a DNS server for AD. Is it possible the "external"
DNS server set on all other clients hosts the DNS records for your domain?

Who owns the "external" DNS server?

The DNS server for your domain hosts the SRV records AD clients MUST
Click to expand...
find
in
order to join the domain.
When you boot your Win 2k server it attempts to update the DNS server listed
in the properties of TCP/IP with it's SRV records. *Usually* an ISP will not
allow this. Nor do you want your AD servers registering themselves in a
public DNS server. That is why you would need a DNS server for your AD
domain.
Clients pointing to a DNS server that does not hold the SRV records for the
domain will take a long time to log into the domain. Joining a client to the
domain with it pointing to a DNS server that does not have the SRV records
will result in errors about the domain not being found.
Opening "domain" related MMC consoles will give errors, take extra long time
to open. Group policy will not work.
Clients pointed to their ISP's DNS server instead of the DNS server that
hosts the SRV records for your domain will access the Internet with no
problems.
There are tons of problems associated with clients pointed to the wrong DNS
server. It does not sound like you are having this problem on your domain,
so I can only conclude that the "external" DNS server is owned by your
company and is hosting your DNS zone or there is another DNS server
*somewhere* on your network.
Here are a couple of links on the proper way to set up DNS for an AD domain.

How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



hth

DDS W 2k MVP MCSE



laptop
has
Click to expand...
worst!
I validating
the please
see
Click to expand...
but
I Alt
DNS point I
do in
the
Click to expand...
Click to expand...
 
I would update the NIC first. Then REMOVE all the lan
settings, reboot and then re install them. Your nic could
be faulty, dont overlook that.
 
Hello jazeal,

What's the NIC?

I have removed the user account from the domain controller and re-created it
(same username, password, privileges, everything). I logged on with this
recreated user account and got everything working fine EXCEPT that it
created a different profile in my machine. How can I recover the old
profile?

C
 
Back
Top