Windows Forum

Ask something
Discussion Locked

Slow connect to Exchange 5.5

0 helpful
5 replies

by jerrykidd

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have Exchange 5.5 installed on a Win2K member server in a NT domain. I use Outlook 2000 to connect. After logging in to the domain the users start Outlook. Typically after 30 seconds Outlook will return an error message that it timed out while trying to connect. A subsequent retry will usually connect. Any idea as to what is going on?

5 replies

by curlergirl

This is probably related to Outlook's weird way of finding its server. Make sure that your DNS settings on your workstations are pointing to the correct (local) DNS server and that your DNS server has an MX record configured correctly to point to your Exchange server. If you aren't running DNS on your network, you may have to put a HOSTS file on the workstations, particularly on Win9x workstations. They are usually the slowest with resolving Exchange server names. The slowness is caused by the fact that Outlook is trying to use broadcast to resolve the server name first, then DNS - if you don't have a local DNS server and/or the DNS server(s) you are using don't have an MX record for your local Exchange server, it takes them a long timeto find the right IP address. I've tried all the TechNet stuff they say will force Outlook to use other methods but it never seems to work - HOSTS files are the most reliable. If you've never used a HOSTS file, you can find an example on any workstation in the C:\Windows folder for 9x or the \%systemroot%\system32\drivers\etc folder for NT. Be sure to remember that the HOSTS file must be saved without any extension - the sample is stored with a .SAM extension. Hope this helps!

by dao251

Sorry to comment previous answer, but DNS MX records do not relate to DNS name resolution neither to Outlook to Exchange Server interaction. Please note exchange can work without any TCP/IP, SMTP, etc.etc.

Yes, the problem could be caused by slowname resolution so you have to check how name resolution is performed on your network (in case you use pure TCP/IP network). Or, that can be caused by multiple protocols installed on your clients (say client first tries IPX and then TCP/IP but your server uses TCP/IP only).

Talking of TCP/IP:

names can be resolved using:
broadcast,
DNS
WINS
local HOSTS file
local LMHOSTS file

depending on your client node type, certain sequence of those is used. Please check MS docs about node types and name resolution.

and forget of MX records at this stage :-)

HTH,
Dima

This discussion is closed to new replies.