• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2150
  • Last Modified:

Exchange 2010 - The attempt to connect to http://server/powershell using "Kerberos" autentication failed

We upgraded to SP1, rollups for SP1, and applied all windows updates about 10 days ago.  MAJOR mistake.  Everything is running even slower than it did before, but that's a story for another day.  Both my backups and attempts to connect to EMC fail.  Again, backups for another day.  I need to get EMC working ASAP.  I've tried the winrm quick config both on the CAS and Mailbox servers but it still doesn't work.  Here is the error I'm getting now.

The attempt to connect to server/powershell using "kerberos" authentication failed.  processing data from remote server failed with the following error message: the winrm client cannot complete the operation with the time specified.  check if the machine name is valid and is reachable over the network and firewall exception for winrm service is enabled..
0
BrianRB
Asked:
BrianRB
  • 5
  • 2
  • 2
1 Solution
 
BrianRBAuthor Commented:
oh, i cannot connect to it locally or remotely
0
 
5g6tdcv4Commented:
check to make sure time is within 5 minutes of AD server
0
 
BrianRBAuthor Commented:
the time is correct :(
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
5g6tdcv4Commented:
are there any clues in the the event log? Specifically the security log?
0
 
BrianRBAuthor Commented:
i checked and nothing really stood out.  there's too much in the security logs to find anything meaningful.  anything specific i should be looking for?
0
 
KaffiendCommented:
Did you check IIS?
0
 
BrianRBAuthor Commented:
check it for what?
0
 
KaffiendCommented:
Check maybe:

authentication settings on the "powershell" virtual directory

see if the MSExchangePowerShellAppPool exists (hopefully the update didn't hose this) and is selected for this virtual directory

check the "physical path" and make sure it is correct
0
 
BrianRBAuthor Commented:
yeah i did that before i ever put out the post :(
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 5
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now