Software
Consulting
HomeDownloadForumOrderContactDealers onlySitemap
Current Version: LOGINventory 5.1.5
You are here: Home LOGINventory FAQ Prerequisites for Scanning
Deutsch English

Prerequisites for Scanning (4.x, 5.x)

Due to the limited networking capabilities of Windows 9x, XP Home and Vista Home, LOGINventory is unable to remotely scan PCs with these operating systems. Instead, by executing LOGINfo.EXE locally (for example via startup or logon script) it is possible to inventory these computers, too (see section 2.1 of the LOGINventory Trouble Shooting Guide for detailed explanation).

The following prerequisites may be checked to assure proper scans:

For scanning remote computers, valid logon credentials as a local administrator on the remote PC are required.

Typically, this is no problem in a domain environment when logged on with an account which is a member of the 'Domain Admins' group. Otherwise user name and password must be specified within LOGINquiry. For domain accounts the user name must be prefixed with the domain name (e.g.: MYDOMAIN\myadministrator).

In a workgroup environment user name and password are always required. The user account must have administrative privileges on the target, otherwise ERROR 5 or ERROR 1326 (access denied) occurs.

Microsoft integrated a new security mechanism into Windows XP and later that automatically maps every connection to the 'Guest' user on network access, even if the Guest account is deactivated. This feature can be turned off in the local security policy by setting Local Policies/Security Options/Network access: 'Sharing and Security model for local accounts' to classic.

'Client for Windows Networks' and 'File and Printer Sharing' must be enabled, the service 'Server' must be started.

Administrative shares (C$, D$ ...) are required for gathering disk space if no WMI is used.

It must be possible to connect to a Windows work station share using:

NET USE * \\PCname\IPC$ /USER:domain\adminaccount password

Or

NET USE * \\PCname\IPC$ /USER:localadminaccount password"

Regedit respectively Regedit32 remote registry access should work:

  • Start REGEDIT
  • Select 'File' / 'Connect Network Registry'
  • Enter the object name to select:

The result of NBSTAT [-a PCname] or NBSTAT [-A PC-IP-address] (i.e. 192.268.1.2) should list [PCname] within NetBIOS name table.

On Windows XP or later Remote WMI access can be checked by WMI, e.g.:

WMIC /NODE:remotepc-FQDN /USER:domain\adminaccount /PASSWORD:secret CPU

 

LOGINventory uses the following protocols and ports for scanning:

  • ICMP Echo Request (if Ping doesn't work - SNMP connect is tried only)
  • TCP Port 139 (NetBIOS Session Services)
  • UDP Port 137 and 138 (NetBIOS Name Server, NetBIOS Datagramm
  • TCP Port 445 (RPC)
  • UDP Port 161 (SNMP)

In most cases 'Ping' and 'TCP/139' are sufficient for Windows PCs.

When using SNMP, the device generally must also answer Ping; it is also possible but not recommended to configure LOGINquiry for retrieving SNMP data from devices not answering Ping.