Network access on HMP

From SpinetiX Support Wiki

(Redirected from Network access)
Jump to: navigation, search
It is not recommended to have the HMP connected directly to the Internet as it does not have a firewall and thus it is exposed to all sorts of threats. The player is not designed to be used in this manner - alternatives for remote access are detailed below.


The HMP provides different network interfaces which can be accessed via HTTP when the player is connected to the network and properly configured. In case of HMP350 and HMP300, the HTTPS protocol can be used as well.

The HMP also uses the WebDAV protocol for pushing content and raw TCP socket connection for accessing the Shared Variables interface.

Other protocols, like SSH, Telnet, FTP etc., are not supported.

HMP addresses

The player web interface can be accessed from a web browser using http://HMP_address/ where HMP_address can be any of the following: the hostname address, the IPv4 address, the IPv6 address.

Note Notes:
  • Briefly press and release the HMP blue button to trigger On Screen Display (OSD) which displays these addresses.
  • The HMP350 and HMP300 devices can also be accessed via the HTTPS protocol.

Hostname address

  • {Serial_Number} represents the serial number of the HMP, for example http://spx-hmp-001d502000b2.local/
  • The hostname address of the HMP cannot be changed.
  • Bonjour has to be installed on your computer to use this address. Note that installing Elementi / HMD will automatically install Bonjour as well. On Mac OS X, Bonjour™ is already installed as part of the operating system.
  • To avoid a common behavior of some browsers which try "guessing" the URL by adding "www." at the beginning and / or ".com" and the end of the URL when the address is not reachable, make sure to type http at the beginning or add a trailing dot (period) at the end of the URL (i.e. http://spx-hmp-{Serial_Number}.local./ )

IPv4 address
  • Four octets IPv4 address written as decimal numbers, ranging from 0 to 255, separated by a dot / full stop.
  • The HMP is configured by default to use DHCP, so its IPv4 address is allocated automatically by the DHCP server. If there is no DHCP server found or there is an IP conflict or the network link is not detected, then IPv4 address of the HMP is auto-configured in the range -
  • Example:

IPv6 address

  • Link-local IPv6 address to use on Windows Vista or later. Example: http://[fe80::21d:50ff:fe10:0014]/
Note Note:
The {XX:XXXX} notation above needs to be replaced with the the last six digits of the serial number of the HMP.

HMP internal web server

SpinetiX players feature an embedded web server offering access to different player applications, such as:

See the full article about embedded web server.

Remote access

Here are some methods to access an HMP behind a NAT router / firewall:

  1. Use Pull mode to update the content from an external server and to retrieve monitoring and accounting logs, or an RPC concentrator for extended functionality.
    • pro: secure, easy to set up, no extra costs
    • con: allows only indirect access, needs access to a web server
  2. Use a VPN connection to get access to the private network.
    • pro: very secure, allows direct access
    • con: more complex to manage, may require extra hardware (VPN server)
  3. Use port forwarding into the internal network - for instance external ports 5550 and 5551 can be forwarded to ports 80 and 81 of an internal IP address to allow accessing the embedded web server and publish server of a certain player. The ports on the player side cannot be changed. See also how to publish using different ports.
    • Pro: easy to reach from anywhere
    • con: security issues, the HMP can be exposed to Internet threats
  4. Use dynamic DNS - this is not natively supported by the HMP, but is typically implemented by router devices. You can find more details about Dynamic DNS on this Netgear page.
    • Pro: easy to reach from anywhere
    • con: security issues, the HMP can be exposed to Internet threats
This page was last modified on 7 February 2019, at 12:18.