|
Home > Archive > General Discussion > November 2001 > The specified domain either does not exist or could not be contacted ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
The specified domain either does not exist or could not be contacted ?
|
|
|
| another litte problem in the life of ando ...
I can't seem to join 2 workstations to my win2k domain ? Every time I try and join them to the domain, I get the following error:
"The Following Error occured validating the name "My_Network_Domain_Name".
The specified domain either does not exist or could not be contacted" ?????
I am using DHCP on the workstation, all IP requirements are given including DNS. I can ping the server "Jordan" by using the FQDN as well as the Netbios name "jordan" from the workstation. I have the workstation on the same subnet as the Domain Controller (10.0.2.0/24). I have tryed out of desperation to install the NetBuei protocal on both the server and the workstation, but still no luck ???? What the hell is going on?
I've managed to install around 20 Win2k workstations onto the domain with no problem... I remember having this problem before, but nothing as serious as this.
When joining the domain, I've tryed using netbios as well as FQDN (domain & domain.com) and I have also tryed using Caps(DOMAIN & DOMAIN.com)
I've also manually created a computer account for the workstaion on the server, still no luck...
Does anyone have any ideas what I can do... Its stupid having a domain when I can't install any more workstations.
Actually, now that I think of it... could this be licencing ? | |
| depamo 2001-11-01, 12:32 pm |
| Most Microsoft products tell you when it is a licensing issue.
Feel your pain, seems that since you have the connectivity that the only other issue that could be in this would be an incorrectly typed in Microsoft Domain Name when you are adding the workstation, or WINS malfunction, policy restriction on the Server (this can be many different things), network filtering or ACL's (did you connect other computers in the same broadcast domain before??) or lastly is a lack of a client license with the Desktop Workstation OS and your server is setup with per seat licensing. Beyond that, there are pratically a million different settings in 2K that will effect its ability to logon to a network correctly.
Is this a laptop that you are installing this on with PCMCIA network cards?? and were they inserted when you installed the OS?? There are some problems that look like this with laptops and PCMCIA network adapters. | |
|
| This is getting more serious... Now when ppl logon to the server with roaming profiles, the error appears:
'There are currently no logon servers available to complete your logon request. You are being logged on with your local profile.'
Now, the only real thing that has been done to the network since all this started was:
1) ACT database software was installed
2) winfax software installed
3) Connected this network to another via leased line (Two seperate domains) | |
| Joe Blacke 2001-11-02, 7:40 am |
| I would really check your DNS server, and make sure that the service records for your domain controller are being registered. | |
|
| quote:
and make sure that the service records for your domain controller are being registered
how do i do this ?
Another person did the linking of this network to another and was configuring static routes for the server by using the (route add 10.0.0.0 MASK 255.255.255.0 10.0.2.10) comand prompt. I wonder if this is stopping the workstations from seeing the server as a domain controller ?
Can someone point me to a site where it shows exactly how a worstation is authenticated by a DC ?
None of the computers are now seeing the server as a Domain controller ????  | |
| Joe Blacke 2001-11-02, 10:31 am |
| Ando,
Windows 2000 clients in a 2000 domain authenticate by by first contacting a DNS server to locate a service record and A pointer record for a domain controller. The DNS server must support service records (2000 DNS, or Bind 8.1.2). If the DNS server doesn't have the service record for a domain controller, then the client tries to contact a WINS server to locate the DC. If no DC record exists on the WINS server, or if no WINS server is available, then the client tries to find a DC via a broadcast.
Now, if your clients are getting their addresses via DHCP, make sure that they receive the proper DNS server as one of their scope options. Make sure the DNS server is up and pingable.
Now, for the DNS server is it Windows 2000? Is it a primary, secondary, or AD integrated? The zone must be configured for support of service records, and preferablly for dynamic updates. If the DNS server doesn't support dynamic updates, then you have to manually enter the service records. If the server supports dynamic updates, you can stop and restart the netlogon service on the domain controller to try and reregister the service records (net stop netlogon net start netlogon).
On the DNS server it should have records for MSDCS, sites, TCP, and UDP under the zone for your domain. | |
|
| quote:
Originally posted by Joe Blacke
for the DNS server is it Windows 2000? Is it a primary, secondary, or AD integrated?
DNS is Active Directory Integrated (the DNS server is also the Domain controller)
quote:
The zone must be configured for support of service records, and preferablly for dynamic updates.
I'm having a look at that now 
quote:
On the DNS server it should have records for MSDCS, sites, TCP, and UDP under the zone for your domain.
Yes, it does have them already | |
| Joe Blacke 2001-11-02, 1:51 pm |
| Are the clients on the same subnet as the domain controller? Have you tried setting one of them to a static IP, and static setting for DNS server? Are the clients pointed to the domain controller that hosts the DNS zone, or a second dns server? If the first DNS server is also a domain controller (with AD integrated zones), are all the rest of the DNS servers domain controllers, and are they set up with AD integrated zones? If they are not domain controllers, or if they are domain controllers but without AD integrated zones, you may have configured two different zones (one primary zone of a DNS server and one AD integrated zone) and these two zones will not replecate information with each other. | |
|
| quote:
Originally posted by Joe Blacke
Are the clients on the same subnet as the domain controller?`
Yes
quote:
Have you tried setting one of them to a static IP, and static setting for DNS server?
Yes
quote:
Are the clients pointed to the domain controller that hosts the DNS zone, or a second dns server?
They are all pointed at the DC that hosts the DNS zone
There is only the one DC and the one DNS server in the entire domain.
Actually, somthing I've noticed... when I go into AD Users and computers, and right click the domain, then open group policy, an error pops up saying that the domain 'nets.ie' is unavailable or that there is no Domain controllers available ?
It just seems that even though i can ping 'nets.ie' from any command prompt on any workstation, it still cannot communicate with it on another level ?
damn, I'm starting to think its a software conflict or something like that ? | |
| Joe Blacke 2001-11-05, 11:42 am |
| Are there ANY errors in event viewer? Did you stop any services in computer management or the services mmc? |
|
|
|
|