• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1895
  • Last Modified:

No access to OWA since public IP address change.

I recently needed to change our static public IP address for our domain so our network could use a new fibre link rather than an older slower copper one. Our Exchange server 2010 on an SBS 2011 DC had worked and run OWA fine until the change-over. Now my users can't log in remotely athough OWA works fine internally.

I also changed the router from a Netgear FVS318 to a Cisco-branded Lynksys RV042 for a VPN to a branch office and have forwarded both ports 80 & 443 on the router to the Exchange server but externally only port 443 appears to be open and traffic can't pass through 80 to the server. Our ISP has confirmed they are not blocking port 80 and I can telnet the server on 80 from the internal network.

Looking at the IIS Manager i notice that there is a question mark over the globe for 'Default Web Site' and there doesn't seem to be a clue as to what the ? mark is referring to.

Would the server be blocking access via HTTP to port 80 from the router? Could there be an issue with the bidings. Or could I have a fault with the router?
0
astgpaul
Asked:
astgpaul
  • 3
  • 3
  • 2
  • +1
4 Solutions
 
micropc1Commented:
My first thought would be an issue at the gateway. Have you checked your NAT configuration and firewall settings?
0
 
Neil RussellTechnical Development LeadCommented:
What you dont mention is have you changed your external DNS records that point at your webmail ?
This will need to point to your new external IP and not the old one.
0
 
DavidPresidentCommented:
A few things
 - make sure all those registry settings and configuration files don't have the IP number hardwired in any of the OWA services.

You might also create another OWA instance (been years, I THINK you can do this) that uses the domain name, and just see if that instance works.  If it does, then you are home free.

Purge all arp tables & DNS stuuff
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
astgpaulAuthor Commented:
Thanks for all coming back so quickly. I'm wondering if this is a certificate issue. If I try to connect using https I get a warning about an insecure site, accept the warning, register the exception and then get a 404 Not Found 'The requested URL /owa was not found on this server'
0
 
Neil RussellTechnical Development LeadCommented:
I repeat as you have not answered. Have you updated your external DNS records and confirmed that replication/propergation has taken place?

do you get the correct IP address if you try

PING yourwebmailserver.yourdomin.com  from an EXTERNAL computer?
0
 
astgpaulAuthor Commented:
Neilsr - I have considered your comments about the dns records and I'm going to look into this when the domain hosting company open in the morning (I'm in the UK).

Thanks - I'll let you know.
0
 
DavidPresidentCommented:
If you can get to a unix box do this, assuming your domain is xyz.co.uk and dns is ns0.myisp.com


nslookup
set host ns0.myisp.com
set type=any
xyz.co.uk.

This will reveal everything that the DNS server is putting out there, including the MX records and the TTL.

You can then repeat by doing another set host  and use a different name server, to see what any nameserver of your choice is presenting.  Maybe one of your internal machines or the sbs server itself is wrong.
0
 
astgpaulAuthor Commented:
Thanks to those that provided suggestions. It would appear the router can't port forward 443 while also handling VPN.
0
 
DavidPresidentCommented:
Really? What router is that.  (So I can be sure to avoid that POS)
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now