ESX 4.0 Build 208167 is recognized as linux asset

[jsassm]

Got an VMware ESX 4.0 (Build 208167) which is recognized by lansweeper 5.0.0.10 as linux server, but not as vmware-server. All my other VMWares (ESXi 5.1.0) are identified correct!

Tested with DeviceTester:

Lansweeper DeviceTester 5.0.0.10
Scanning Lansweeper Service (on this machine)..
	Status: Service not found
	Version: Executable not found
Pinging 192.168.253.25
	Ping ok.
Scanning TCP ports..
	Open ports:
		22 (SSH)
		80 (HTTP)
		443 (HTTPS)
	Closed ports:
		21 (FTP)
		23 (Telnet)
		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..
	Url: http://192.168.253.25
	Certificate issuer: O=VMware Installer
	Response Uri: https://192.168.253.25/
	Content-Length: 5091
	Content-Type: text/html
	Date: Mon, 30 Dec 2013 07:37:52 GMT
	Title: " + ID_EESX_Welcome + "
Scanning HTTPS..
	Url: https://192.168.253.25
	Certificate issuer: O=VMware Installer
	Response Uri: https://192.168.253.25/
	Content-Length: 5091
	Content-Type: text/html
	Date: Mon, 30 Dec 2013 07:37:52 GMT
	Title: " + ID_EESX_Welcome + "
Scanning VMware webpages..
Error: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Done.

[jsassm · Accepted solution]

Thanks for the hint!

I cant access port 80, its a firewall problem between lansweeper and the ESX-Server.
(Run the device tester before on a different machine, not from the lansweeper-server...)

Solved for me,
thank you

[Hemoco]

are you able to access urls /mob and /sdk on your vmware server?

[jsassm]

Sorry 5.0.0.10 was the version shown by the device-Tester, my LanSweeper Version is the latest stable: 5.0.0.81

Or did you mean, i should install the release candidate Version 5.1?

grettings,
JS

[Hemoco]

Can you upgrade to the latest version please.