Windows 2000 Domain controller and AD /DNS with Windows XP clients

  • Thread starter Thread starter XdriveX
  • Start date Start date
X

XdriveX

guys , i need a little help over here

Here is the situation :

i have speedstream router , DHCP enabled on the router , i have 3 machines
conected to the router .

first machine is a solaris box 192.168.254.127
second machine is windows XP pro 192.168.254.99
thrid machine is Widnows 2000 advanced 192.168.254.239

i have configured my Domain controller server with Active directory and DNS
on the third server , i have ran all tests i can think of
i've ran the 2 test that you can do from the DNS when you right click on the
server and go to monitoring tab and they both passed

i have alos ran nslookup on the server and got this back

C:\Documents and Settings\Administrator.CHEETAH.000>nslookup
Default Server: cheetah.mydomain.com
Address: 192.168.254.239
cheetah
Click to expand...
Server: cheetah.mydomain.com
Address: 192.168.254.239

Name: cheetah.mydomain.com
Address: 192.168.254.239

which indicates it working just fine
i have also configured my forward zone and reserve zone

what the problem is that when right click on my computer on the windows xp
machine / proprties / computer name tab / change
and i type the domain name in there . which is "mydomain" i get an error ,
here is the error "a domain controller for the domain mydomain.com could not
be contacted "

it doesn't seem to find the domain server , i can't add my client to the
domain what should i do , do i need to add the widnowsxp info somewhere on
the server , do i need to add any info about the server somewhere on my
windows xp machine , please any input is greatly appreicated , i think my
domain server is working fine but i just don't know and can't get the
clients to connect to it and find it


Thanks
 
In
XdriveX said:
guys , i need a little help over here

Here is the situation :

i have speedstream router , DHCP enabled on the router , i have 3
machines conected to the router .

first machine is a solaris box
192.168.254.127 second machine is windows XP pro
192.168.254.99
thrid machine is Widnows 2000 advanced 192.168.254.239

i have configured my Domain controller server with Active directory
and DNS on the third server , i have ran all tests i can think of
i've ran the 2 test that you can do from the DNS when you right click
on the server and go to monitoring tab and they both passed

i have alos ran nslookup on the server and got this back

C:\Documents and Settings\Administrator.CHEETAH.000>nslookup
Default Server: cheetah.mydomain.com
Address: 192.168.254.239

Server: cheetah.mydomain.com
Address: 192.168.254.239

Name: cheetah.mydomain.com
Address: 192.168.254.239

which indicates it working just fine
i have also configured my forward zone and reserve zone

what the problem is that when right click on my computer on the
windows xp machine / proprties / computer name tab / change
and i type the domain name in there . which is "mydomain" i get an
error , here is the error "a domain controller for the domain
mydomain.com could not be contacted "

it doesn't seem to find the domain server , i can't add my client to
the domain what should i do , do i need to add the widnowsxp info
somewhere on the server , do i need to add any info about the server
somewhere on my windows xp machine , please any input is greatly
appreicated , i think my domain server is working fine but i just
don't know and can't get the clients to connect to it and find it


Thanks
Click to expand...


Is the DNS name mydomain or mydomain.com?
Try using the FQDN to join to the domain.
If it is mydomain (single label domain name) XP will have a problem with it
and so will the Win2k machine with SP4 take a look at this and make the
registry entry that allows single label domain names on XP and Win2kSP4.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

Also and most important Win2k domains store the service and resource records
for the domain in DNS therefore, you must *only* use the AD DNS server in
TCP/IP properties for DNS in all machines that are a member of the domain.
You also need to set the FLZ properties to allow dynamic updates to the
zone.
 
kevin
Thanks for your reply really appreciated , here are some answers to your
questions , i'm glad that you asked me those question so it's clear to
everyone that reads it
:
the domain is "mydomain.com:
i just tried to use the the FQDN to join to the domain , still didn't work

sorry but can you explain this part a little more , i'm confused of what the
FLZ is
Also
for the domain in DNS therefore, you must *only* use the AD DNS server in
TCP/IP properties for DNS in all machines that are a member of the domain.
You also need to set the FLZ properties to allow dynamic updates to the
zone.
Click to expand...

let me know if you have more questions
Thanks again
 
In
XdriveX said:
kevin
Thanks for your reply really appreciated , here are some answers to
your questions , i'm glad that you asked me those question so it's
clear to everyone that reads it
the domain is "mydomain.com:
i just tried to use the the FQDN to join to the domain , still didn't
work

sorry but can you explain this part a little more , i'm confused of
what the FLZ is
Click to expand...

Forward Lookup zone
In your local DNS check the properties of the mydomain.com forward lookup
zone an the General page "Allow Dynamic updates" set to "Yes" not "Only
secure updates" as of yet.

You can also create a computer account for the machine name in ADUC

Can you post an ipconfig /all for the client and server?
 
oh i get it , nevermind , FLZ is forward lookup zones

FLZ properties is set to allow dynamic updates

what do you mean about

