Title: Message
looks like a name resolution problem to me
 
do you have a #pre #dom entry in lmhosts?
 
You can also change the default protocl behaviour for outlook, search google and you'll find it. you should set the default to TCP/IP.
 
Also, unless you use it, disable instant messaging in outlook (tools/OPtions) this decreases the Outlook open time by about 30 seconds.
 
Symon
-----Original Message-----
From: Tice, Jeff (ADM) [mailto:[EMAIL PROTECTED]]
Sent: 27 January 2003 19:00
To: [EMAIL PROTECTED]
Subject: Re: [FW-1] Win XP - SecuRemote - Outlook - SLOW!!!

cable modem (T-1 speed connection)
-----Original Message-----
From: <Aaron Reynolds> [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 12:56 PM
To: [EMAIL PROTECTED]
Subject: Re: [FW-1] Win XP - SecuRemote - Outlook - SLOW!!!

Could be fragmentation.  Is this behind a DSL router?
 
-Aaron
-----Original Message-----
From: Tice, Jeff (ADM) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 27, 2003 9:19 AM
To: [EMAIL PROTECTED]
Subject: [FW-1] Win XP - SecuRemote - Outlook - SLOW!!!

Hi!

Home:
Win XP Pro sp1
Outlook XP (or 2000)
SecuRemote bld 4200 (FWZ)

Office:
Win NT 4.0sp6a
FW-1 4.1sp6

Situation -
Takes exceptionally long (3-4mins) time to log into NT domain at the office from home
** Old WinME machine (SecuRemote 4186) took about 10 secs
Once logged in, everything "inside" the domain works great - EXCEPT Outlook (5 mins to open)
** Old WinME machine took about 15 secs to open and use

Hosts & Lmhosts file have internal IP of Exchange (5.5sp4) server listed
DNS settings options are presented differently than ME (have tried varios combos)

Any ideas?

Thanks!

- Jeff


Jeff Tice
Director of Technology
Hickory Public Schools
(828) 312-0717 - voice


=============================================

This email has been content filtered and
subject to spam filtering. If you consider
this email is unsolicited please forward
the email to [EMAIL PROTECTED] and
request that the sender's domain be
blocked from sending any further emails.

=============================================

Reply via email to