Client cant Join Domain

  • Thread starter Thread starter news
  • Start date Start date
N

news

Hi all, at present I am having problems joining a fifth Win2k Pro Client to
the Domain. At each attempt at joining the domain I am met with the
following message.



"The following error occurred when attempting to join "domain name". "The
network path was not found"



Also it can take current users from 10 to 20 minutes to logon and if they
try to change there own password, the error message below is displayed.



"The network path was not found"





If I log on locally I can see the network via network neighbourhood, and the
other four clients can log on so there is no physical problem.



I have a feeling this is DNS related,can anyone offer any advice?







Current set up





2 Servers



Server 1 (Domain Controller)

-------------------------------------------------------------





Windows 2000 Advance Server

Active Directory

DNS Server

DHCP Server Issuing the following

Scope 10.1.1.1 to 10.1.1.200, Subnet 255.255.255.0

Default gateway 10.1.1.200

DNS Server 10.1.1.254



1 x Nic - Static

IP Address 10.1.1.254 Subnet 255.255.255.0

Default Gateway 10.1.1.200



Log on





Server 2 (Internet Gateway)

-------------------------------------------------------------



Windows 2000 Advance Server

2 x Nics

Nic 1 IP/Subnet/Gateway all assigned by ISP



Nic 2 (Assigned by Server 1)

IP Address 10.1.1.200 Subnet
255.255.255.0

Default gateway 10.1.1.254

DNS Server 10.1.1.254







4 Clients

-------------------------------------------------------------



Windows 2000 Pro

Nic (Assigned by Server 1)

IP Address 10.1.1.(1 - 20) Subnet 255.255.255.0

Default gateway 10.1.1.200

DNS Server 10.1.1.254







Fifth Client

-------------------------------------------------------------



Windows 2000 Pro

Nic (Assigned by Server 1)

IP Address 10.1.1.(1 - 20) Subnet 255.255.255.0

Default gateway 10.1.1.200

DNS Server 10.1.1.254



Thanks in advance for all your help



Paul.
 
In
Hi all, at present I am having problems joining a fifth
Win2k Pro Client to the Domain. At each attempt at
joining the domain I am met with the following message.

"The following error occurred when attempting to join
"domain name". "The network path was not found"

Also it can take current users from 10 to 20 minutes to
logon and if they try to change there own password, the
error message below is displayed.

"The network path was not found"

If I log on locally I can see the network via network
neighbourhood, and the other four clients can log on so
there is no physical problem.
Click to expand...


From what I can tell all your client seem to be configured correctly, the
problem may be with your domain controller or domain. Can you please post
all of the following?

ipconfig /all (unedited)
domain name from ADU&C
listing of Forward lookup zones in DNS

The ipconfig /all has your primary DNS suffix, that suffix must match your
domain name in ADU&C and there must also be a Forward Lookup Zone in DNS for
that name. Additionally, if the domain name is a single-label name, the DC
cannot register its records and the clients cannot find the DC by domain
name.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684

826743 - Clients cannot dynamically register DNS records in a single-label
forward lookup zone: http://support.microsoft.com/?id=826743

257623 Domain Controller's Domain Name System Suffix Does Not Match Domain
Name
http://support.microsoft.com/?id=257623
 
Also, look at the TCP/IP properties on the 5th client and make sure you
uncheck the "use lmhosts" option. then reboot and retry.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
Hi thanks Kevin and Deji, for your info and links.

On reading your info I realised that one of my main problems is that I have
a single label domain "companyname" with no .local. My forward lookup zones
where completely empty. no domain name or _msdcs.

I also had LMHost ticked under IP/Win Property's

Is there anyway to change this to a Company.Local without losing client
account info on the domain Controller?

Thanks for your help

Paul
 
In
Hi thanks Kevin and Deji, for your info and links.

On reading your info I realised that one of my main
problems is that I have a single label domain
"companyname" with no .local. My forward lookup zones
where completely empty. no domain name or _msdcs.

I also had LMHost ticked under IP/Win Property's

Is there anyway to change this to a Company.Local without
losing client account info on the domain Controller?
Click to expand...

Unfortunately, you cannot rename a Win2k domain, that option is available in
Win2k3. There is two ways you can fix this and save the accounts.
One is to add an NT4 BDC to the domain (if still in mixed mode) then
promote the NT4 BDC to PDC, upgrade it to Win2k DCPROMO it to a Domain
controller using the domain name company.local
The other is to build a new Win2k DC with the correct name and use ADMT to
migrate the accounts.
The major disadvantage to the second option is you have to use a different
NetBIOS domain name.
 
Back
Top