Link to home
Start Free TrialLog in
Avatar of liminal
liminal

asked on

OAW SSL Cert Bindings

Have a strange problem with my IIS, I have created a new binding that covers all unassigned IPs on port 443 with no host name and my proper SSL cert. But when accessing from a browser, it just shows the self signed cert?

There is another binding for 127.0.0.1 thats has the selfsigned on it. But that should not interfere right?  

Any ideas?
Avatar of VB ITS
VB ITS
Flag of Australia image

Is this SSL certificate for Exchange? If so you should assign the certificate either through the Exchange Management Console or Exchange Management Shell.

See this article for the relevant steps: http://technet.microsoft.com/en-us/library/dd351257%28v=exchg.141%29.aspx
Avatar of liminal
liminal

ASKER

I have done that, should I have left just left the bindings in IIS alone?
Yep, no need to touch them. Try re-applying the certificate through EMC or EMS. If that doesn't work, remove the self signed certificate that's bound to 127.0.0.1
Avatar of liminal

ASKER

Ok, so im trying to remove the authorised cert. Then re add and apply all the services. But I cant untick the services?
Avatar of liminal

ASKER

Right, so I worked that out, removed and readded and then reapplied all the services. But its still not working.

SO you say, remove the self signed from within EMC?
Did you remove the binding to 127.0.0.1 within IIS Manager?
Avatar of liminal

ASKER

Interestingly its working for ECP, but not OWA :(
ASKER CERTIFIED SOLUTION
Avatar of VB ITS
VB ITS
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of liminal

ASKER

Yup that was it.

Thanks mate!
Glad we got there in the end :)
Avatar of liminal

ASKER

No, removing that binding in IIS broke it again and now I cant get into anything :(
Argh! Try re-assigning it again through EMC.