This might also happen if a user is executing a command that creates some
sort of lock and the execution of the command is suspended by, for example,
an E-Mail pop-up message. The lock will remain until the command finishes
executing. This can stop other users trying for the same resource. Thus,
some users will have no problem, whereas, several other users will have
"Waiting for resources" message. Once the initial user allows the command
to finish executing, other users can then gain access to the resource.
Frank Radice
[EMAIL PROTECTED]
----------------------------------------------------------------------------
----------------
-----Original Message-----
From: K Kleinman Zajac [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 07, 2001 3:45 PM
To: [EMAIL PROTECTED]
Subject: RE: RB Win 65++ on W2k Server
>> I would guess you either have a power problem, or a bad network card
causing
your problems. <<
I am haveing a similar problem with the Waiting for resources message,
though not as bad. I am confident that this is not power problem, nor a
NIC issue.
