
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2016 06:10 PM
When viewing asset details (computer) and trying to use the ping command, I get the following message:
I get the same error for:
When trying to use the Http/Https actions I get:
I get the same error for:
However the reset of the basic actions work fine: Commgt,EvenerView, Shutdown.
I checked and the $Lansweeper share exists and I have access and full permissions.
What I am missing, I am sure it is something simple.
Thanks.
Permission denied.
cmd.exe /K "ping.exe QCSPC27.xxxxxx
I get the same error for:
- PingPath
TraceRt
NBTstat
When trying to use the Http/Https actions I get:
File not found.
\\qcspc20\lansweeper$\shellexec.vbs "http://192.168.10.27"
I get the same error for:
- Open C$
Open Admin$
However the reset of the basic actions work fine: Commgt,EvenerView, Shutdown.
I checked and the $Lansweeper share exists and I have access and full permissions.
What I am missing, I am sure it is something simple.
Thanks.
Labels:
- Labels:
-
General Discussion
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2016 06:28 PM
As a side note, if I navigate to the Lansweeper$ share, I can run putty and DeviceTester.
I am thinking it has to be some kind of permissions issue??
I am thinking it has to be some kind of permissions issue??

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2016 05:48 PM
Thanks for the reply Karel.
Its funny you say that, I was using 6.0.0.45, but I upgraded last night to .48.
I just tried again and got the same results.
Its funny you say that, I was using 6.0.0.45, but I upgraded last night to .48.
I just tried again and got the same results.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2016 09:01 AM
Could it be you're using version 6.0.0.45? This introduced a bug which looked similar to this and was later fixed in version 6.0.0.48. You can find the latest download here.
