One for Chad / Nominous - OWA on Exch.2K

[BassAddict]

Anyone else feel free to answer by the way !!
Just had an Exch.2000 Outlook Web Access server moved to a different vlan so its IP address has changed, everything appears to start ok, but then the Exchange Virtual Server (in IIS) stops, saying its unable to access the M: drive thats created for Exchange OWA.
When you try and connect to it you get "HTTP/1.1 503 Service Unavailable" - found a few articles but none are relevant - it doesn't do any other hosting on this server, only the OWA.
Strangely though, if you close and re-open the port it needs on the firewall it starts working again - so we can't figure out if its the server, or the new firwewall its behind ! Any thoughts ?!!! :)
Rich

[nominous]

Is it working internally ?
If you've changed the IP did you open a port on the firewall to a specific address and now the IP has changed have you changed the IP it forwards to?
(start simple)

[BassAddict]

Works internally when working externally, then just drops out completely until the firewall is tinkerd with by the comms guys, then it works again for say 30 minutes, then bombs out again - no errors in the 2K event logs or IIS logs, and no errors on the comms kit I'm assured... :?
NAT'd address is defo set right on the firewall as it works for a while then gives up - can't help but think its gotta be a prob with the server, even though it seems start working again by tinkering with the firewall (cisco pix)
rich

[ChadH]

Once it's stopped working externally, does it still work internally?
Sounds defintely firewall related. What model firewall do you have, and what ports are you forwarding internally?

[BassAddict]

Once its stopped it goes both internally and externally - unfortunately I dont have any kind of access to any of the comms kit - including the firewall - all I know is our comms setup has about 25 full height racks of large cisco boxes !!! Sounds a lot, but we've got offices at every uk airport, loads of call centres, about 1000 shops and hundreds of foreign resort offices !!!
Rich

[ChadH]

OK, if it goes internally too, then it must be a server issue - just to check, when you use it internally, do you use a different IP address to using it externally? Are you getting anything in the event logs at about the same time? What Exchange service pack are you using? Do any of your other internet sites go down - ie is IIS still running OK?

[BassAddict]

Yup - internally its on a private ip range 10.blah.de.blah (can't remember the external address from home - I always connect via vpn and run everything as normal!). Nothing in the event logs when it goes, according to IIS admin its still up and running (its only occasionally it has this error accessing the exchage virtual directory), buty there's no other sites on this box to test at the same time (other intranet and internet sites on different servers are all fine still)
Rich

[ChadH]

You could try checking the DNS entries for the server - there may still be some entries pointing to the old IP address. Even though you access it by IP number, it will probably still use the IP names behind the scenes. Also use Exchange Sytem Manager->Servers->Protocols->HTTP to check the settings - sometimes OWA reacts strangely if you make changes in IIS instead of Exchange System Manager. Have you got the latest service packs and patches?

[BassAddict]

The DNS settings are ok - checked them on Friday - haven't checked http settings via Exch Sys Man though - I'll look at the on Monday - ta !!! :)
Pretty sure SP level is upto date - not so positive on the patches though !
Rich

[ChadH]

It could be the ESM settings then. I seem to recall that if you tell it to listen on a different IP address in IIS, then the ESM settings override it a bit later on. All from memory though so it could be wrong!

[BassAddict]

Hmm, if you try and use ESM to manage the server you get "You must use IIS to manage this virtual server" !!!! :?
Rich

[ChadH]

Ah, you're using the one that's a subdirectory of the Default website. I usually create another webserver listening on the same IP address but with a different hostheader (eg exchange.domain.com instead of server.domain.com/exchange). That one can be configured from ESM where it looks like the default one can't be - sorry didn't realise.

How about doing it the way I just suggested though - you could create another website - you will need to be able to change DNS settings internally and externally, and then have it listening on the host headers you've set up. If it works, then you'll be able to tell that IIS is at fault. If you do it this way, you will be able to leave the existing method of access in place too.

[BassAddict]

Hmm - seems to be working fine today for some bizarre reason !!!! Quite handy though !!!
Like the idea of it being its own sub-domain though - might try your method if it goes again - wont try it just yet though due to the amount of bullsh*t paperwork you have to go through here to change absolutely anything !! :) !!!
Rich