Hi,
What happens when you try - any error message?
Leif

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

Clear/Flush DNS cache on server and clients and test.
Does it work on the Exch server itself?Sukh

Need to support users over the internet? click here try our remote control online beta

already tried that, doesn't work on exchange server itself either

There is an amazing pack of free network admin tools. click here to download it

Hi,
What happens when you try - any error message?
Leif

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

you mean I should remove the entry for the server from dns?

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

no, justr add one to the host file locally on a client and test.Sukh

Need to support users over the internet? click here try our remote control online beta

Clear/Flush DNS cache on server and clients and test.
Does it work on the Exch server itself?Sukh

Need to support users over the internet? click here try our remote control online beta

already tried that, doesn't work on exchange server itself either

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

you mean I should remove the entry for the server from dns?

Need to support users over the internet? click here try our remote control online beta

doesn't work either

Need to support users over the internet? click here try our remote control online beta

no, justr add one to the host file locally on a client and test.Sukh

Need to support users over the internet? click here try our remote control online beta

doesn't work either

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

yep, I can ping the server by ip address and i can access owa via ip address

Need to support users over the internet? click here try our remote control online beta

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

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

yep, I can ping the server by ip address and i can access owa via ip address

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

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?

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

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

Need to support users over the internet? click here try our remote control online beta

I have restarted the ISS server

Need to support users over the internet? click here try our remote control online beta

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?

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

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

Need to support users over the internet? click here try our remote control online beta

I have restarted the ISS server

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

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

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

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

There is an amazing pack of free network admin tools. click here to download it

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

Need to support users over the internet? click here try our remote control online beta

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

Need to support users over the internet? click here try our remote control online beta

I don't remember having a split dns on the old server - there was only one zone which currently exists on the new server

There is an amazing pack of free network admin tools. click here to download it

I don't remember having a split dns on the old server - there was only one zone which currently exists on the new server

Need to support users over the internet? click here try our remote control online beta

Could have been a forward which has been setup -

http://www.techrepublic.com/article/configure-a-split-dns-system-on-windows-server-2003/6097830Sukh


Need to support users over the internet? click here try our remote control online beta

Could have been a forward which has been setup -

http://www.techrepublic.com/article/configure-a-split-dns-system-on-windows-server-2003/6097830Sukh


There is an amazing pack of free network admin tools. click here to download it

added an entry to the host file on a vm and it worked - added a entry in the dns server and it works - thanks!

There is an amazing pack of free network admin tools. click here to download it

added an entry to the host file on a vm and it worked - added a entry in the dns server and it works - thanks!

Need to support users over the internet? click here try our remote control online beta