cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
EStarshinov
Engaged Sweeper II
Lansweeper version - 7.1.100.16
Firewall on wms00925.blabla.ru - Off.

After scannig Domain (BLABLA) and Type (Windows) not determined.
In Asset page Name as wms00925.blabla.ru and Type as Unknown.


Lansweeper Connection Tester 7.1.0.1

Scanning Lansweeper Service (on this machine)..
Status: Running
Version: 7.1.100.16

Pinging wms00925.blabla.ru
Ping ok.

Scanning TCP ports..
135 open (EPMAP)
139 open (NetBIOS Session Service)
445 open (SMB)


Checking DNS..
wms00925.blabla.ru resolved to: 172.20.192.60
If this is not correct, please check for DNS problems.

Checking reverse DNS..
172.20.192.60:
wms00925.blabla.ru

Scanning netbios (UDP)..
Could not scan netbios


Scanning netbios (445)..
Could not scan netbios

Scanning Active Directory..

Scanning WMI..
Computername: WMS00925
If this is not correct, please check for DNS problems

Operating system: Майкрософт Windows 10 Pro
\root\cimv2 Remote WMI access test OK

Operating system: Windows 10 Pro
\root\default Remote WMI access test OK

Checking C$ Access
Deployment Folder: OK
Access Rights: OK

Checking Task Scheduler
Не найден сетевой путь. (Исключение из HRESULT: 0x80070035)

Done.

5 REPLIES 5
SHib11
Engaged Sweeper II
Has there been an update to this?
I am experiencing the very same issue on WIN 10 workstations.
Esben_D
Lansweeper Employee
Lansweeper Employee
Not being able to scan the NetBIOS name shouldn't cause issues with scanning.
EStarshinov
Engaged Sweeper II
Esben.D wrote:
Not being able to scan the NetBIOS name shouldn't cause issues with scanning.


However, this seems to be the case.
How to solve the problem "Could not scan netbios" оn workstation?
EStarshinov
Engaged Sweeper II
But this is a special case. Most PCs are OK:

Lansweeper Connection Tester 7.1.0.1

Scanning Lansweeper Service (on this machine)..
Status: Running
Version: 7.1.100.16

Pinging wms00950.blabla.ru
Ping ok.

Scanning TCP ports..
135 open (EPMAP)
139 open (NetBIOS Session Service)
445 open (SMB)

Checking DNS..
wms00950.blabla.ru resolved to: 172.20.192.189
If this is not correct, please check for DNS problems.

Checking reverse DNS..
172.20.192.189:
WMS00950.blabla.ru

Scanning netbios (UDP)..
Computername: WMS00950
Domain: BLABLA


Scanning netbios (445)..
Could not scan netbios

Scanning Active Directory..
operatingSystem: Windows 10 Pro
operatingSystemVersion: 10.0 (17134)

Scanning WMI..
Computername: WMS00950
If this is not correct, please check for DNS problems

Operating system: Майкрософт Windows 10 Pro
\root\cimv2 Remote WMI access test OK

Operating system: Windows 10 Pro
\root\default Remote WMI access test OK

Checking C$ Access
Deployment Folder: OK
Access Rights: OK

Checking Task Scheduler
Не найден сетевой путь. (Исключение из HRESULT: 0x80070035)

Done.
Esben_D
Lansweeper Employee
Lansweeper Employee
Doesn't look like there is anything wrong in the device tester. I'd suggest contacting support and sending them Lansweeper's errorlog. They can also provide you with debug options to enable so they can more easily see what is happening in the background.