|
| autodiscoverredirect issues in Vista SP1 |
 |
Thu, 28 Feb 2008 04:51:18 +000 |
We have some test clients here at our site, and recently installed the final
release of SP1. Now all the sudden the machines that have SP1 don't like the
cname shell game HMC 4 plays with autodiscovery. I get the
autodiscover.clientdomain.cc "the name on the security certificate in
invald or does not mch" If I click yes everything is fine just as it was
pre-Vista SP1. What changed in SP1 that can be undone to allow compatibility
with the HMC autodiscovery process?
Is anyone else having similar problems.
Thanks,
Kurt
|
| Post Reply
|
| Re: autodiscoverredirect issues in Vista SP1 |
 |
Sun, 2 Mar 2008 16:36:57 +0000 |
Anyone else run into this yet? Do I have my autodiscoverredirect with SSL setup
incorrectly?
Thanks ahead of time for any help or insight.
Kurt
|
| Post Reply
|
| Re: autodiscoverredirect issues in Vista SP1 |
 |
Thu, 13 Mar 2008 18:37:34 +000 |
Bump
|
| Post Reply
|
| Re: autodiscoverredirect issues in Vista SP1 |
 |
Wed, 19 Mar 2008 15:37:29 +000 |
Now that SP1 is publicly available anyone have any ideas for me? Thanks!
|
| Post Reply
|
| Re: autodiscoverredirect issues in Vista SP1 |
 |
Wed, 19 Mar 2008 15:45:38 +000 |
The solution from Alex from another post below is what fixed it just now. Weird
that it would work flawlessly until SP1 is install on Vista. XP and SP0 Vista
didn't have any issues. >>>>>>>>>>> Yes, this
was long time ago. In firewall rules allow 443 (not 80) for autodiscover and 80
(not 443) for autodiscoverredirect inbound Alex
<<<<<<<<<<
|
| Post Reply
|
|
|
|
|
|
|
|
|
|