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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SLOW!!! Outlook performance

Status
Not open for further replies.

mikieL

MIS
Oct 10, 2000
1
US
Running Outlook2000 on Win98 workstations. Exchange 5.5 server on NT4.0. Some stations=very quick response, loading, mailing, etc. Others are so slow, can't be used practically in business environment. Same workstation equipment! Intel (Dell) 350's. Any suggestions? [sig][/sig]
 
Hi,

Do you have a hosts files in the c:\windows folder
basically its a text file in the format

ipaddress <tab> server name

ie

1.2.3.4 PDC1
5.6.7.8 BDC1
9.10.11.12 EXCHANGE1
13.14.15.16 PROXY

That should help to speed things up


Paul [sig][/sig]
 
Hi,

Do you have a hosts files in the c:\windows folder
basically its a text file called &quot;hosts&quot; in the format

ipaddress <tab> server name

ie

1.2.3.4 PDC1
5.6.7.8 BDC1
9.10.11.12 EXCHANGE1
13.14.15.16 PROXY

That should help to speed things up


Paul [sig][/sig]
 
When does windows read the hosts file? Start up? Log in?

Also do you need to have LMHOSTS enabled in advanced TCP/IP settings first?

Thanks

Phil.
 
Is it only interaction with the Exchange server when the slowness occurs? For instance, if you bring up Outlook offline does it have a better response time or is still slow?

Do the clients have personal folders on a network drive by any chance and if so how big are they? If you remove all components but the Microsoft Exchange server does Outlook respond better? joegz
&quot;Sometimes you just need to find out what it's not first to figure out what it is.&quot;
 
I've seen this where it's a name resolution problem for the server. LMHOSTS is the file you need for netBios name resolution. HOSTS is for DNS.

Are you running WINS? If so, check the database for correct Exchange server mapping.

Name resolution is done at boot up. Name checking is done in this order:

Check whether the queried name belongs to the local machine.

Check the local name cache, which by default retains resolved names for 10 minutes.

Direct a point-to-point query to the configured WINS server or servers.

Use a broadcast query.

Use a local LMHOSTS file, if one exists.

Use a local HOSTS file, if one exists. (A HOSTS file resides in the \%systemroot%\system32\drivers\etc folder on Win2K or NT systems or in the Windows folder on Win9x systems.)

Issue a point-to-point query to any configured DNS serve.
 
To add to Joegz's response, and if I understand the problem to be some users have slow while others have nornal response times, have you had a &quot;slow&quot; user log on to a &quot;normal&quot; users station?

If the problem persists I would say the &quot;slow&quot; user has something wrong with a .pst, .ost, .pab etc. or has those files loaded on a slow file server or similar problems.

If the problem disappears I would say the &quot;slow&quot; user has a problem at his/hers desktop level.

Much luck
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top