Accessing Exhange 2007 OWA with Edge Transport Role

I have a new, clean install of Exchange 2007 on one server and could successfully send and recievie e-mails as well as access OWA. I then installed the Edge Transport role on another server and successfully subscribed the servers together. Since then I can access the OWA logon screen locally but cannot login. Also I cannot access OWA from the External address at all.

Both servers are brand new HP DL320 and new installation of Exchange 2007. The public IP address after the standard install was pointing to the Exchange server and then changed it to the NIC of the EDGE Transport server. I can successfull PING my mail.domain.com and webmail.domain.com both times to the same public IP.

Why can I not access or logon to OWA after installing the edge transport role?
Dennis JansonIT ManagerAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MesthaConnect With a Mentor Commented:
If you are running Edge and CAS then ideally a second IP address would be required.
If your firewall can do port forwarding where different ports go to do different addresses then https would go to CAS and 25 to Edge.

Simon.
0
 
MesthaConnect With a Mentor Commented:
Edge doesn't have the client access role - it is for SMTP traffic only.
For OWA you will need to open port 443 to the server with the CAS role.

Otherwise the deployment of Edge should not have stopped OWA from working correctly, so its deployment is probably unrelated.

Simon.
0
 
Dennis JansonIT ManagerAuthor Commented:
That seams simple enoough but it worked properly before, but nothing else in the environment has changed other then moving the IP and installing the edge transport server. Why would I get the internal OWA logon screen and then timout when I try to log in?  
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Dennis JansonIT ManagerAuthor Commented:
Does OWA need its own public IP for external access?
0
 
Dennis JansonIT ManagerAuthor Commented:
I was thinking I may need a second IP address, though I have only a few to work with wo I was hoping I didn't have to. I will test it today and come back with a proper answer.
0
 
Dennis JansonIT ManagerAuthor Commented:
Okay, I have a public IP record pointing at my Exchange server using host record webmail.mydomain.net
and my external URL for OWA properties is http://webmail.mydomain.net. And I cannot access OWA through this URL. Any ideas?
0
 
MesthaConnect With a Mentor Commented:
Firewall?
If you use the IP address on its own, does that work?

Simon.
0
 
Dennis JansonIT ManagerAuthor Commented:
Yes it does! Which lead me to believe that it was a DNS issue. I had ran out of availible IP address but I was able to get a new block from my ISP however it replaced my old block so I had some reconfiguration to do.

 What we did to fix the problem was originally we had a host record with godaddy.com set to webmail.mydomain.com pointing to "my ip address". We also had a CNAME with "webmail" pointing to "webmail.mydomain.com". We proceded to remove the webmail CNAME and it immediately began to work with just the host record. Thanks for pointing me in the right direction!
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.