?
Solved

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

Posted on 2011-09-26
9
Medium Priority
?
2,122 Views
Last Modified: 2012-05-12
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
Comment
Question by:BrianRB
  • 5
  • 2
  • 2
9 Comments
 
LVL 2

Author Comment

by:BrianRB
ID: 36600946
oh, i cannot connect to it locally or remotely
0
 
LVL 13

Expert Comment

by:5g6tdcv4
ID: 36601248
check to make sure time is within 5 minutes of AD server
0
 
LVL 2

Author Comment

by:BrianRB
ID: 36601307
the time is correct :(
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 13

Expert Comment

by:5g6tdcv4
ID: 36601650
are there any clues in the the event log? Specifically the security log?
0
 
LVL 2

Author Comment

by:BrianRB
ID: 36601673
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
 
LVL 14

Expert Comment

by:Kaffiend
ID: 36659553
Did you check IIS?
0
 
LVL 2

Author Comment

by:BrianRB
ID: 36709609
check it for what?
0
 
LVL 14

Accepted Solution

by:
Kaffiend earned 2000 total points
ID: 36711294
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
 
LVL 2

Author Comment

by:BrianRB
ID: 36711617
yeah i did that before i ever put out the post :(
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month8 days, 14 hours left to enroll

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question