Exchange 2010 EMC error: The attempt to connect to http /powershell using 'Kerberos' auth failed

Ok so getting the error:

The attempt to connect to http server/powershell using 'Kerberos' authentication failed: Connecting to the remote server failed with the following error message: access is denied.

Rebuilt the virtualdirectory, verified the applicationhost.config file contained the correct path to kerbauth.dll and wsman.dll

Also the two user accounts Ive tried do have remote powershell enabled.

the kerbauth module in the powershell virtualdirectory does not have a path value, and it is listed as managed.  I know that usually means that the applicationhost.config file has an incorrect path.. but i can assure you the path is correct.  I even copied the kerbauth.dll file into c:\program files\microsoft\exchange\v14\bin (when my exchange install path is c:\exchange\v14
I also verified my ExchangeInstallPath env variable does say c:\exchange\v14 which is where my exchange is installed to.

I've ran iisreset /noforce multiple times before, during and after.
LVL 14
Ben HartAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zaheer IqbalTechnical Assurance & ImplementationCommented:
0
Zaheer IqbalTechnical Assurance & ImplementationCommented:
esolutions:

Method 1:

Close all MMC/EMC instances before proceeding.
Open Registry Editor (regedit) as the user you run the EMC under.
Go to
HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools
Look for value NodeStructureSetting.
If it is there, back it up and then remove it.
Method 2:

Close all MMC/EMC Instances before proceeding.
Open Powershell or Powershell IDE as the user you run the EMC under and execute the following command:.
Remove-ItemProperty -Path HKCU:\Software\Microsoft\ExchangeServer\v14\AdminTools\ -Name NodeStructureSettings
Close Powershell
After performing either of the methods above to remove the registry entry you should be able to open the Exchange Management Console and it will discover another Exchange server and connect.
1
Zaheer IqbalTechnical Assurance & ImplementationCommented:
Also check your time is in sync with the DC
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Zaheer IqbalTechnical Assurance & ImplementationCommented:
0
Ben HartAuthor Commented:
time is syncing correctly.. also I can't believe I forgot this part but this error is happening on a Win7 vm.  So it's the exchange management tools on a remote machine.  EMC/EMS on local server work perfectly.
0
Zaheer IqbalTechnical Assurance & ImplementationCommented:
try logging in as another user that has access to exchange on that VM does it work ?
0
Ben HartAuthor Commented:
The second link you posted is not a matching error.  I read through it but Im not getting any errors under the Windows Remote Management logs.
0
Ben HartAuthor Commented:
logging in with a different domain account (that is also an Org Admin) I get 'Access is denied.  It was running the command discover-exchangeserver -usewia $true -suppresserror $true -currentversion version 14.2 (build 247.5)


I also tried adding another forest and specifying the server at the main site.  But I gives me the original error complaining about powershell and kerberos..
0
Ben HartAuthor Commented:
new development.. now on the local server here at my site I am getting the same original error now.  Kerberos authentication failed while connecting to the remote server.  So it's happening on both a Win7 vm and our second exchange server.
0
Zaheer IqbalTechnical Assurance & ImplementationCommented:
Ok quite possible if you can restart your DC(s)?
0
Ben HartAuthor Commented:
two different ad accounts that are organization admins.. wouldn't think there's be some DC disconnect.
0
Ben HartAuthor Commented:
Anyone else?
Short of a reinstall how can I get kerbauth.dll recognized and loaded as native versus managed?
0
Ben HartAuthor Commented:
I ended up re-creating the virtual directories after a management tool reinstall.  I do not know what actually resolved my issue but after those two were done I found kerbauth as native.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ben HartAuthor Commented:
My issue was resolved by reinstallation of the mnmgt tools.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.