Re: Problem joining computer to domain
- From: Andy <ajj3085@xxxxxxxxxxxx>
- Date: 14 May 2007 05:35:11 -0700
On May 11, 5:08 am, v-ja...@xxxxxxxxxxxxxxxxxxxx ("Jacky Luo [MSFT]")
wrote:
From the description, I understand the issue is that you cannot join a
computer to domain.If I am off base, please don't hesitate to let me know.
Let us refer to the following steps to troubleshoot the issue:
Before we can go further,Please let me know how do you join the computer to
domain, manually join or via connectcomputer?
1.Please delete computer account from server management
2.Please create computer account from server management
3.Rejoin the computer to domain viahttp://SBSserver/connectcomputer
if not work,Please manually join to domain,what's the result?
If the issue persists, let us try to
1. Quit the client computer which is mentioned in the event from the
domain. Make sure its computer name is not duplicated with another computer.
2. Delete this computer account from AD Users and Computers (dsa.msc)
snap-in if it is still there.
3. Reset the TCP/IP stack using the method in the following article:
For Windows Server 2003:
317518 How to Reset "Internet Protocol (TCP/IP) " in Windows Server 2003http://support.microsoft.com/?id=317518
For Windows XP:
299357 How to Reset Internet Protocol (TCP/IP) in Windows XPhttp://support.microsoft.com/?id=299357
For Windows 2000:
285034 How to Remove and Reinstall TCP/IP for Windows 2000http://support.microsoft.com/?id=285034
4. Re-join the computer into the domain.
If issue still occur,Please refer to the following article for
troubleshooting.
http://www.eventid.net/display.asp?eventid=1053&eventno=1584&source=U...
phase=1
http://www.eventid.net/display.asp?eventid=1054&eventno=1393&source=U...
phase=1
Especially note if it is related to firewall block network traffic.
Hi,
The issue was not that i couldn't join the computer to the domain, the
issue was that after joining to the domain, I could not logon to the
domain.
At any rate, I think I found the problem. I have one WAP, lets call
it SecWap secured per Owen's wireless sbs security document (which can
be found in this group..). I had a second, unsecured WAP, lets call
it UnSec. I was trying the connect computer through the UnSec access
point. The join worked ok, but for some reason Cert enrollment
wouldn't happen over the UnSec AP. The SecWap network showed up, but
obviously I couldn't connect to that network without Certificate
Enrollment occuring.
I started over and did everything from a wired network, and the
computer joined the domain fine and was then able to access SecWap.
The error messages where misleading though, because I thought that
enrollment and other processing should have been able to work over the
UnSec AP; apparently this is not the case.
Andy
.
- Follow-Ups:
- Re: Problem joining computer to domain
- From: "Jacky Luo [MSFT]"
- Re: Problem joining computer to domain
- References:
- Problem joining computer to domain
- From: Andy
- Re: Problem joining computer to domain
- From: Andy
- Re: Problem joining computer to domain
- From: "Jacky Luo [MSFT]"
- Problem joining computer to domain
- Prev by Date: Re: Unable to stop/restart SMTP service
- Next by Date: Outlook 2003 not working
- Previous by thread: Re: Problem joining computer to domain
- Next by thread: Re: Problem joining computer to domain
- Index(es):
Relevant Pages
|
