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

Briefly press and release the player blue button to display the player addresses.

The player web interface can be accessed from a web browser using http(s)://HMP_address/ with the address being any of the following: IPv4 address, IPv6 address, or hostname address.

IPv4 address

IPv4 addresses may be represented in any notation expressing a 32-bit integer value. They are most often written in the dot-decimal notation,

which consists of four octets of the address expressed individually in decimal numbers, ranging from 0 to 255, separated by a dot / full stop. Example:

Note Notes:
  • The player 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 -
  • When Network Discovery is enabled on Windows computers, HMP350 and HMP300 devices are listed in the Windows Explorer's Network view.

IPv6 address

IPv6 addresses are represented as eight groups of four hexadecimal digits with the groups being separated by colons, for example 2001:0db8:0000:0042:0000:8a2e:0370:7334, but methods to abbreviate this full notation exist - zeros can be omitted for instance.

  • Link-local IPv6 address to use on Windows Vista or later. The {XX:XXXX} notation must be replaced with the last six digits of the player serial number, without the curly brackets. Example: http://[fe80::21d:50ff:fe20:b2]/
  • Unique local address (ULA) - a site-local or global IPv6 address using the router-advertised network prefix. Example: http://[fe35:299:14bc:0:21d:50ff:fe20:b2]/

Hostname address

In computer networking, a hostname is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. The hostname of the HMP has the following format:


where {Serial_Number} represents the full serial number of the player. Example: http://spx-hmp-001d502000b2.local/

Note Notes:
  • The hostname of the player cannot be modified.
  • To resolve such a .local address, Bonjour™ service (multicast domain name service) has to be present on your computer - on Mac OS X, Bonjour is already installed as part of the operating system, while on Windows it can be installed via Elementi or iTunes.
  • If another hostname is required, it must be manually added within the local DNS server along with the corresponding IP.
  • To avoid a common behavior of some browsers of "guessing" the URL by adding "www." at the beginning and / or ".com" and the end of the URL, when the address is not reachable, you might add a trailing dot (period).

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 13:18.