Carl Billington
asked on
Cannot access Exchange 2010 Management Console
Hope this helps: http://support.microsoft.com/kb/2027062
ASKER
Thanks. The correct values already exist.
Have you read:
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
and more specifically:
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
and more specifically:
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx
Are you sure you're logging in with a domain account and not a local account?
ASKER
I am using the domain admin account
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
might be this one -
http://support.microsoft.com/kb/2027063
In one of my similar issues, i was unable to connect to server manager remotely and the root cause was duplicate SPN (host) of target server registered on a service account.
http://support.microsoft.com/kb/2027063
In one of my similar issues, i was unable to connect to server manager remotely and the root cause was duplicate SPN (host) of target server registered on a service account.
ASKER
Ah I see you are running SBS.
In IIS:
If you click on the Sites tree, this will give you a list of Web Sites in the right hand window and it will show your 'Bindings'
Default Web Site - will normally be bound to *:80 (http) and :443 (https)
Do you see others in that list that may now be bound to 80 or 443?
The reason I ask is, you can only bind one Web Site to a TCP port unless it's configured with a host header.
The Website you show, doesn't appear to be stopped though as it would have a black stop square icon on it.
Can you try opening https://localhost/owa and see if you can get to the webpage or does it give you an error?
In IIS:
If you click on the Sites tree, this will give you a list of Web Sites in the right hand window and it will show your 'Bindings'
Default Web Site - will normally be bound to *:80 (http) and :443 (https)
Do you see others in that list that may now be bound to 80 or 443?
The reason I ask is, you can only bind one Web Site to a TCP port unless it's configured with a host header.
The Website you show, doesn't appear to be stopped though as it would have a black stop square icon on it.
Can you try opening https://localhost/owa and see if you can get to the webpage or does it give you an error?
Hi there,
i had a similar problem after i installed Management console 2010 and THEN uninstalled Management console 2007 ON MY CLIENT ...
can you access the server from a client with a fresh installed Management console 2010 and the appropriate rights ?
greetings
i had a similar problem after i installed Management console 2010 and THEN uninstalled Management console 2007 ON MY CLIENT ...
can you access the server from a client with a fresh installed Management console 2010 and the appropriate rights ?
greetings
Do you have enough memory and other hardware.
Yeah got the same problem on the exchange direkt when he had less than 8GB after a few weeks uptime
ASKER
This was resolved because I discovered that MS Exchange IMAP service was using port 443, on automatic and was started. I stopped the service and put it on manual.
Hi,
Please confirm you have installed the winrm roles with IP6 is enabled on the network properties or not.
Please try it once and revert for further update.
Thank you
Please confirm you have installed the winrm roles with IP6 is enabled on the network properties or not.
Please try it once and revert for further update.
Thank you