Re: Cannot join domain by Windows XP Tablet Edition

On Sun, 4 Mar 2007 23:09:46 -0800, Hung Chan (EDIasia)
<HungChanEDIasia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Thu, 1 Mar 2007 01:50:08 -0800, Hung Chan (EDIasia)
<HungChanEDIasia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Wed, 28 Feb 2007 17:33:33 -0800, Hung Chan (EDIasia)
<HungChanEDIasia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Tue, 27 Feb 2007 22:25:05 -0800, Hung Chan (EDIasia)
<HungChanEDIasia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

"Chuck" wrote:

On Tue, 27 Feb 2007 20:07:03 -0800, Hung Chan (EDIasia)
<HungChanEDIasia@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi,

When I try to join the Windows 2003 Active Directory Domain, it said "A
domain controller for the domain could not be contacted". I have tried on
other Windows XP Professional, it is work.

When I checked on the Active Directory Users and Computers, I can find that
computer, but it have a "X" on the computer name.

Is anyone faced this problem before? Any suggestion on this issue? Thanks a
lot!!

How is name resolution setup on this computer? Identifying the domain
controller is not a magic setting.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

Hi,

Thanks for your reply. But I don't know how to check the "name resolution
setup" in my computer, can you please give me more information about this?

Thanks a lot.

Look at "Node Type" from "ipconfig /all", and read my articles.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html

Hi,

The node type is "Unknonw". By the way, I can't connect to the below link,
please let me have more information when you are free.

Thanks a lot!!!

Try the links again. The Blogger problem should be fixed now.
<http://bloggerstatusforreal.blogspot.com/2007/02/bx-sp4hmm.html>
http://bloggerstatusforreal.blogspot.com/2007/02/bx-sp4hmm.html

Do you have a WINS server? If not, "Unknown" will be treated as "Broadcast".
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

Check your DNS server setup (you do use DNS for local name resolution, I hope?)
- it is critical on a domain. Check the NetBT setup, and the firewall setup
too.
<http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html>
http://nitecruzr.blogspot.com/2005/05/windows-xp-on-nt-domain.html
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html

Hi,

I guess my DNS server is fine. It is because all the other WinXP Pro can
connect to this domain. Just one WinXP Tablet Edition cannot be work.

By the way, I have got one router in my network which running DHCP, so the
DNS should be point to my ISP's DNS server on all computer, include WinXP
Tablet.

Why the other WinXP Pro can join the domain but WinXP Tablet cannot?

Thanks a lot!!!

I think this is where we have to ask for more details about your network. You
said you have an AD Server 2003 domain, but you have also a router (a NAT
router?) issuing DHCP? And you're using the ISPs DNS?

I've written about these issues, and they are pretty intricate. If you can read
my cited articles, you'll be helping both of us.

The ISP can provide you Internet DNS service. Local name resolution, which your
ISP WON'T provide, is your problem.

The key here is Server Message Blocks. SMBs are key elements in file sharing,
Windows networking, and name resolution.
<http://nitecruzr.blogspot.com/search?q=server+message+blocks>
http://nitecruzr.blogspot.com/search?q=server+message+blocks

Do you have a local DNS server? With an AD domain, once folks spend the money
for Server 2003, they usually run DHCP and DNS off the server. That's if you
ONLY have Windows 2000, XP, or Vista clients.

Do you have a WINS server? WINS is an ancient name resolution technique, that
Microsoft used, before they fell into step with the computing world in general.

However you do your name resolution, the NetBT settings, and personal firewalls,
must be properly set on all clients AND the server.
# If you run DNS based name resolution, then you DISABLE NetBT on all computers,
and use SMBs directly hosted on IP. And you configure all personal firewalls to
permit port 445.
<http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html>
http://nitecruzr.blogspot.com/2006/07/advanced-windows-networking-using.html
# If you don't run DNS based name resolution, then you ENABLE NetBT on all
computers, and use SMBs hosted on NetBT. And you configure all personal
firewalls to permit ports 137 - 139.
<http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html>
http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html

Now, if none of this helps, we could look at "browstat status", "ipconfig /all",
"net config server", and "net config workstation", from the problem computer,
and from 2 computers that are NOT a problem, AND from the server, and diagnose
the problem. Read this article, and linked articles, and follow instructions
precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Hi,

The problem has solved. It is because the personal firewall has blocked the
connection. I have tried to disable the personal firewall, then I can join
the domain. Anyway, Thanks a lot for your great help!!!

And another PFW issue. Thanks for the update.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Relevant Pages

  • Re: NT Domain to AD migration
    ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Secondary DNS and PIX
    ... Of course I updated them with the DNS ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ... Windows SBS 2003 SP1 is available. ...
    (microsoft.public.windows.server.sbs)
  • Re: Find AD hostname from Linux command line
    ... The Windows XP workstation gets an IP ... "Register this connection's addresses in DNS" turned ON. ... If I am on a Linux server and do "ping lancelot.ad.mydomain.com", ...
    (microsoft.public.win2000.dns)
  • Re: Secondary DNS and PIX
    ... SBS SP1 was a very specific service pack comprising several ... Root hints for DNS means you leave the forwarders ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ...
    (microsoft.public.windows.server.sbs)
  • Re: Two Win2k3 questions ... Roaming Profiles & Access Privileges ...
    ... >DHCP, DNS, Print Server, and File Server responsibilities. ... lookup zone on Windows NT" ... http://support.microsoft.com?kbid=229873 "Delegate Control Wizard Cannot Be Used ...
    (microsoft.public.win2000.advanced_server)
Loading