Desmond [mailto:br...@briandesmond.com]
Sent: Friday, April 09, 2010 12:06 AM
To: NT System Admin Issues
Subject: RE: Unable to join computer to Domain
What’s the actual (complete) error message?
Thanks,
Brian Desmond
br...@briandesmond.com
c - 312.731.3132
-Original Message-
From: Bob
.
>>> "Ray" 4/9/2010 1:02 AM >>>
New machine or one that's already got an account in ADUC?
-Original Message-
From: Brian Desmond [mailto:br...@briandesmond.com]
Sent: Thursday, April 08, 2010 9:06 PM
To: NT System Admin Issues
Subject: RE: Unable to jo
New machine or one that's already got an account in ADUC?
-Original Message-
From: Brian Desmond [mailto:br...@briandesmond.com]
Sent: Thursday, April 08, 2010 9:06 PM
To: NT System Admin Issues
Subject: RE: Unable to join computer to Domain
What’s the actual (complete) error me
What’s the actual (complete) error message?
Thanks,
Brian Desmond
br...@briandesmond.com
c - 312.731.3132
-Original Message-
From: Bob Anderson [mailto:bander...@kentwatersports.com]
Sent: Tuesday, April 06, 2010 6:31 AM
To: NT System Admin Issues
Subject: Unable to join computer to D
esday, April 06, 2010 9:49 AM
> To: NT System Admin Issues
> Subject: RE: Unable to join computer to Domain
>
>
>
> Sorry for that.
>
> This is a XP sp3 box with hard wired IP addresses for machine and DNS
> servers The machine was renamed while not on the domain. I
rebooting, change the domain back to your domain.
Bill Mayo
From: Bob Anderson [mailto:bander...@kentwatersports.com]
Sent: Tuesday, April 06, 2010 9:49 AM
To: NT System Admin Issues
Subject: RE: Unable to join computer to Domain
Sorry for that.
This is a XP
when you specify the domain to join, have you tried both NetBIOS name and
FQDN? For example ACME vs. ACME.COM ? Also how are you specifying the
admin credentials? acme\jdoe ? Have you tried using a UPN
(j...@acme.com)?
Chris Bodnar, MCSE
Systems Engineer
Distributed Systems Service Delivery
: RE: Unable to join computer to Domain
Sorry for that.
This is a XP sp3 box with hard wired IP addresses for machine and DNS servers
The machine was renamed while not on the domain. I have added the machine name
in AD and done both direct add and network discovery.
Bob
IT Manager
From: Erik
[mailto:egold...@gmail.com]
Sent: Tuesday, April 06, 2010 9:40 AM
To: NT System Admin Issues
Subject: Re: Unable to join computer to Domain
you don't give much to go on, like the OS of the workstation, what version of
domain ( 2003 AD, 2008 AD, etc )
Have you checked for duplicate machine name,
: Tuesday, April 06, 2010 9:40 AM
To: NT System Admin Issues
Subject: Re: Unable to join computer to Domain
you don't give much to go on, like the OS of the workstation, what version of
domain ( 2003 AD, 2008 AD, etc )
Have you checked for duplicate machine name, tried NewSid, verified your D
WELL... back in the Win95 days (and perhaps on a Windows 2000 machine), I
had this happen perhaps 3 times.
There are some MS domain controller testers which may tell you if any of
your DCs have DNS issues.
Meanwhile, on those three problem machines, I actually needed to pull the
NIC and remov
You need to be able to at minimum FQDN one of the DC's \\server.domain.local. I
usually see the error message you mention when the wrong DNS servers are
specified.
David Lum // SYSTEMS ENGINEER
NORTHWEST EVALUATION ASSOCIATION
(Desk) 971.222.1025 // (Cell) 503.267.9764
-Original Message-
you don't give much to go on, like the OS of the workstation, what version
of domain ( 2003 AD, 2008 AD, etc )
Have you checked for duplicate machine name, tried NewSid, verified your DNS
is pointing to a DC, check DNS for your workstation record, etc ...
On Tue, Apr 6, 2010 at 9:30 AM, Bob Anderso
Silly question, but you *have* verified that the DNS servers are correct for
the domain controllers? What about using the LMHOSTS file and hard-coding the
DC IP addresses as well? That might help. Failing that, I'd say it's about time
to nuke it and rebuild it.
-Original Message-
From:
14 matches
Mail list logo
