Solved

Changed internal server IP now external OWA not working! Grrrr.......

Posted on 2006-10-24
27
331 Views
Last Modified: 2008-02-01
Hi there

I have need to change the internal IP addressing structure of my network. All went well, with one exception. My Exchange server (2003 sp1) is working fine, emails flowing no problem at all, and internally OWA is working OK - no problems at all. The problem I do have is that external access (simply using http://internet.facing.ip.address/exchange) is now not working. The browser just sits for an age and fails to load the page. The server's public face is not behind any type of a firewall - I know it needs to be, and it will, I'm just trying to make the darned thing work.

Any advice would be deeply appreciated.

Mark
0
Comment
Question by:mgosden33
  • 13
  • 12
  • +1
27 Comments
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17795926
Does the server itself actually have a public IP address assigned to it's NIC, or is it NATted at your router?  If it is NATted, then it probably just needs the incoming port 80 traffic pointing at the new private IP address.
0
 

Author Comment

by:mgosden33
ID: 17795947
Nope - I thought of that - usually NAtted but for testing puropses the server's 2nd NIC has the public address directly facing the internet.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796012
So the server's internal IP address on one NIC has changed, but its public IP address on the second NIC remained the same?
0
 

Author Comment

by:mgosden33
ID: 17796059
correct. before the change everything was working fine.
0
 
LVL 16

Expert Comment

by:poweruser32
ID: 17796066
these ones are always strange-did you do any reboot or restart IIS -owa sometimes works for no apparent reason after a while
externally
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796088
Have a look at the properties of your Default Web Site in IIS Manager, and see if the listening IP address has been set to something other than 'All Unassigned' since the IP address change.
0
 

Author Comment

by:mgosden33
ID: 17796118
I did a reboot after the IP change. The Default Web Site is set to "all unassigned". It's a touch frustrating to say the least!
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796137
Have a look at the server's IIS Log to see if the external requests are even reaching the server.  IIS Logs are in C:\Windows\System32\LogFiles\W3SVC1
0
 

Author Comment

by:mgosden33
ID: 17796150
No - it would appear they are not. There are no log entries for the external interface - they are all internal ones.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796240
That's really strange.  The external IP hasn't changed, and I assume that nothing between the NIC and the outside world has been touched?  The Default Web Site is listening on 'All Unassigned'.  It should work.

Since your public IP address is not behind a firewall, you should be able to ping it from the Internet.  Have you tried that?
0
 

Author Comment

by:mgosden33
ID: 17796269
Yes - it pings quite happily. Slight progress (if you can call it that) from my end. The problem is not with OWA - but IIS in general. I put a holding page up as the default page if you visit http://public.facing.ip.address (as opposed to http://public.facing.ip.address/exchange). No holding page from the external address but works fine on the internal address.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796313
Yes, if there's nothing in the Default Web Site IIS log, then IIS is not receiving anything for the whole site.  In other words, it's an IIS problem, not just OWA.  Trouble is, I can't think of anything that would cause this, simply by changing the IP address on another NIC.

In what way did you change the private IP address?  Was it simply a different number in the same range (e.g. 192.168.1.1 to 192.168.1.2), or did you give your whole LAN a new range, and change the IP address to something in the new range (e.g. 192.168.1.1 to 10.0.0.1)?
0
 

Author Comment

by:mgosden33
ID: 17796331
I had to change the internal address from 10.1.51.1/255.255.0.0 to 10.85.39.20/255.255.248.0 - so effectively a new range entirely.
0
Does Powershell have you tied up in knots?

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

 

Author Comment

by:mgosden33
ID: 17796336
It's doubly weird because everything else on the network - AD synchronisation included - is working 100%
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796541
Have a look at the properties of your Default Web Site again, and click the Advanced button.  Has a host header been configured?
0
 

Author Comment

by:mgosden33
ID: 17796578
I'm now in the realms of not knowing very much (like I wasn't there before!). All that is in the advanced section is in the top window (multiple identities) & it says default on port 80. The host header value column is empty.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796659
Those are pretty much standard values.  The Default Web Site is listening on All IP addresses (All Unassigned) on the default port (80), and there is no host header, so there is no reason why it should not work - assuming that the requests are landing at the NIC in the same way, and it sounds like nothing has changed in that respect.  Have a look at the drop-down list that is currently set to All Unassigned.  It would be a good test if you could possibly change it to 10.85.39.20 for a few seconds, and see if that makes any difference.  This will mean that the OWA installation is not available from the LAN for the duration.
0
 

Author Comment

by:mgosden33
ID: 17796787
OK - I changed it to the 10. address and it worked fine from inside and not externally (same problem). Changed it to the external address and it stalled as before from outside and then failed and internally it immediately returned a "Bad Request (Invalid Hostname)" error.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796845
Are you testing the external IP address from a computer on the LAN, or are you doing this with a computer that's actually off-site, or a dialled-up (to an ISP) laptop?
0
 

Author Comment

by:mgosden33
ID: 17796865
A computer which is directly plugged in to the router using the same external address range as the server's trying to use.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17796901
How about if you try to go to http://external.ip/ from the server itself, not the other computer?  BTW, make sure that the Default Web Site IP is back on 'All Unassigned'.  Unless you already did?
0
 

Author Comment

by:mgosden33
ID: 17796925
I have switched back to "all unassigned". If you try and access the external.ip address from the server it fails with the same problem. Using the internal IP is fine.
0
 
LVL 31

Accepted Solution

by:
LeeDerbyshire earned 500 total points
ID: 17796961
Well, I am stumped, and now I have to go home for the day.  I will see if I can think of anything else later.
0
 

Author Comment

by:mgosden33
ID: 17796972
OK. Thanks for everything so far!
0
 
LVL 6

Expert Comment

by:Michael S
ID: 17798169
You have dual NIC's?  If you're not doing any kind of load balancing or multi-nic setups, try disabling one of the NIC's and using the one you've configured with the new IP address.
0
 

Author Comment

by:mgosden33
ID: 17801676
Fixed! When I was changing the IP addresses I set the Default Gateway to the internal NIC address - it was 11pm on Sunday and I wasn't thinking straight. I've set it to the internal address of my NAT box and all is well! Thanks Lee & latterly Jay for helping out. Lee - you get the points for being a mine of ideas. Thanks.
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 17801755
You know, that crossed my mind, but when you said that pinging the server worked okay, I thought it couldn't be that.  Anyway, I'm glad it's fixed.
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

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
how to add IIS SMTP to handle application/Scanner relays into office 365.

914 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now