for the domain in DNS therefore, you must *only* use the AD DNS server indomain

Thanks
 
In
XdriveX said:
oh i get it , nevermind , FLZ is forward lookup zones

FLZ properties is set to allow dynamic updates

what do you mean about

for the domain in DNS therefore, you must *only* use the AD DNS
server in
Click to expand...

Active Directory stores its service and resource records in DNS, domain
members look to DNS to find the domain controller. If you have DNS on the
DC, which is the recommended way, you need to point all machines to the DC
for DNS *only*
 
this is from the server

C:\Documents and Settings\Administrator.CHEETAH.000>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : cheetah
Primary DNS Suffix . . . . . . . : mydomain.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mydomain.com
Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast
Ethernet
Controller (3C905B-TX Compatible)
Physical Address. . . . . . . . . : 00-C0-4F-61-18-63
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.254.239
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.254.254
DHCP Server . . . . . . . . . . . : 192.168.254.254
DNS Servers . . . . . . . . . . . : 192.168.254.239
Lease Obtained. . . . . . . . . . : Wednesday, October 15, 2003
8:10:55
PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038 9:14:07
PM

C:\Documents and Settings\Administrator.CHEETAH.000>
---


this is from the client :

C:\Documents and Settings\XdriveX>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : windowsxp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys NC100 Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-04-5A-4A-0C-AB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.254.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.254.254
DHCP Server . . . . . . . . . . . : 192.168.254.254
DNS Servers . . . . . . . . . . . : 192.168.254.254
Lease Obtained. . . . . . . . . . : Wednesday, October 15, 2003
10:39:44
AM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038
10:14:07 PM


C:\Documents and Settings\XdriveX>

---
is the three 0's normal in the forst line of the server's out put , this one
C:\Documents and Settings\Administrator.CHEETAH.000>ipconfig /all

what are the 000 for ??

i did create computer account for the machine name in ADUC
still no luck

Thanks for your help
 
In
XdriveX said:
this is from the server

C:\Documents and Settings\Administrator.CHEETAH.000>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : cheetah
Primary DNS Suffix . . . . . . . : mydomain.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mydomain.com
Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast
Ethernet
Controller (3C905B-TX Compatible)
Physical Address. . . . . . . . . : 00-C0-4F-61-18-63
DHCP Enabled. . . . . . . . . . . : Yes<!!!!!!this is a no no
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.254.239
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.254.254
DHCP Server . . . . . . . . . . . : 192.168.254.254<!!!!!!
DNS Servers . . . . . . . . . . . : 192.168.254.239
Click to expand...

You are using a dynamic address for this DC, especially with DNS installed
this is not good, assign this machine a static address and exclude it from
the DHCP scope
this is from the client :

C:\Documents and Settings\XdriveX>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : windowsxp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys NC100 Fast
Ethernet Adapter
Physical Address. . . . . . . . . : 00-04-5A-4A-0C-AB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.254.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.254.254
DHCP Server . . . . . . . . . . . : 192.168.254.254
DNS Servers . . . . . . . . . . . : 192.168.254.254
Click to expand...

Here is your problem, the DNS server should be the address of your DC
192.168.254.239 then configure DNS as per this KB: 300202 - HOW TO Configure
DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1

Also I see you are using your router for DHCP, you will be much better off
to use DHCP in Win2k, it is much better suited for AD configure it with
these Scope options and Authorize it in AD:
003 Your Routers address
006 DNS server use the IP of your DC for DNS
015 DNS Domain name (your AD DNS Domain name)
081 DDNS registration (this option is configured on the DNS tab of your
DHCP server properties in the DHCP console) Win2k DHCP supports registration
in DNS of clients that cannot
Lease Obtained. . . . . . . . . . : Wednesday, October 15,
2003 10:39:44
AM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038
10:14:07 PM


C:\Documents and Settings\XdriveX>

---
is the three 0's normal in the forst line of the server's out put ,
this one C:\Documents and Settings\Administrator.CHEETAH.000>ipconfig
/all

what are the 000 for ??
Click to expand...
That is the directory your user profile is in.
Windows adds the 000 when there are different users with the same logon
name, Because when you logon you actually logon with the ID that is
assigned by either Windows or the domain, when you DCPROMOed the machine it
created a domain Administrator account so it could not use the computer
administrator account to logon.

You did not post the domain name in ADUC does it match exactly the primary
DNS suffix of the DC?
 
The client is pointing to the wrong DNS server. It whould point at the DC for DNS only. On the DC, you will want to verfiy that in the DNS forward lookup zone
that the DC is registering it's SRV records. You will see 4 folders under you domain name called, _msdcs, _sites, _TCP, _UDP. If these are there, this is a
good indication that DNS and the DC are setup correctly. If they are not there, then make sure the zone is spelled correctly. Then make sure the zone allows
dynamic updates.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Kevin Thanks alot for your help , you are right , everything is working
perfect now , i really appreciate all your help .
Thank you very much

also wanted to thank michael for his input

Thanks guys , i'm happy now :)
 
Back
Top