companyweb problem

[tim555]

Some weeks ago, a company with a number of sites with individual Exchange servers, got some new mobile phones which needed access to corporate email.

I set up a router to route port 80 to the server, and in IIS opened up access to all computers and set it to not use SSL. I then configured the ActiveSync on the mobile phones and everything worked fine, including internal OWA and companyweb.

So, that was one office and I then did exactly the same on the three other offices and everything worked perfectly until last week, when one set of phones could no longer sync with the associated Exchange server.

Going onto that server directly,

http://companyweb/

is "unavailable" in IE, although

http://<server

ip address> does bring up the Welcome page with the My Company's Internal Web Site, Network Config Wizard, Remote Web Workplace and Information links, but only after a username and password popup (which doesn't happen on any other server). However, the My Company's Internal Web Site link is "unavailable", although the other links do work, but again the Remote Web Workplace link has a username and password popup (which also doesn't happen on any other server), before then showing the Remote Web Workplace login screen. If I then login, it tries to display the page but all I get is the words "Loading..." at the top and "Loading..." in the middle.

Typing

http://<server

ip address>/exchange gives an error message "440 Login Timeout".

As far as I am aware, nothing has been changed on this problem server since I originally enabled OWA for the phones and I am at a loss to solve the problem. I have compared all the setups and they appear identical.

Doesn't any of the above suggest anything to someone?

Many thanks.

 

[danielwestendorf]

Are you getting these results from inside or outside the network? Whenever I run into these types of problems, I eliminate NAT/Port Forwarding/Firewalling from the equation.

This does sound like a DNS issue though. If it is responding via IP, but not hostname, that is the first thing I would look at. Make sure all your records are pointing to the right IP. If your DNS isn't working right, it breaks a lot of stuff.

 

[tim555]

Thanks for the reply.

Although the problem came to light from external access, all the issues mentioned relate to sitting at the server, thus taking all NAT etc. problems out of the equation. I will check the DNS and see if anything comes to light.

I forgot to mention that this is an 2003 SBS server and like any other SBS installation, opening a browser at

http://companyweb

normally brings up the default company web site, which, as it happens, we do not use.

I am ignoring the phones for now, which I assume are simply a symptom of a more fundamental issue which will correct itself when the problems mentioned above are corrected.

This is the worst kind of problem, since it was working and yet nothing has been touched. Or at least, I don't think they have!?