Can't log into PowerShell and EAC on Exchange 2013 Server

I'm not sure why but I my Exchange PowerShell can't log into my Exchange server and I can't access the EAC via localhost or the URL.

I did notice that I enabled HTTP Proxy in IIS and that I used Application Route Requesting with it but I went ahead and reversed all those changes. I also noticed that the physical path for each sub-site in Default Web Site goes to the HTTP Proxy version of that folder instead of the ClientAccess one. I changed each folder to the clientaccess one but that didn't help. I did some research on this and I saw that I had to enable the kerbauth in the modules area and I did that to. I restarted IIS and WebRM and that still didn't help.

The Exchange Management Shell error:

New-PSSession : [exchangeserver.domain.net] Connecting to remote server exchangeserver.domain.net failed with the following
error message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed

On the web when I try to access EAC on our URL and not localhost, I get this error:

400 Bad Request :(

The request sent by your browser was not valid

On localhost, I just get a page cannot be found.

March 4th, 2015 4:35pm

Hi

Can you remove /recreate powershell virtual directory and see the results

To delete the virtual directory

Get-PowershellVirtualDirectory | Remove-PowershellvirtualDirectory

To create Virtual Directory

New-PowerShellVirtualDirectory -Name Powershell -RequireSSL:$False

Free Windows Admin Tool Kit Click here and download it now
March 12th, 2015 9:58am

Hello CharGP02A,

You mention you restarted WebRM, did you mean to say WinRM?

First thing you should do to troubleshoot this is disable any AV software you may have running and then try to connect again, if it works now, that is your problem, probably a 3rd party firewall issue.

If not, please check WinRM configuration is properly configured by running:

Drop to an elevated cmd prompt and execute "WinRM QuickConfig"
You will be asked a Yes or No on a few questions, just say Y to everything, now run it again until you see "WinRM already is set up to receive..." and WinRM already is set up for remote..." results. YOu may need to run this more than once to get it to show both.

Now check the services, and check the
WS-Management or Windows Remote Management
World Wide Web Publishing
IIS Admin

Make sure each is running and each is set to Automatically start.

Next go to IIS and look at the Default Website, Is it running? If it isn't start it up.

Check to see if you can connect.

Some more things to try:

Does this happen only on the Exchange Server, ie. can you get to EAC from any other box?
Also are you able to hit OWA itself, or run Management Shell from the Server?

If this is just a website error, meaning you can hit it from other systems, just not from the server, usually there can be issues connecting to websites hosted on the server you are connected on, but doesn't happen often in Exchange. You could try setting LSA to allow the website local access by configuring backconnectionhostnames value in the registry:

Go to HKEY_LM\System\CCS\Control\LSA\MSV1.0 and add a DWORD value if it doesn't exist of "BackConnectionHostNames" then open it up and add the base url without http or anything, just the URL you are trying to hit.

YOu may need to do an IISRESET after setting it, but sometimes you don't. Give it a try now, if it doesn't work, try the IISRESET.

Hope this helps you,

Hugh
Please remember to mark as an answer if this helps!

March 12th, 2015 11:05am

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

Other recent topics Other recent topics