Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Microsoft Exchange Server is Unavailable ...

Status
Not open for further replies.

bsorenson

IS-IT--Management
Feb 21, 2003
3
US
We are connecting external users over the Internet from Outlook 2000 to our Exchange 2000 server and having problems. We get the "Your Microsoft Exchange Server is Unavailable" after a 30 second timeout. We get the "Retry" option, and after retrying once or twice get the login popup.

The clients are running anything from Win98 to WinXP, and are all having the same issue. We've tried LMHOSTS files, putting our Mail server address in DNS (mail.ourhost.com - 216.210.210.210), and a few other things.

We also need to sync Palms over the Internet, and are having the same kind of issues there. We're using the Intellisync product, and setting up a local copy of Outlook to sync to Exchange, and then syncing to that local Outlook copy.

Any ideas to try?
 
Is there a firewall between the Exchange server and users?
 
Did you ever resolve this? I have the same problem with getting the messages: "Your Microsoft Exchange Server is Unavailable" after a 30 second timeout. We get the "Retry" option, and after retrying once or twice get the login popup.

The location with the problem runs Windows2K Server with XP clients. They connect via a LINKSYS VPN box to an identical box on our other campus' Exchange server.
 
Change the timeout to 90 seconds and make sure the firewall ports are open.

GlennA
MIS






 
I am having the Server not available problem with XP Outlook 2000 clients connecting over a frame relay link to my exchange 2000 server. It worked fine until October 15th and now they have trouble connecting. The timeout is set at 60 seconds and they click Retry 4 or 5 times before it will connect. Once connected, Outlook will work normally.

I know that I haven't made any changes on the firewall or the server or the clients. They just quit working the 15tht. I have 2 windows NT 4.0 with Outlook clients at the same branch office and they can connect without problem. I've reinstalled Office, reinstalled networking, rebooted the firewall. They can browse to the server via network neighborhood. I have them accessing the server via Outlook Web Access for now. But, they want their Outlook back and I am at a loss on what to try next. The only information I found was that maybe a worm on Port 445, but their virus scan is up to date and doesn't detect a virus. I am now investigating sun spots and curses as a possible cause! If anyone has an idea, I would appreciate hearing it. Thanks, Alice
 
How long does it take for the pcs to log on?
Are they in the domain or not?

GlennA
MIS






 
I have been expirencing the same problem. We also tun a CISCO PIX. I have opened all known ports suggested by MS for exchange 200 to run on the outside, but still get the timeout. Any answers to this question?
 
I'm experiencing the same problem...has anyone solved this??

thx
g.
 
We have been successful by stopping using Outlook XP or Outlook 2002 and using Outlook 2000. We just reinstall Outlook 2000 in a different directory, setup the profile, and it works immediately. We did have to open ports on the PIX before it worked. I can't remember the ports specifically.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top