patcheah
asked on
Certificate error prompt out from outlook
Hi Expert,
I have a users, when open outlook, certificate error prompt out ( pls refer attachment) , after view the certificate, it was not from outlookanywhere.
After google, found out that the certiticate IP is 192.168.168.168 is refer to sonicwall. We have sonicwall, but from different branch, and this user have sonicwall vpn client installed, but has been some time he didnt use this vpn.
remarks: sonicwall has not been renewal for a year.
please advise
Thanks
problem.jpg
I have a users, when open outlook, certificate error prompt out ( pls refer attachment) , after view the certificate, it was not from outlookanywhere.
After google, found out that the certiticate IP is 192.168.168.168 is refer to sonicwall. We have sonicwall, but from different branch, and this user have sonicwall vpn client installed, but has been some time he didnt use this vpn.
remarks: sonicwall has not been renewal for a year.
please advise
Thanks
problem.jpg
ASKER
Hi David,
Im not an expert,
My outlook anywhere cert is purchased from godaddy, is not a self signed cert. As for the IP, i dont think users will access the page through IP as he is not a computer expert as well.
i wanted to know why this cert will prompt out? Sorry, your english migh be too deep for me. Might need you to explain in a simple english.. Thanks
Im not an expert,
My outlook anywhere cert is purchased from godaddy, is not a self signed cert. As for the IP, i dont think users will access the page through IP as he is not a computer expert as well.
i wanted to know why this cert will prompt out? Sorry, your english migh be too deep for me. Might need you to explain in a simple english.. Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
since it is a self-signed certificate it will have to be imported into each computers trusted root providers.
Problem 2: the subject name is an ip addess which unless the outlook users are accessing the site VIA the ip address you will get an error. as the name 192.x.x.x doesn't match the servers fully qualified domain name
it has nothing to do with the sonicwall