Why doesn't DCDIAG work under telnet?

[JBruyet]

Hey all,

I setup a small web server with my HP web diagnostics on it, and while doing that I added a few MS items. One of the MS items I added was TELNET. I tried using TELNET to gain access to my domain controllers (2k3 SP2) so I could run DCDIAG but I get the following errors:

This is for DC2 --
Starting test: KnowsOfRoleHolders
Warning: SRV-DC3 is the Schema Owner, but is not responding to DS RPC Bind.
Warning: SRV-DC3 is the Domain Owner, but is not responding to DS RPC Bind.
Warning: SRV-DC3 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
......................... SRV-DC2 failed test KnowsOfRoleHolders

Doing primary tests
Testing server: Default-First-Site-Name\SRV-DC2
Starting test: Replications
[SRV-DC3] DsBindWithSpnEx() failed with error 5,
Access is denied..

This is for DC3 --
Starting test: KnowsOfRoleHolders
Warning: SRV-DC2 is the PDC Owner, but is not responding to DS RPC Bind.
Warning: SRV-DC2 is the Rid Owner, but is not responding to DS RPC Bind.
......................... SRV-DC3 failed test KnowsOfRoleHolders

After seeing these errors I had been trying to find out what was wrong and when I actually logged onto the domain controllers to run DCDIAG it ran clean. No errors. I only get the errors when I run DCDIAG out of a TELNET session. Are there any tweaks I can use for my TELNET sessions so I can run DCDIAG under them?

Thanks,

Joe B

 

[TechyMcSe2k]

You may need some parameters when connecting with Telnet to authenticate your session with AD to allow the RPC Bind.

possibly "set" for NTLM authentication...

Review here:

http://technet.microsoft.com/en-us/library/c.aspx

_______________________________________
Great knowledge can be obtained by mastering the Google algorithm.

 

[JBruyet]

Hi TechyMcSe2k,

I tried adding the "set ntlm" to the command line that opens my telnet window but I can't get that to work at all. I tried opening a telnet session from the command prompt on my workstation and I can do the "set ntlm" from there but I still get the errors. I think I'm just going to have to take the time to login to my domain controllers. I can live with that but doing it from a link on a web page would have been easier. And TECHier.

Thanks for the help,

Joe B