OWA does not working

OWA does not work with mail.domainname.org/owa, but works with servername/owa
rsilver24Asked:
Who is Participating?
 
wfcraven12Connect With a Mentor Commented:
Glad that worked out.

I would suggest posting the other two issues separately.  Everyone will see your issue with the Backend & SSL & may have the correct solution faster than me.  

But FWIW, I believe you should just go to your BE exchange server & pull up the properties for the server in ESM & in the General tab there is a check box that specifies whether it's a front end or back end server.  Like I said though, make it a separate question b/c I may be way off.

Regarding the certificate, it sounds like you need to issue a new certificate with the URL & apply that to IIS on your ESM front end server.  but again, post this issue separately.
0
 
wfcraven12Commented:
sounds like a DNS issue really.  Are you able to connect to OWA from the outside?
0
 
rsilver24Author Commented:
No, but I can ping it by name from the outside
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
wfcraven12Commented:
you can ping IP 1.2.3.4 but you can't go to the address 1.2.3.4/owa?

have you put https://1.2.3.4/owa in the address bar?
0
 
rsilver24Author Commented:
Yes I have tried that.  It does not work either.  Is it possible it has something to do with the firewall blocking port 443?  I looked at my Firewall, I am running SonicWall and it appears that traffice is open for port 443, but I am not sure if I have to specify that port for OWA.  Please advise.

Thanks,

Rina
0
 
wfcraven12Commented:
whenever you put https it is specifying port 443.  If the firewall is blocking 443 then you definitely are not going to be able to connect to it.  

pull up command prompt & type the following (1.2.3.4 being your owa IP address)

telnet 1.2.3.4 443
0
 
rsilver24Author Commented:
Connection failed
0
 
wfcraven12Commented:
okay your FW is blocking 443.  You need to get over that hump first.
0
 
rsilver24Author Commented:
That is what I thought.  I also thought it was opened, but I need to contact Sonicwall.  Unless there is anything you can suggest.

Thanks,

Rina
0
 
wfcraven12Commented:
I would contact the vendor to make sure that 443 is open for that IP address from outside traffic.  Keep them on the phone until you can telnet to that IP
0
 
rsilver24Author Commented:
Thanks I opened the port and OWA is working.  I now have 2 other issues.  How do I uninstall Client Access from my Exchange BackEnd Server?  I have Client Access installed on a front end server already and want to make sure the users are only accessing OWA from that server.  The other issue I am having is when I ran tha ActiveSync Analyzer, I received the following error

Testing the SSL certificate to make sure it's valid.
  The SSL certificate failed one or more certificate validation checks.
     Host name mail.domainname.org doesn't match any name found on the server certificate CN=ServerName.  This is actually the server name of the server I want to uninstall the Client Access from.  How to I make sure I am using the correct certificate on the correct Client Access Server.

Thanks,

Rina
 
 
0
 
rsilver24Author Commented:
Thank you I will post 2 separate questions.  Thank you for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.