exchange 2003 owa not working on internal network
Hi,
What happens when you try - any error message?
Leif
June 19th, 2012 5:41am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 5:42am
Clear/Flush DNS cache on server and clients and test.
Does it work on the Exch server itself?Sukh
June 19th, 2012 5:48am
already tried that, doesn't work on exchange server itself either
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 5:49am
Hi,
What happens when you try - any error message?
Leif
June 19th, 2012 5:52am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 5:53am
you mean I should remove the entry for the server from dns?
June 19th, 2012 5:57am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 5:57am
no, justr add one to the host file locally on a client and test.Sukh
June 19th, 2012 5:58am
Clear/Flush DNS cache on server and clients and test.
Does it work on the Exch server itself?Sukh
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 5:59am
already tried that, doesn't work on exchange server itself either
June 19th, 2012 6:00am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:04am
you mean I should remove the entry for the server from dns?
June 19th, 2012 6:08am
doesn't work either
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:09am
no, justr add one to the host file locally on a client and test.Sukh
June 19th, 2012 6:10am
doesn't work either
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:20am
Hi,
Can you ping the server? (it sounds like a network issue)
Leif
June 19th, 2012 6:31am
yep, I can ping the server by ip address and i can access owa via ip address
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:33am
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
June 19th, 2012 6:33am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:36am
Hi,
Can you ping the server? (it sounds like a network issue)
Leif
June 19th, 2012 6:42am
yep, I can ping the server by ip address and i can access owa via ip address
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:44am
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
June 19th, 2012 6:44am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 6:47am
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
June 19th, 2012 6:58am
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?
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:05am
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
June 19th, 2012 7:10am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:14am
I have restarted the ISS server
June 19th, 2012 7:16am
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?
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:16am
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
June 19th, 2012 7:23am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:26am
I have restarted the ISS server
June 19th, 2012 7:27am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:34am
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
June 19th, 2012 7:34am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:37am
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
June 19th, 2012 7:43am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:43am
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
June 19th, 2012 7:46am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:46am
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
June 19th, 2012 7:52am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:54am
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
June 19th, 2012 7:55am
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
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 7:57am
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
June 19th, 2012 8:03am
I don't remember having a split dns on the old server - there was only one zone which currently exists on the new server
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 9:17am
I don't remember having a split dns on the old server - there was only one zone which currently exists on the new server
June 19th, 2012 9:27am
Could have been a forward which has been setup -
http://www.techrepublic.com/article/configure-a-split-dns-system-on-windows-server-2003/6097830Sukh
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2012 9:38am
Could have been a forward which has been setup -
http://www.techrepublic.com/article/configure-a-split-dns-system-on-windows-server-2003/6097830Sukh
June 19th, 2012 9:48am
added an entry to the host file on a vm and it worked - added a entry in the dns server and it works - thanks!
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 4:26am
added an entry to the host file on a vm and it worked - added a entry in the dns server and it works - thanks!
June 20th, 2012 4:35am