Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper
First of all congratulations with the version 5 update and the many new features. Impressive !!!

I'm trying to shorten my list of scanning errors and this one puzzles me big time.

I get a scanning error for a remote access device of an IBM server :
SSH Error Could not connect to SSH with credentials root1-13 (root), Global (root)

The device tester shows this :

Scanning Lansweeper Service (on this machine)..
Status: Running
Ping ok.
Scanning TCP ports..
Open ports:
22 (SSH)
23 (Telnet)
80 (HTTP)
443 (HTTPS)
Closed ports:
21 (FTP)
25 (SMTP)
135 (EPMAP)
139 (NetBIOS Session Service)
445 (SMB)
9100 (Jetdirect)
Scanning netbios (UDP)..
Could not scan netbios
Scanning SIP..
Error: No reply
Scanning HTTP..
Response Uri:
Connection: close
Accept-Ranges: bytes
Content-Length: 3616
Content-Type: text/html
Date: Tue, 12 Feb 2013 15:27:32 GMT
ETag: "-204036876"
Last-Modified: Thu, 29 Nov 2012 14:43:04 GMT
Server: lighttpd/1.4.13
Title: IMM
Scanning HTTPS..
Error: The operation has timed out
Scanning SNMP..
Snmp version: Ver2
Hostname: SNMP Service
Description: Linux DEKESX11-IMM #2 PREEMPT Thu Nov 29 09:40:04 UTC 2012 mips
Uptime: 0d 2h 32m 51s 340ms
Contact: -
Location: -
MAC 4: 5C F3 FC DC CC E0
MAC 5: 5C F3 FC DC CC E1
MAC 6: 5C F3 FC DC CC E2
IpForwarding: 0
Interfaces: 6

Similar RAC of servers with exactly the same setup are scanned perfectly with SNMP, just the one above fails with the SSH error.

Only difference is the failing RAC is being scanned over our WAN. There is no filter/firewall in place on the WAN.

We also use PRTG which can access the RAC with SNMP perfectly.

Any insights would be greatly appreciated.


Lansweeper Alumni
Can you please contact us at and provide screenshots of the problem.