Error when open management console
Hi When I try to open the Exchnage 2010 Management console, takes the following error: The attemp to connect to http://servername/Power shell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. The WinRM service is running but the console doesnt work and the powershell console dooesnt connect to server Exchnage.
November 11th, 2010 7:55pm

Hi, Did you try to run the following command: winrm quickconfig and winrm get winrm/config/winrs Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, URL: http://blog.WhatDoUC.net Phone: +923008210320
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 10:29pm

Hi when run winrm get winrm/config, i see diferent values, i need to check some value?? Thanks
November 12th, 2010 11:37pm

Try these steps: Step 1: Run WinRM quick config WinRM already is set up to receive requests on this machine. WinRM already is set up for remote management on this machine. Step 2: IIS manager à Default website à Edit bindings à Confirm HTTP is configured to work on port 80 (If customer is running more than 1 website make sure default website is working on port 80 ) WinRM 2.0 no longer uses Port 80. Since Power shell virtual directory is placed under default website if the default website is not configured to work on port 80. We will not be able to browse any virtual directories under default website. Step 3: IIS manager à Default website à Edit bindings à HTTP à hostname value should be blank (Some time you will see hostname as local host) Step 4: Try accessing OWA and the default website from the IIS and make sure we are able to access the websites. (Some time we may get HTTP error 500) SSL is not required on the Powershell virtual directory. Step 5: IIS Manager à Default website à Module à Make sure we don’t have kerbauth module loaded. If you see Kerbauth in the Default website module remove it. (By default kerbauth authentication is give to power shell and not for the default website) Step 6: IIS Manager à Default website à Power shell virtual directory à Module à check do we have kerbauth module loaded and it should be in Native mode not as a managed mode If you see in managed mode à remove the kerbauth à add it again and choose native mode Kerbauth authentication method should be in local and not inherited Step 7: Check Exchange is communicating with the domain controller (Nic settings on the Exchange server) Check for the application logs ----------------- - Vinit Nair
Free Windows Admin Tool Kit Click here and download it now
November 13th, 2010 2:21am

The resolution is reinstall the Exchange, Disaster Recovery, for this server
December 7th, 2010 6:51pm

i facing the same problem i check all steps it's okey but problem is stillMohamed Abd Elhamid Abd Elaziz Microsoft System Administrator Abdul Samad Al Qurashi Co.
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2011 9:07am

i'm facing this error and solving it by this link: http://www.ldap389.info/en/2011/04/14/the-winrm-client-cannot-complete-the-operation-within-the-time-specified/Mohamed Abd Elhamid Abd Elaziz Microsoft System Administrator Abdul Samad Al Qurashi Co.
July 25th, 2011 5:12pm

i'm facing this error and solving it by this link: http://www.ldap389.info/en/2011/04/14/the-winrm-client-cannot-complete-the-operation-within-the-time-specified/ the problem related with WinHttp Setting. Mohamed Abd Elhamid Abd Elaziz Microsoft System Administrator Abdul Samad Al Qurashi Co.
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2011 12:02am

i hope the issue was solved. tell us pleaseMohamed Abd Elhamid Abd Elaziz Microsoft System Administrator Abdul Samad Al Qurashi Co.
August 8th, 2011 5:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics