NMAP - OS Fingerprinting Ports Used in LANDesk 9 SP2

May 23, 2011, 1:53 pm

≫ Next: Agent deployment: Policy.client.invoker.exe crashes when installing the agent.

≪ Previous: Error when going to video properties

$

0

0

For community benefit, here are the ports that NMAP appears to use for OS Fingerprinting when called by LANDesk UDD.  I obtained these ports from the XML output file generated by NMAP during UDD/Fingerprinting, and cross referenced ports on the IANA database and supplemented "unknowns" from the list maintained by PC-LIBRARY.COM

 

Also, here's the exact parameters that LANDesk calls NMAP with:

NMAP.EXE -v -PN --min-hostgroup 128 --max-hostgroup 512 -T4 -sS -F -O -iL <LANDesk generated list of IP addresses to scan> -oX <XML output>

 

-v increased verbosity
-PN Treat all hosts as online (scan ports even if no ICMP response)
-T4 Timing template 4
-sS SYN scan technique
-F Fast mode (fewer ports - limit to the 100 most common ports listed below)
-O Enable OS detection

 

 

7	ECHO
9	DISCARD
13	DAYTIME
21	FTP
22	SSH
23	TELNET
25	SMTP
26	RSFTP
37	TIME
53	DNS
79	FINGER
80	HTTP
81	HOSTS2
88	KERBEROS
106	3COM-TSMUX
110	POP3
111	SUNRPC
113	AUTH
119	NNTP
135	EPMAP
139	NETBIOS-SSN
143	IMAP
144	UMA
179	BGP
199	SMUX
389	LDAP
427	SRVLOC
443	HTTPS
444	SNPP
445	MICROSOFT-DS
465	MACON-TCP
513	LOGIN
514	SYSLOG
515	TALK
543	KLOGIN
544	KSHELL
548	AFPOVERTCP
554	RTSP
587	SUBMISSION
631	IPP
646	LDP
873	RSYNC
990	FTPS
993	IMAPS
995	POP3S
1025	BLACKJACK
1026	CAP
1027	DEPRECATED
1028	DEPRECATED
1029	SOLID-MUX
1110	WEBADMSTART
1433	MS-SQL-S
1720	H3223HOSTCALL
1723	PPTP
1755	MS-SREAMING
1900	SSDP
2000	CISCO-SCCP
2001	DC
2049	SHILP
2121	SCIENTIA-SSDB
2717	PN-REQUESTER
3000	HBCI
3128	NDL-AAS
3306	MYSQL
3389	MS-WBT-SERVER
3986	MAPPER-WS_ETHD
4899	RADMIN-PORT
5000	COMMPLEX-MAIN
5009	WINFS
5051	ITA-AGENT
5060	SIP
5101	TALARIAN-TCP
5190	AOL
5357	WSDAPI
5432	POSTGRESQL
5631	PCANYWHEREDATA
5666	UNASSIGNED
5800	UNASSIGNED
5900	RFB
6000	X11
6001	X11
6646	UNASSIGNED
7070	ARCP
8000	IRDMI
8008	HTTP-ALT
8009	NETWARE-HTTP
8080	HTTP-ALT
8081	SUNPROXYADMIN
8443	PCSYNC-HTTPS
8888	DDI-TCP-1
9100	HP-PDL-DATASTR
9999	DISTINCT
10000	NDMP
32768	FILENET-TMS
49152	UTORRENT
49153	ANTLR(LANGUAGE RECOGNITION)
49154	PRIVATE/DYNAMIC
49155	PRIVATE/DYNAMIC
49156	VUZE/AZUREUS(TORRENT)
49157	PRIVATE/DYNAMIC

---

Agent deployment: Policy.client.invoker.exe crashes when installing the agent.

September 17, 2008, 8:26 am

≫ Next: alert.exe:Unexpected HTTP response code (403) from server http://127.0.0.1:9592

≪ Previous: NMAP - OS Fingerprinting Ports Used in LANDesk 9 SP2

$

0

0

I have upgraded from 8.8 to 8.8 SP2 today. Rather than doing an update to the agents I wanted to take the opportunity to create a new agent (reason below). However, on most machines, during the agent install Windows pops up an error stating that Policy.client.invoker.exe has crashed. I have attached a screenshot of the event log. Does anyone know why this has happened?

 

REASON FOR NEW AGENT.

 

Looking at the usage stats in SLM today i noticed that they were wildly inaccurate. This was because i sent an email to 20 users of a package (automatically discovered by LD) asking if i could remove it as SLM shows its never been run. They all wrote back that can't be right as they use it every day. All machines HAD done a full scan that morning but the usage stats are not being updated. Pushing out a whole new agent seems to resolve the issue but for how long i do not know.

 

Thanks for any help on the above. I will log the SLM issue seperately.

alert.exe:Unexpected HTTP response code (403) from server http://127.0.0.1:9592

March 25, 2013, 12:13 pm

≫ Next: Agent on Windows 8

≪ Previous: Agent deployment: Policy.client.invoker.exe crashes when installing the agent.

$

0

0

Error no log "c:\Program Files (x86)\LANDesk\Shared Files\alert.log"

Agent on Windows 8

October 31, 2012, 3:25 pm

≫ Next: Query for LANDesk version

≪ Previous: alert.exe:Unexpected HTTP response code (403) from server http://127.0.0.1:9592

$

0

0

I have several W8 Enterprise installs done for testing purposes. These are not beta versions. When I install the LD agent (9.1 sp3), either via push or local, it appears to complete however the machine does not show up in the console. If I try to run an inventory scan from the local machine, I receive missing .dll errors. I don't see any other questions on W8 in the forum. Ideas?

 

Thanks,

Query for LANDesk version

January 29, 2009, 7:33 am

≫ Next: ClientDBUtil.exe applicaton error while installing agent

≪ Previous: Agent on Windows 8

$

0

0

I am doing an agent install for 8.80 SP2A.  So I created a query based on who needed the patch, no problem.

 

Then I summed up those who have with those who needed and I didn't come up with all my devices.

 

Now I'm wondering if all the users didn't get SP2 and are on SP1

 

Can I create a query to find out what version of the agent is installed?

 

Thank you,

 

S.....

ClientDBUtil.exe applicaton error while installing agent

July 14, 2009, 9:15 pm

≫ Next: Windows Embedded Standard Agent Configuration

≪ Previous: Query for LANDesk version

$

0

0

ClientDBUtil.exe applicaton error

The application failed to initialize properly (0xc0150002). Click on OK to terminate the application.

 

 

How can we solve it?

Windows Embedded Standard Agent Configuration

March 27, 2013, 8:15 pm

≫ Next: CBA 8, unable to contact the remote agent

≪ Previous: ClientDBUtil.exe applicaton error while installing agent

$

0

0

LDMS 9.5

I have the Tenant option in my LDMS licensing also.

 

I noticed today that the Tenant configuration is not part of the Windows Embedded Standard agent configuration. Anyone else notice this? Possible oversight?

CBA 8, unable to contact the remote agent

December 27, 2007, 9:49 pm

≫ Next: Unable to deploy the LANDesk windows to client Machines

≪ Previous: Windows Embedded Standard Agent Configuration

$

0

0

 

I have a machine that has agent installed fine, is displaying in the all devices. However i have noticed that the remote agent control status has not been loaded. When i run a scan from the machine itself it seems to work and data has been sent to the core server. When i run a scan from the LDMS server console it fails- cba8, unable to contact the remote agent

 

 

when i do a repair job it says straight away- Cannot Find Agent

 

 

The agent has been removed and re-installed. Same agent version as other machines.

 

 

i have re ran the cba8inst.msi file no issues.

 

 

Cant do any repair jobs or scans from the LDMS?!?!?

 

 

Any help would be appreciated. **(FYI-im away next week so no reponse until the following week)**

 

 

---

Unable to deploy the LANDesk windows to client Machines

March 27, 2013, 5:48 am

≫ Next: Accidently installed packaged client on Core... Can I uninstall?

≪ Previous: CBA 8, unable to contact the remote agent

$

0

0

HI Team,

 

I unable to install the LANDesk windows agents to client machines thru LANDesk, getting an error failed to build the agent installation Package, Can someone pls help me to resolve this issue.

 

Regards

Srinath YN

Accidently installed packaged client on Core... Can I uninstall?

September 20, 2009, 10:27 pm

≫ Next: LD 9.5 - Strange language items in ldclient folder, do you have this?

≪ Previous: Unable to deploy the LANDesk windows to client Machines

$

0

0

Just as the subject states... Accidently hit enter with the package selected, and before I knew the installer was half way done.  I killed the process, and did not let it complete.

 

Can I run uninstallwinclient on the core without causing damage?

 

Ooops

 

Chris

LD 9.5 - Strange language items in ldclient folder, do you have this?

March 28, 2013, 8:55 am

≫ Next: Miniscan.exe Application Error

≪ Previous: Accidently installed packaged client on Core... Can I uninstall?

$

0

0

Can some of you that are on LD 9.5 please check one of your clients and in the the ldclient folder, do you have strange language folders as shown below?

 

Please let me know if you do and if you have installed the patch below or not

 

I have a 9.5 Dev core up and running, I have installed the latest (LD95-CP_BASE-2013-0228) patch installed.

 

Thanks

 

 

 

Miniscan.exe Application Error

April 17, 2008, 6:45 am

≫ Next: Advance agent shared folder permission

≪ Previous: LD 9.5 - Strange language items in ldclient folder, do you have this?

$

0

0

 

After removing the 8.7 client and installing the 8.8 client I an getting Miniscan.exe Application Error.  The event log shows:

 

 

Faulting application MINISCAN.EXE, version 8.80.0.249, faulting module MINISCAN.EXE, version 8.80.0.249, fault address 0x00001702.

 

 

All Suggestions welcome!

 

 

Advance agent shared folder permission

October 10, 2012, 12:46 am

≫ Next: Advance Agent MSI Package defective

≪ Previous: Miniscan.exe Application Error

$

0

0

Hi,

 

I am deploying agent using the advance agent method. But during the deployment, I get this error from the AdvanceAgent.log:

 

Download failed to connect server - hs=0x80004005, try bypass proxy

Attempting to download file: \\xxxxxxxx

Couldn't download file \\xxxxxx, returned 80004005

 

I believe that the error 80004005 is because of shared folder permission. Do anyone have the list of user need to be entered in the share/ntfs permission?

 

Thanks.

Advance Agent MSI Package defective

June 26, 2008, 2:48 am

≫ Next: LANDesk agent 9.5 deployment methods

≪ Previous: Advance agent shared folder permission

$

0

0

 

When i try to deploy the Advance Agent Package, the Deployment is shown as "successful" but in the results columnt is "The Setup has returned an error" (or similar). Directly starting the MSI-File returns: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2725". It also doesn't help to create a new configuration and create a new Advance Agent Package. Always the same error. I think it came up after installing the mini-rollup 05-08

 

 

LANDesk agent 9.5 deployment methods

February 27, 2013, 2:28 pm

≫ Next: Is there a switch for BrokerConfig.exe to specify a timeout?

≪ Previous: Advance Agent MSI Package defective

$

0

0

Hi all,

 

i am having trouble finding the documentation for the recommended methods of the agent upgrade in version 9.5. Can someone point me in the right direction please?

 

Thank you.

---

Is there a switch for BrokerConfig.exe to specify a timeout?

December 7, 2009, 1:34 pm

≫ Next: Mirror Drivers disable Windows Aero on Windows 7 64 bit

≪ Previous: LANDesk agent 9.5 deployment methods

$

0

0

I have BrokerConfig running at time of installation of my agents, and have noticed for some reason it takes ~5 minutes for that portion of the installation to continue.  Now, it's not a huge deal, but a waste of time in my mind.  I mean if it's going to work it should work within the first minute.  Is there a way to make it timeout after 120 seconds?

 

Thanks,

Chris

Mirror Drivers disable Windows Aero on Windows 7 64 bit

January 25, 2010, 10:03 am

≫ Next: LDMS 9 - Agent Failing when Pushed

≪ Previous: Is there a switch for BrokerConfig.exe to specify a timeout?

$

0

0

I discovered that if you install an agent using the Remote Control Mirror drivers on a Windows 7 64 bit pc it disabled the Windows Aero feature.  This was not the case on a 32 bit Windows 7 machine.  The machines I used were a Dell 755 (64bit) and a Dell D820 laptop (32bit).  Just wanted to pass this on should anyone else see it.  Once I changed the client and rebooted Aero started working again.  This was a version 9 client.

LDMS 9 - Agent Failing when Pushed

February 24, 2010, 8:00 am

≫ Next: How do we remove an agent?

≪ Previous: Mirror Drivers disable Windows Aero on Windows 7 64 bit

$

0

0

I have a question regarding my LDMS9 Test Environment. I've successfully discovered a device using Unmanaged Device Discovery within my small 2 PC / 1 Core test environment. After I discovered PC1 I wanted to push the Agent I created out to it. When I do so the Scheduled Task fails. It states Unable to contact the specified machine. The machine may be off or unreachable. Well, the machine is on and is pingable from the core. Anyone have any suggestions to why this may be failing?

 

Other notes: PC1 is a Windows 7 Machine and these computers are in a a WORKGROUP.

How do we remove an agent?

January 15, 2008, 10:44 am

≫ Next: Drill down into a PC for Agent information

≪ Previous: LDMS 9 - Agent Failing when Pushed

$

0

0

I've been thru the manual, and can only find 1 or 2 instances of "remove agent", and hundreds of instances of either word by itself.

 

We have one user who is being harrassed by LD.  Every day LD wants to install some update/patch...even after we apply everything there is to apply manually, using remote control.

 

We don't know specifically what it's trying to install.  We thought for the moment that we'd just remove the agent.  But we don't know how.  I had seen LANDesk listed under Add/Remove SW on my PC, but when I connected to his, it wasn't there.  We're assuming that my LANDesk listing was for the console, rather than for the agent.

 

Thanks in advance for the assistance,

 

Tom

Drill down into a PC for Agent information

April 2, 2013, 6:12 am

≫ Next: What is rainstall.exe?

≪ Previous: How do we remove an agent?

$

0

0

I have serveral agents that I have configured, my question is how do I drill down into a PC on the Landesk console in order to find out what is the current agent on that PC.