asked on

Exchange Management Console Failed to Open

Hi,
I have Exchange 2010 server and every other day the management console failed to open. The error varies and this time is "Powershell Kerberos failed to authentication". "Access Denied to connect to remote server". By the way, the exchange server is not domain controller.

Can someone help me please?

Thanks a lot!

ASKER CERTIFIED SOLUTION

Manpreet SIngh Khatra

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

xDUCKx

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

lgallion

ASKER

I only have one exchange 2010 server and no roles installed. DC/GC is running fine. shell gave me same error. it asked enter FQDN to connect server and it said pssession open failed after I typed in FQDN. I tried logoff and log back in and it didn't work.

SOLUTION

Adam Brown

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

lgallion

ASKER

I have 2 http 80 no binding and 1 https 443 no binding. Is it ok to delete them?

Manpreet SIngh Khatra

As per the error it seems surely a connection drop with the DC\GC at that moment.

- Rancy

Adam Brown

Can you post a screen grab of your binding list?

lgallion

ASKER

I deleted them and it gave me WimRM error. I put them back.

Adam Brown

Go through your bindings and just make sure that each of them are bound to the Server's IP or 127.0.0.1. If none of the existing bindings are bound to the server IP, change them to reflect that. You should have something that looks similar to the attached image (Ignore the port 444 entry, since that's something else on my server)
IIS-Bindings.JPG

lgallion

ASKER

Mine is like this Please see the attachemnt. Shall I delete extra http?
IIS-Binding.docx

Adam Brown

Edit the 443 entry with no binding and set it to an IP of "All Unassigned".

lgallion

ASKER

it set to All Unassisgned already.

lgallion

ASKER

Sorry I ment to attch this image.
IIS-443.docx

Adam Brown

Hit ok on that and it should show that the binding has an IP address now, and all your bindings should be valid after that. Then try out the management console.

lgallion

ASKER

I called Microsoft and they fixed my replication/DNS problem. The mangement console can be able to load now! Thanks a lot for your help!!