N
Nigel Smith
Some one emailed me recently to ask if I had resolved this problem.
The short answer in no, I have not resolved this.
I have access to two seperate production forests - both show this
error.
I have also tried in our isolated test environment - same error.
I have tried in a virtual environment using VmWare, with clean
installs of Windows - same error.
When I originally posted the message to the news group, we were still
using 'mixed-mode'.
We have now switched to 'native' mode - but still the same error.
Also we have introduced some 2003 servers as Domain Controllers.
Using the latest versions of NETDOM.EXE & NLTEST.EXE, version
5.2.3790.0
We still get this error!
My conclusion is that this is some sort of bug in NETDOM & NLTEST, and
that every forest shows this error!
We are seeing no other behaviour that indicates a problem.
So I have stopped worrying and just accepted that NETDOM & NLTEST show
this error.
Maybe one day Microsoft will acknowledge this error. Maybe then they
will fix it.
It's definitely not a DNS issue, as far as I can see.
I used 'Ethereal' to trace the ethernet packets to the PDC.
(http://www.ethereal.com/distribution/win32/)
You can see the PC making a 'Remote Procedure Call' (RPC) to the PDC
on TCP port 445.
The RPC's UUID indicates the request it's calling the
'NetrLogonControl2' operation.
It immediately replies with error code '0x0000054b'.
This basically confirms what the NLTEST.EXE is showing.
So I think the problem is in a API call of some sort that both NETDOM
& NLTEST use to get information from Active Directory.
Thanks
Nigel
The short answer in no, I have not resolved this.
I have access to two seperate production forests - both show this
error.
I have also tried in our isolated test environment - same error.
I have tried in a virtual environment using VmWare, with clean
installs of Windows - same error.
When I originally posted the message to the news group, we were still
using 'mixed-mode'.
We have now switched to 'native' mode - but still the same error.
Also we have introduced some 2003 servers as Domain Controllers.
Using the latest versions of NETDOM.EXE & NLTEST.EXE, version
5.2.3790.0
We still get this error!
My conclusion is that this is some sort of bug in NETDOM & NLTEST, and
that every forest shows this error!
We are seeing no other behaviour that indicates a problem.
So I have stopped worrying and just accepted that NETDOM & NLTEST show
this error.
Maybe one day Microsoft will acknowledge this error. Maybe then they
will fix it.
It's definitely not a DNS issue, as far as I can see.
I used 'Ethereal' to trace the ethernet packets to the PDC.
(http://www.ethereal.com/distribution/win32/)
You can see the PC making a 'Remote Procedure Call' (RPC) to the PDC
on TCP port 445.
The RPC's UUID indicates the request it's calling the
'NetrLogonControl2' operation.
It immediately replies with error code '0x0000054b'.
This basically confirms what the NLTEST.EXE is showing.
So I think the problem is in a API call of some sort that both NETDOM
& NLTEST use to get information from Active Directory.
Thanks
Nigel