IP range Scanning problem with network printers

[SistemaCdP]

Hi all,

we have a problem with the ip scan of some network printers: the scan gets stuck on all our Konica Minolta printers. This is the queue:

IP scans in queue 32793
IP scans running 10 
SCAN_192.168.5.250
SCAN_192.168.10.192
SCAN_192.168.10.217
SCAN_192.168.20.55
SCAN_192.168.20.68
SCAN_192.168.20.78
SCAN_192.168.20.105
SCAN_192.168.21.223
SCAN_192.168.21.224
SCAN_192.168.21.227

The queue stays this way for hours, and trying with the devicetester, the scan seems to hang on ftp scanning.

Is there a way to setup a timeout for each scan or to exclude selected protocols (ftp in this case)?

Thanks in advance

[Hemoco]

Please contact us by e-mail for this problem.

[rainit]

I have the exact same problem with about 5 devices on our network. 3 are Polycom Video conference endpoints. All 3 Polycom endpoints hang on HTTP. They all happen to use some flash. We have other Polycom endpoints running different firmware that work fine (and don't use flash). The other 2 devices are odd balls. One is a Zebra label printer that hands on FTP scan, but we have a bunch that scan fine, not sure whats up with this one. I've reset it and checked the config on it numerous times. The last device is a Tandberg endpoint that hangs on HTTP scan.

We are running the latest lansweeper install (4.0.0.42). If you want me to test something out (or email support) just let me know.

[Hemoco]

lansweeper@hemoco.com

[SistemaCdP]

What's the email address?

[Hemoco]

Can you please contact us by e-mail for this problem.

[SistemaCdP]

We upgraded successfully to the latest version, but the issue is not solved, the queue still hangs on the same printers.

The errorlog does not say anything about it; if it can help, the snmp oid (the only thing that lansweeper is extracting before hanging) is 1.3.6.1.4.1.18334.1.1.1.2.1.6.1.2

Any idea?

[Hemoco]

Can you upgrade to the latest version (released today)
This fixes an issue with ftp scanning.