PS when I launch Salive as an application (under the same user I
provided in the com check setup) The check works fine. 

Jason Passow
Mississippi Welders Supply
[EMAIL PROTECTED]
ph: (507) 494-5178
fax: (507) 454-8104

"If you do everything right, nobody will realize you've done anything at all."



Jason Passow wrote:
> I am using the full UNC path.   I do however have the drive mapped.  I
> have also disconnect that drive.  When I do a net use on the server
> machine there are no connections showing.  I have verified that there
> are just no connections that I can see (using the tools I am aware of). 
>
> Jason Passow
> Mississippi Welders Supply
> [EMAIL PROTECTED]
> ph: (507) 494-5178
> fax: (507) 454-8104
>
> "If you do everything right, nobody will realize you've done anything at all."
>
>
>
> Ferrell, Jim wrote:
>   
>> Have you mapped the drive that you are trying to check?  I've been
>> burned by that before. 
>>
>> Jim Ferrell
>> EDS - Allison Transmission
>> 4700 W 10th St
>> Mail Code 462-470-H04
>> Indianapolis, IN  46222
>>
>> * phone: +01-317-242-0034 (8-252)
>> * mailto:[EMAIL PROTECTED]
>> Cell phone: 317-716-4541
>>
>>
>> -----Original Message-----
>> From: Jason Passow [mailto:[EMAIL PROTECTED] 
>> Sent: Monday, March 20, 2006 9:30 AM
>> To: Servers Alive Discussion List
>> Subject: [SA-list] multiple connections to shared resource
>>
>> I am getting a "multiple connections to shared resource not allowed".  I
>> am using the file count check.  I am using the administrator
>> authentication.   (This check has been working for many months).  It
>> uses the same credentials I am logging on to my server with and I can
>> access that directory through windows.  In otherwards I know this is a
>> windows error but I cannot duplicate it within windows itself.  I can
>> reboot the server tonight but I would like to troubleshoot this first. 
>>
>>
>>     
> To unsubscribe send a message with UNSUBSCRIBE as subject to 
> [email protected]
>
>
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]

Reply via email to