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