xp pro can't join 2k domain

[confuse]

Hi,

I am trying to set up a practice environment. I have a 2k
server with active directory installed. The domain is
home.org. Also, I have a laptop with winxp pro trying to
join the domain. The server and the laptop are connected
to the internet through the linksys router. The ip for
the server is 192.168.1.x and the laptop is 192.168.1.x.

Here's my problem. When I tried to join the domain, I get
an error message saying the domain cannot be contact and
is a dns issue. I am able to ping the server's ip and
server name. However, I am not able to ping the domain
home.org. In the AD dns, I put the linksys ip in the
server's forwarder. And in the laptop, the ip of the
server. Doing this would allow me to ping the server's
name because I'm using the internal dns from the server.
I thought that by doing it would resolve my issue in
joining the domain with the laptop, but that didn't work.

I check the tcp/ip settings in the laptop and it seems to
be correct. I followed the post that was posted earlier
with the dns issue and it still hasn't resolved my
problem. I even tried reinstalling the laptop and active
directory. So any help with this issue is greatly
appreciated. Thanks.

 

[Graham]

I had an issue with logging onto a AD domain over a VPN, not sure if this is
related but fixed by article number MS KB 244474 or link
http://support.microsoft.com/?kbid=244474 may help!
Regards,
Graham.

 

[Paul]

I had a similar isue a couple of months ago and that is because the dns
service on the domain controller had set itself up as a root server. It may
be worth checking if this is the same case. If it is then delete the zone
*.* under Forward Lookup Zones within the DNS configuration.

Paul

 

[confuse]

Paul,

Under forward lookup zone is my domain. I'm assuming
thats the default. I tried deleting it and still it
didn't work. If it is of any help the error I got when
trying to connect to the domain is "DNS name does not
exist". When I do an nslookup on the laptop, it says that
it can not find server name for address 192.168.1.X
(server). Like I said before, I am able to ping the
server's ip and server name, but not the domain. I will
try to play around with this some more, but I might have
to reinstall the server again and work with it from there.
Thanks.

confuse

 

[Kevin D. Goodknecht Sr. [MVP]]

In confuse <[email protected]>
posted their concerrns,
Then Kevin D4Dad added his reply at the bottom.

Paul,

Under forward lookup zone is my domain. I'm assuming
thats the default. I tried deleting it and still it
didn't work. If it is of any help the error I got when
trying to connect to the domain is "DNS name does not
exist". When I do an nslookup on the laptop, it says that
it can not find server name for address 192.168.1.X
(server). Like I said before, I am able to ping the
server's ip and server name, but not the domain. I will
try to play around with this some more, but I might have
to reinstall the server again and work with it from there.
Thanks.

confuse

Confuse,
The nslookup error is not relivant, nslookup attempts a reverse lookup on
the IP addresses of DNS servers it uses. All it means is that there is no
reverse lookup on the DNS server it is using. Ignore the error or create a
reverse lookup for the DNS server.
That being said after nslookup starts is it able to resolve DNS addresses?

I can help you with this problem but I need a couple of things, I need to
see an unedited ipconfig /all from both the DC and from the XP machines.

In your AD DNS forward lookup zone do these folders exist?
_msdcs
_sites
_tcp
_udp

Do you have "Allow dynamic updates" set to "Yes"

Is the DC pointing only to its own private IP for DNS only? not 127.0.0.1

Is the XP Pro machine pointing only to the DC for DNS?

Do you have the DNS suffix for the AD domain in the DNS suffix for this
connection field on the DNS tab on the XP Pro machine?
This is important because XP Pro must be able to register its addresses in
DNS, Another problem with XP is that it cannot register its addresses in
domains that have a single label domain (domain vs. domain.com)

But to start diagnosing the problem I need to see the ipconfig /all
unedited.

I would be glad to help you but you need to stop beating around the bush.

 

[confuse]

Kevin,

Here's the ipconfig /all from the server and xp pro.
BTW, I reinstalled the server and still it didn't work.
The new domain is "home.com". And no I did not see any of
those folders listed. Hope this help. Thanks.

server:
Host Name . . . . . . . . . . . . : win2k
Primary DNS Suffix . . . . . . . : home.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home.com

t adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100

Physical Address. . . . . . . . . : 00-07-E9-79-E8-6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.205.x.x
24.205.x.x
24.205.x.x
xp pro:
Host Name . . . . . . . . . . . . : xplaptop
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

t adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100

Physical Address. . . . . . . . . : 00-08-79-B2-
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.101