locked
exchange 2003 owa not working on internal network RRS feed

  • Question

  • for some reason owa is not working on our internal network - it works fine when I try to connect from home - not sure what might be causing this?

    I can connect via IP

    • Edited by cinek12 Tuesday, June 19, 2012 9:31 AM
    Tuesday, June 19, 2012 9:31 AM

Answers

  • Create a entry in the host file and test.  Clear cache or even reboot a client PC and test after modifying the host file.

    Sukh

    • Marked as answer by cinek12 Wednesday, June 20, 2012 8:06 AM
    Tuesday, June 19, 2012 9:53 AM

All replies

  • Hi,

    What happens when you try - any error message?

    Leif

    Tuesday, June 19, 2012 9:41 AM
  • This web page is not available 

    The server at  can't be found because the DNS look-up failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network.

    I have checked the dns forward lookup zone and the ip is pointing to the correct server

    • Edited by cinek12 Tuesday, June 19, 2012 9:47 AM
    Tuesday, June 19, 2012 9:46 AM
  • Clear/Flush DNS cache on server and clients and test.

    Does it work on the Exch server itself?


    Sukh

    Tuesday, June 19, 2012 9:48 AM
  • already tried that, doesn't work on exchange server itself either 
    Tuesday, June 19, 2012 9:49 AM
  • Create a entry in the host file and test.  Clear cache or even reboot a client PC and test after modifying the host file.

    Sukh

    • Marked as answer by cinek12 Wednesday, June 20, 2012 8:06 AM
    Tuesday, June 19, 2012 9:53 AM
  • you mean I should remove the entry for the server  from dns?
    Tuesday, June 19, 2012 9:57 AM
  • no, justr add one to the host file locally on a client and test.

    Sukh

    Tuesday, June 19, 2012 9:58 AM
  • doesn't work either 
    Tuesday, June 19, 2012 10:09 AM
  • Hi,

    Can you ping the server? (it sounds like a network issue)

    Leif

    Tuesday, June 19, 2012 10:31 AM
  • yep, I can ping the server by ip address and i can access owa via ip address
    Tuesday, June 19, 2012 10:33 AM
  • Is there anything between the clients on the LAN and Exch server? I.e firewall/ACL's etc?

    ANy firewall on the clients or server?


    Sukh

    Tuesday, June 19, 2012 10:33 AM
  • nope, no firewalls - it was working fine, then we moved the dns server to another server and now it stopped working - everything else works fine
    Tuesday, June 19, 2012 10:36 AM
  • What happened with the old dns server? Are they windows DNS server (ADS integrated)?

    You can successfully doa nslookup against all DNS servers for that IP/Name and resolution works fine?

    Did you use a split DNS config for OWA?

    Have you checked your internal URL's for OWA?


    Sukh

    Tuesday, June 19, 2012 10:58 AM
  • 1. old server is long gone

    2. I can do nslookup against all dns servers for the exchange server ip

    3. no idea

    4. how do I find the internal url for owa?

    Tuesday, June 19, 2012 11:05 AM
  • 4. I was thinking Exch 2010 here, this is about 2003. Forget that.

    I assume you've performed an IIS reset at some point?

    I'm thinking going down this route. BUT the error above suggests it's a DNS issue, in addition this only seems to have happened when the DNS server was moved. So I would focus on that more before thinking about the reset or vDir.


    Sukh

    Tuesday, June 19, 2012 11:14 AM
  • I have restarted the ISS server
    Tuesday, June 19, 2012 11:16 AM
  • We just tested locally on the Exch server itself and failed.

    So if your go to http://fqdn_of _Exch_svr/Exchange on the server it fails too~?


    Sukh

    Tuesday, June 19, 2012 11:23 AM
  • if I go to the external link which is office.domain.co.uk/exchange it doesn't work on the server either

    if I go to servername.domainname/exchange it works

    Tuesday, June 19, 2012 11:34 AM
  • Well, you may have been using split DNS.

    Does the same URL work on a client PC if using the FQDN and NOT the office.domain.co.uk/exchange?


    Sukh

    Tuesday, June 19, 2012 11:37 AM
  • right now I'm trying it on my pc (internal) servername.domainname/exchange it also works on all other internal pcs but it  won't work outside only office.domain.co.uk/exchange which atm doesn't work internally nor externally 
    Tuesday, June 19, 2012 11:43 AM
  • There's some confusion here.

    To simplfy, internal user should be connecting using the FQDN which seems to be working.

    External users should be using the office.domain.co.uk which is or isnt working extenally?


    Sukh

    Tuesday, June 19, 2012 11:46 AM
  • both internal and external users should be using office.domain.co.uk/exchange to access owa if not using outlook which doesn't work internally 

    I've been going through the dns forward lookup zone and I can't see office.domain.co.uk entries - should there be any?

    sorry - the previous post should say it doesn't work internally only 

    • Edited by cinek12 Tuesday, June 19, 2012 11:48 AM
    Tuesday, June 19, 2012 11:47 AM
  • That's what split DNS would be, seems like this may have been setup on the old DNS server.  Create this zone, and the A record and test again.

    So Exch is working as it should, it's a DNS issue, which seems like hasn't been setup as the old server.

    Do the Split DNS config.


    Sukh

    Tuesday, June 19, 2012 11:54 AM
  • I don't remember having a split dns on the old server -  there was only one zone which currently exists on the new server 
    Tuesday, June 19, 2012 1:17 PM
  • Tuesday, June 19, 2012 1:38 PM
  • added an entry to the host file on a vm and it worked - added a entry in the dns server and it works - thanks! 
    Wednesday, June 20, 2012 8:26 AM