Domain Problems

[Guest]

Hey;

I am about to either pull my hair out or throw out this pc... Our company is
allowing the presidents friend to use some extra office space for the time
being.... He wishes to use his own personal computer as he has TONNES of
programs and migrating would be a nightmare.... It was originally running
Windows XP Home Edition, but he did a step up upgrade to windows XP Pro
[didnt know that was possible?].

My problem is with joining his computer to the domain. When I try to join
the domain the system cannot resolve the domain name (unless i append the
..local). The computer then "joins" the domain succesfully. After the restart
the domain cannot be contacted when you attempt to log on as a member of the
domain.

When I log on as a local machine admin, I cannot browse to the
\\server_path\. but I can browse to the servers ip \\192.168.x.x\. When i
play around with the TCP/IP settings I can get the domain name path to
resolve randomly.....

I can ping the domain name and the domain IP....

I have tried the "netsh int ip reset C:\TCPResetLog.txt" to no avail.

The internet works through our proxy properly

I've spent about 12 hours on this machine allready... anybody have any
pointers?

Thanks for your time,
Kris

 

[Guest]

Also forgot to mention that I have ran System File Checker to no avail....

 

[Chuck]

Hey;

I am about to either pull my hair out or throw out this pc... Our company is
allowing the presidents friend to use some extra office space for the time
being.... He wishes to use his own personal computer as he has TONNES of
programs and migrating would be a nightmare.... It was originally running
Windows XP Home Edition, but he did a step up upgrade to windows XP Pro
[didnt know that was possible?].

My problem is with joining his computer to the domain. When I try to join
the domain the system cannot resolve the domain name (unless i append the
.local). The computer then "joins" the domain succesfully. After the restart
the domain cannot be contacted when you attempt to log on as a member of the
domain.

When I log on as a local machine admin, I cannot browse to the
\\server_path\. but I can browse to the servers ip \\192.168.x.x\. When i
play around with the TCP/IP settings I can get the domain name path to
resolve randomly.....

I can ping the domain name and the domain IP....

I have tried the "netsh int ip reset C:\TCPResetLog.txt" to no avail.

The internet works through our proxy properly

I've spent about 12 hours on this machine allready... anybody have any
pointers?

Thanks for your time,
Kris

Kris,

There are specific settings that you need to make on individual computers, and
other setting that you need to make on the domain controller, to enable Windows
XP computers on a domain. Name resolution issues, which appear to be a good
part of your problems, are discussed here.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>

 

[Guest]

Thanks for the help....

We are using SBS2003... the domain control has that computer enabled on the
domain and the dns server is configured properly....

I do get the error that the domain control could not be connected properly.

Hey;

I am about to either pull my hair out or throw out this pc... Our company is
allowing the presidents friend to use some extra office space for the time
being.... He wishes to use his own personal computer as he has TONNES of
programs and migrating would be a nightmare.... It was originally running
Windows XP Home Edition, but he did a step up upgrade to windows XP Pro
[didnt know that was possible?].

My problem is with joining his computer to the domain. When I try to join
the domain the system cannot resolve the domain name (unless i append the
.local). The computer then "joins" the domain succesfully. After the restart
the domain cannot be contacted when you attempt to log on as a member of the
domain.

When I log on as a local machine admin, I cannot browse to the
\\server_path\. but I can browse to the servers ip \\192.168.x.x\. When i
play around with the TCP/IP settings I can get the domain name path to
resolve randomly.....

I can ping the domain name and the domain IP....

I have tried the "netsh int ip reset C:\TCPResetLog.txt" to no avail.

The internet works through our proxy properly

I've spent about 12 hours on this machine allready... anybody have any
pointers?

Thanks for your time,
Kris

Kris,

There are specific settings that you need to make on individual computers, and
other setting that you need to make on the domain controller, to enable Windows
XP computers on a domain. Name resolution issues, which appear to be a good
part of your problems, are discussed here.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>

 

[Chuck]

Hey;

I am about to either pull my hair out or throw out this pc... Our company is
allowing the presidents friend to use some extra office space for the time
being.... He wishes to use his own personal computer as he has TONNES of
programs and migrating would be a nightmare.... It was originally running
Windows XP Home Edition, but he did a step up upgrade to windows XP Pro
[didnt know that was possible?].

My problem is with joining his computer to the domain. When I try to join
the domain the system cannot resolve the domain name (unless i append the
.local). The computer then "joins" the domain succesfully. After the restart
the domain cannot be contacted when you attempt to log on as a member of the
domain.

When I log on as a local machine admin, I cannot browse to the
\\server_path\. but I can browse to the servers ip \\192.168.x.x\. When i
play around with the TCP/IP settings I can get the domain name path to
resolve randomly.....

I can ping the domain name and the domain IP....

I have tried the "netsh int ip reset C:\TCPResetLog.txt" to no avail.

The internet works through our proxy properly

I've spent about 12 hours on this machine allready... anybody have any
pointers?

Thanks for your time,
Kris

Kris,

There are specific settings that you need to make on individual computers, and
other setting that you need to make on the domain controller, to enable Windows
XP computers on a domain. Name resolution issues, which appear to be a good
part of your problems, are discussed here.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
<http://nitecruzr.blogspot.com/2005/07/windows-networking.html>

Thanks for the help....

We are using SBS2003... the domain control has that computer enabled on the
domain and the dns server is configured properly....

I do get the error that the domain control could not be connected properly.

How about DHCP? Take a look at "ipconfig /all" from the problem computer, and
from a couple non problem computers.
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>

 

[Ron Lowe]

My problem is with joining his computer to the domain. When I try to join

the domain the system cannot resolve the domain name (unless i append the
.local). The computer then "joins" the domain succesfully. After the
restart
the domain cannot be contacted when you attempt to log on as a member of
the
domain.

When I log on as a local machine admin, I cannot browse to the
\\server_path\. but I can browse to the servers ip \\192.168.x.x\. When i
play around with the TCP/IP settings I can get the domain name path to
resolve randomly.....

You have a DNS problem.

Ensure the client PC is pointing to ONLY the internal DNS server.
( The server machine itself, probably. )
( Your DHCP server should push this out for you. )

Here's my usual lecture on the topic:

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:


How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861


If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )


1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.


( you should use the DHCP server to push out the local DNS server
address. )


2) Ensure DNS server on win2k is configured to permit dynamic updates.


3) Ensure the win2k server points to itself as a DNS server.


4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.


On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:


Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
DNS and AD FAQs:
http://support.microsoft.com/?id=291382