The user complains Notes is slow to open a database (60 seconds) or if you are in a view then it is slow to move anywhere else if you have been inactive for several minutes.
However while Notes is hourglassed, on the same client machine you can then open VNC (or PCAnywhere) to the same Domino server and connect immediately, but notes is still trying and will take 60 seconds or more, by then it produces a "max time" message. Try the same again and it immediately works fine. (no issue with network capacity or machine resources).
If you get hourglasses then control break, and then try to open again then Notes works fine at least until you leave it idle for a while.
There are similar posts in this forum:
"Connection problem in 6.5.2 Client?"
"Domino 6 Server "sleepy"
"Possible nasty: Horrible ....."
There has never been a resolution to this issue.
From the same workstation I can connect to R5 Domino servers and NEVER have the problem. With R6 (6.5.1 currently)regardless of version I experience the problem. On the Domino newsgroup others also experience the same problem. Some say it is intermittent for all users, other say about 10% of users are affected. That is the same 10% have the intermittent issue and the 90% never complain of it, suggesting a workstation issue? That admin could not find any commonality with networks etc. for the affected users. The affected users became local replicators as a workaround.
On one Domino test server, P4, 1GByte ram etc with only two mail databases with only a few documents and no application databases, no agents running, little resources in use, but still has exactly the same problem.
I have replaced the switch and NICs with 3Com all round. I have played with MTU's etc re:http://www.aylmer.com.au/notesvt58cj39fa.htm
The workaround is to have the users running local replicas and replicating frequently.
Windows 2000 pro and XP pro are equally affected.
I have used netstat based sniffer tools but can not determine any network issue.
So far I only have a small sample size of R6 users to test, most users will stay on R5 until this issue is resolved as they cannot function with local replicas. I do not have a mix of R5 and R6 users. All organisations are one or the other.
Many individuals users are annoyed by this issue but fail to report it, or it works OK when the Admin arrives to test, or the Admin puts it in the too hard bin.
My assumptions so far:
1/ Only R6 users are affected and all versions.
2/ It is a network related problem, but perhaps not the network per se.
3/ It may be a Lotus issue but not yet recognised as one.
4/ It may be a Notes client problem or related to the way the client installs?
5/ The issue is often misdiagnosed and never rectified partly because it is intermittent and it works when you retry.
6/ Notes is the only product on the user's workstations that is affected, all other software products on the workstation work happily. The same applies for MTU issues, it only affects Notes and no other products that the user installs.
7/ Organisations affected by this issue may not realise it because retyring fixes it.
8/ In my experience (but not others apparently) I only have the problem when the R6 server and R6 client are on different subnets. I have never had the problem when they are both on the same subnet.
The worst thing is when you apply an update or send mail and it hourglasses, sometimes it does send the mail and others it does not so you have to repeat the process just in case it failed. Invariably the recipient ends up with two messages.
We need to nail this, any thoughts anyone?