Registered to MCTP, but in the field this is the clustered JBoss HA-JNDI naming port sitting one above 1099.
IANA registers 1100 as mctp. What actually shows up on scans is JBoss Application Server's clustered naming service: the HA-JNDI configuration guide states that the Port attribute "to which the HA-JNDI server will bind waiting for JNP clients" defaults to 1100, with the RMI stub port defaulting to 1101. So finding 1100 open usually means a clustered legacy JBoss/EAP node, and 1098, 1099 and 1101 are typically open alongside it. HA-JNDI lets clients read and write the JNDI tree, which is why it has a long CVE history.
Do not expose
A reachable JNDI naming service lets attackers manipulate bindings and pull in remote objects; keep the whole 1098-1101 cluster range on a private network.
$ nmap -Pn -p 1098-1101 -sV TARGETSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.