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!

Outlook 2000 'sluggish' with XP SP2 4

Status
Not open for further replies.

Arran

MIS
Apr 11, 2002
57
GB
Can't really describe this as a problem as such - but more of a hinderance.

Some of our PCs seem to be having trouble with Outlook 2000 in that sometimes when you send an email (internal or external) the email goes into your Outbox and appears to stay there (the Outbox folder is bold). In actual fact the email HAS gone but the Outbox appears to hold the email. If you click the Outbox folder - there is nothing in the folder and the folder returns to its normal colour (ie - not bold). This only seems to happen on PCs running XP SP2.

The reverse sometimes happens with incoming email. You can have new incoming email sitting in your Inbox but you are not warned about it or the Inbox folder does not turn bold until you click the Inbox - then the new email is highlighted.

Does this ring any bells as something that has happened at other sites? We run Exchange 2000 and Dell PCs.

Like I said - it does appear to be just a SP2 machines.

Any help/guideance would be great

Love you all :)

Arran
 
Hi Arran,
We are experiencing the same problem with some of our users also - All running Outlook 2000 on Dell PC's with XP SP2 installed. I was wondering if you had found a solution to the problem and could pass on your knowledge to me.....
Thanks,
Angela.
 
Hi Angela,

If you search the Microsoft Knowledgebase - and if you look hard enough (and it is well hidden!) there is a article that describes this problem. It seems to be a known problem with Outlook and XP SP2.

Its something to do with the SP2 firewall not letting a protocol through that stops the update of the folder items (like inbox etc). The items eventually update because Outlook senses that the protocol is not working and uses a different protocol.

I know that sounds vague - but i'm trying to recite the knowledgebase entry from memory.

You can let the protocol through the firewall and it should solve the problem - but I could never get this to work through GPs.

I'm living with it at the time being and hoping Microsoft release a patch in the future.

Not much help am I!!

Thanks
A
 
Arran, [smile2]
I have just read through and carried out the first procedure on the knowledge base article you linked me to - A Big IRISH THANK YOU for all your help as the problem is now resolved.
Keep up the excellent work........ I'M WELL IMPRESSED
 
Just out of interest - is an Irish Thankyou bigger than an English Thankyou...???

And how come the first part of that KB article works for you and not for us. Did you apply the rule using a Group Policy or manually on the PC?

Cheers
A
 
Hello again Arran,
In answer to your question regarding the Irish thank you - Yes, it is bigger than an English thank you - For a small country we have to think big. Even our leprechauns think they're giants....
Back to business - I applied the changes to the individual PC's as there are only 7 of them at the moment using Win XP with SP2 installed - We are currently in the process of upgrading our hardware and moving our users to Win XP so we intend implementing Group Policy, etc. at a later date -but who knows, by then there may be a patch released to fix this problem.
SLAN LEAT AGUS NOLLAIG HONA DHUIT FROM THE EMERALD ISLE (That means goodbye and a happy christmas - At least I hope it does - My Irish was never that good)
 
Brill - cheers Angela - and have a merry Xmas your self! Hope Santa brings everything you want... :)
 
Isn't it just typical!!! I searched for weeks on this damn topic and couldn't find an answer, and the minute I fix the problem I THEN find the answer!!!. Anyway, many thanx for the solution.

By the way for anyone with a 2003 domain environment here's the GP policy required:

Default Domain Policy > Administrative Templates > Network > Windows Firewall > Domain Profile . . .
In right hand pane, double click 'Windows Firewall:Define program exceptions', enable the policy and press 'SHOW', then 'ADD'. Enter the following text . . .

%programfiles%\Microsoft Office\<OfficeVersionNumber>\outlook.exe:exchangeserverip:enabled:Outlook

Obviously, you would replace 'exchangeserverip' with the actual IP address of your Exchange Server and to enter more than one Exchange Server IP simply place a comma (,) between the IP's or alternatively replace 'exchangeserverip' with 'localsubnet' to allow Outlook to communicate freely with any machine on your local subnet. OK to all and on client machines enter 'gpupdate' from RUN command to refresh policies immediately or allow client to refresh according to your current GP refresh policy.

Thanx again for info.

Cheers

Marko
 
Hi guys,

Had the same problem with our company. Dell PCs, XP SP2, Outlook 2000. With us, however, it wasn't so much messages staying in the outbox after they were sent...it was extreme lag when switching between folders, and even viewing one message to the next.

I ran through the steps of adding Outlook to the exceptions in the security center, and the issue appears to have cleared up! I guess I'll know soon enough.
 
I'm glad this thread has sorted some peoples problems out - but - it hasn't sorted mine!

Has anyone got this solution to work on a Windows2000 environment, running XP SP2 on Dell PCs with Outlook 2000/XP as the clients.

I can't seem to get the GP option regarding the firewall to sort our problem.

Its not a major problem at all - but it IS bugging me now :)

 
Forget that - I'm a bumbling idiot.

Least it is not bugging me anymore now I have got my arse in gear!!!
 
Arran,

I know how annoying it is when you post a question and then everyone else finds the resolution works apart from yourself! been there m8!.

In regards to you still having the problem - have you actually tried disabling the firewall on the client in an effort to make absolutely sure it is the firewall causing the problem?.

Also, as far as I am aware (and I may be stating the obvious to you here - or totally wrong - it's been that long since I dealt with W2K), a W2K domain controller wouldn't support any client GP configuration for Windows XP Client Firewall and I would therefore assume that you have applied GP settings on the client itself which still doesn't fix the problem?.

 
I have been searching for the answer to this problem for a few weeks now and I wanted to thank you all as well.

As for the GPO setting Arran, I have downloaded and used the gpmc sp1 tool from Microsoft and the solution is not without its problems. The gpmc tool with sp1 will allow you to make the appropriate settings you need. Much like marko2002 said earlier, but here Default Domain Policy > Computer Configuration> Administrative Templates > Network > Windows Firewall > Domain Profile . . .
In right hand pane, double click 'Windows Firewall:Define program exceptions', enable the policy and press 'SHOW', then 'ADD'. Enter the following text . . .

%programfiles%\Microsoft Office\<OfficeVersionNumber>\outlook.exe:exchangeserverip:enabled:Outlook

Obviously, you would replace 'exchangeserverip' with the actual IP address of your Exchange Server and to enter more than one Exchange Server IP simply place a comma (,) between the IP's or alternatively replace 'exchangeserverip' with 'localsubnet' to allow Outlook to communicate freely with any machine on your local subnet. OK to all and on client machines. Go to RUN then type CMD and enter Secedit/refreshpolicy machine_policy/enforce to refresh policies immediately or allow client to refresh according to your current GP refresh policy (marko2002).

If you decide to check this tool out for yourselves a few words of caution. This program will only install on an XP or server 2003 computer. Also if you use the gpmc tool with sp1 on a windows 2000 domain you will find you can no longer access the GPO's from a 2000 Server. It causes some truncating error that forces you to log off or click OK until it has gone through all of the policies. There is an earlier version of this tool, but I have yet to find it.
 
Marko2002. I tried the patch for 2000. It worked like a champ. Thanks a lot.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top