
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2010 06:55 PM
I just upgraded to version 4.0.0.27 Premium. Everything seems fine, and the system is actively scanning all the computers.
However, when I try to manually scan a computer, it says it fails. This is the command I'm running:
lstrigger.exe servername computername domain
And when I run that (even from the server itself, it returns:
C:\Lansweeper>lstrigger.exe server computer domain
Lansweeper trigger client
-------------------------
Connecting...
Failed
However, when I try to manually scan a computer, it says it fails. This is the command I'm running:
lstrigger.exe servername computername domain
And when I run that (even from the server itself, it returns:
C:\Lansweeper>lstrigger.exe server computer domain
Lansweeper trigger client
-------------------------
Connecting...
Failed
Labels:
- Labels:
-
Archive
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-18-2010 04:29 PM
That did it!! Thanks!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2010 10:29 PM
Could you please try the following:
Stop the service
Delete errorlog.txt file
Restart the service
If the problem persists upload the new errorlog.txt file.
Stop the service
Delete errorlog.txt file
Restart the service
If the problem persists upload the new errorlog.txt file.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2010 06:11 PM
what service is not running? Everything on the lansweeper server is running fine, and it's doing the active scans fine.
The firewall on the server is not turned on, and I'm running it against a PC that the firewall is off also.
The firewall on the server is not turned on, and I'm running it against a PC that the firewall is off also.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2010 11:51 AM
This could be:
1) your service is not running
2) The service is running on a non-default port
3) Firewall is blocking access
1) your service is not running
2) The service is running on a non-default port
3) Firewall is blocking access
