Problem Connecting to AD domain From Client PC running Win2K or XP

[CP]

Hi guys,

I have a new AD domain called "ABCdomain". Everything went smoothly during
the setup. Now I have a problem for the client to be connected to the AD
domain. The error shown as follows:

'The following error occrred attatempting to join domain "ABCdomain"
The network location cannot be reached. For information about network
troubleshooting, see Windows Help.'

or

'Network path not found. '

The solution from Microsoft was to enable "TCP/IP NetBIOS Helper Service" in
services.msc. I checked and this was enabled by default. I was make sure
that in my TCP/IP setting, i have chosen "Enable NetBIOS over TCP/IP".

However, I still get this erorr message..

How should I get rid of this error? Is there anything else I need to check?
I ever tried AD domain successfully before this, but due to some error i
formatted the HDD and reinstalled OS and AD all over again.

Please help and advise. I would very much appreciate it !!

regards,
CP

 

[tg]

ensure dns is running in AD mode and your users are
registering themselves with dns. If that doesn't work,
set up wins on your AD server and point the clients to
it.

 

[CP]

My dns is running, but i have not installed WINS. How do i install Wins?

 

[CP]

Tg,

I have installed both DNS and Wins, but my notebook and other pcs still
can't get connected to AD domain.
Any other solution to this problem? btw i have also disable my personal
firewall..

Thanks in advance.

 

[Cary Shultz [A.D. MVP]]

CP,

Installing WINS is not necessarily the answer.

This is most probably a problem with DNS. As you become more familiar with
WIN2000 you will notice that DNS is almost always involved - somehow!

Anyway, let's first ensure that your internal domain is something like
'ABCDomain.com' or 'ABCDomain.local' and not just 'ABCDomain'. This is
known as a single-label domain and it is not very pretty!

If it is a single-label domain, then let us know so that we can follow that
path.

If it is not a single-label domain, let's take a look at your internal DNS.
Assuming that you are running DNS on a WIN2000 Server are you allowing
dynamic updates? Also, do you have - under the Forward Lookup Zone - all
four subfolders ( _msdcs, _sites, _udp and _tcp )? Assuming yes, are they
populated?

How are your client workstations getting their IP Address lease? Are you
running DHCP on a WIN2000 Server or on a 'network device'? Did you
configure the Options ( Option 003, Option 006 and Option 015 if running
DHCP on WIN2000 )? In other words, do your clients have all of the
following: IP Address, Subnet Mask, Default Gateway | Internal DNS Server
IP Address. The key is that your clients have only the internal DNS
information here. You ISP DNS Server information does not belong here -
that belongs in the Forwarders tab in your FLZ.

Please take a look at the following two MSKB Articles:

http://support.microsoft.com/?id=247811
http://support.microsoft.com/?id=314861

HTH,

Cary

 

[tg]

go to add remove programs-->add windows components and go
to the networking, there you will see things such as
dhcp, wins, dns etc. Also make sure everyone is on the
same network scope.

 

[CP]

Hi Cary,

Thanks you so much for your advise. Btw, I configured my domain as a
Single-lable domain / 'ABCDomain' and I'm using ISP DNS and one of our linux
DNS server which is currently no host in my work place. So i guess probably
the 'external DNS' is causing the problem. If it is so, shall I use the
Win2000 AD-integrated DNS IP address instead? I will find out again once I
reach office tomorrow.

As for DHCP, we used a "network device" to distribute a range of IPs. It
works well so far by providing IP add, subnet mask, default gateway and our
own DNS address in linux platform.

I will study the links recommended by you thoroughly. Thanks again =)

 

[CP]

Hi Cary,

I configured my notebook to point to the AD-integrated DNS ip and it works
now. I'm able to joined "ABCdomain" now.
I still have a question here, do I continue to use that DNS ip for DHCP
clients?

Thank you so much for the great help that has enlightened me !

CP

 

[Cary Shultz [A.D. MVP]]

CP,

Yes! All of your clients must point to your internal DNS Server(s) only.
The only place for your ISP's DNS Server information is in the Forward
Lookup Zone in your internal DNS......

However, there is still potentially an issue. You have clearly stated that
you have a single-label domain name. If it is not too late you might want
to consider doing something about that.

Please take a look at the following MSKB Articles:

http://support.microsoft.com/?id=300684
http://support.microsoft.com/?id=826743

These would be two articles to consult if you start having problems....

HTH,

Cary