Win2k3 & XP Pro Machines Cannot Join 2000 Domain

I have a 2000 Domain which seems to be running just fine. Dcdiag and Netdiag
run without any errors and there are no event viewer events. Clients can
login without trouble.

Here's the problem:
Whenever I try to join a new machine to the domain, I receive this message,
"The following error occurred attempting to join the domain "mydomain.com":
"Not enough storage is available to complete this operation."

This message pops up after I've authenticated with Admin credentials. The
weird thing is that a computer account is created on the DC, but it is added
as disabled.

The Netsetup.LOG on the client machine spits out this error,
" 03/23 15:38:44 NetpGetComputerObjectDn: Unable to bind to DS on
'\\mydomain.COM': 0xe "

This only happens with 2003 and XP machines. I can add 2kPro and 2kServer
with no problem.

I've been running around in circles. Any help is
greatly appreciated.

Oh, one more thing. This is a child domain in a forest. Dcdiag and netdiag
all say error free on the Parent domain DC as well. I have no problems with
the parent domain.

"moodcrush" <moodcrush@discussions.microsoft.com> wrote in message
news:F919A219-7B39-4460-8A26-AC6CAEEF0D17@microsoft.com...
> I have a 2000 Domain which seems to be running just fine. Dcdiag and
Netdiag
> run without any errors and there are no event viewer events. Clients can
> login without trouble.
>
> Here's the problem:
> Whenever I try to join a new machine to the domain, I receive this
message,
> "The following error occurred attempting to join the domain
"mydomain.com":
> "Not enough storage is available to complete this operation."

An odd message -- perhaps spurious or perhaps
related to the storage of Profiles?

> This message pops up after I've authenticated with Admin credentials. The
> weird thing is that a computer account is created on the DC, but it is
added
> as disabled.
>
> The Netsetup.LOG on the client machine spits out this error,
> " 03/23 15:38:44 NetpGetComputerObjectDn: Unable to bind to DS on
> '\\mydomain.COM': 0xe "
>

The EventID and Source (from either/both the client and server) would be
useful.

Searching Microsoft from Google with (similar) searches:

[ join domain "storage * available" "complete * operation"
site:microsoft.com ]

Or checking http://www.eventid.net/ might help....


> This only happens with 2003 and XP machines. I can add 2kPro and 2kServer
> with no problem.

I am having trouble understanding what would be specific
to NON-Windows 2000 machines, other than different
configuration.

Normally, I would suggest that most such problems are DNS
related -- but your error messages are odd enough that perhaps
something else is happening.


> I've been running around in circles. Any help is
> greatly appreciated.
>
> Oh, one more thing. This is a child domain in a forest. Dcdiag and netdiag
> all say error free on the Parent domain DC as well. I have no problems
with
> the parent domain.

So DCDiag passes on EACH and EVERY DCs?

Clients DNS is set to use ONLY the internal DNS server
set (that can find the client domain)?

Thanks for your reply. I figured out the problem. It was caused by the Admin
account being in too many groups. This pretty much explains it
http://support.microsoft.com/default...b;en-us;280830.

Now to try to get the Hotfix.

"Herb Martin" wrote:

> "moodcrush" <moodcrush@discussions.microsoft.com> wrote in message
> news:F919A219-7B39-4460-8A26-AC6CAEEF0D17@microsoft.com...
> > I have a 2000 Domain which seems to be running just fine. Dcdiag and
> Netdiag
> > run without any errors and there are no event viewer events. Clients can
> > login without trouble.
> >
> > Here's the problem:
> > Whenever I try to join a new machine to the domain, I receive this
> message,
> > "The following error occurred attempting to join the domain
> "mydomain.com":
> > "Not enough storage is available to complete this operation."
>
> An odd message -- perhaps spurious or perhaps
> related to the storage of Profiles?
>
> > This message pops up after I've authenticated with Admin credentials. The
> > weird thing is that a computer account is created on the DC, but it is
> added
> > as disabled.
> >
> > The Netsetup.LOG on the client machine spits out this error,
> > " 03/23 15:38:44 NetpGetComputerObjectDn: Unable to bind to DS on
> > '\\mydomain.COM': 0xe "
> >
>
> The EventID and Source (from either/both the client and server) would be
> useful.
>
> Searching Microsoft from Google with (similar) searches:
>
> [ join domain "storage * available" "complete * operation"
> site:microsoft.com ]
>
> Or checking http://www.eventid.net/ might help....
>
>
> > This only happens with 2003 and XP machines. I can add 2kPro and 2kServer
> > with no problem.
>
> I am having trouble understanding what would be specific
> to NON-Windows 2000 machines, other than different
> configuration.
>
> Normally, I would suggest that most such problems are DNS
> related -- but your error messages are odd enough that perhaps
> something else is happening.
>
>
> > I've been running around in circles. Any help is
> > greatly appreciated.
> >
> > Oh, one more thing. This is a child domain in a forest. Dcdiag and netdiag
> > all say error free on the Parent domain DC as well. I have no problems
> with
> > the parent domain.
>
> So DCDiag passes on EACH and EVERY DCs?
>
> Clients DNS is set to use ONLY the internal DNS server
> set (that can find the client domain)?
>
>
>
>