*Which ports does SDM2 Device Manager use?
Technical Article | TA-20200927-OV-11 Support Software | SDM2 Device Manager |  |  |
Applies to SDM2 version 2.5.1
SDM2 uses several ports on the local machine it runs on. This enables the tool to detect and drive devices in the network via several mechanisms. Each of these mechanisms use their own protocol and port(s).
Below you will find an overview of the mechanisms and the ports used. Note that you can enable and disable each individual driver and/or detector via the Options.
SPI driver
Typically uses TCP port 80 on the remote device, but you can configure the port used via Edit Device. The SPI protocol is an HTTP based protocol, and every subsequent command-response cycle addresses the given TCP port on the remote device. The (source) port used on the local host is automatically determined by Windows.
ONVIF driver
Typically used TCP port 80 on the remote device, since ONVIF uses HTTP/XML as communication means. You can change this port in the camera, and in that case you also need to change the used TCP port in the Edit Device dialog for your device in SDM2. The (source) port used on the local host is automatically determined by Windows.
MAPI driver
See SPI driver. It uses the same mechanism, but different protocol for its operation.
ISAPI driver
See SPI driver. It uses the same mechanism, but different protocol for its operation.
XSNet driver
Typically uses TCP port 23 on the remote device, but you can configure the port used via Edit Device. The XSNet driver will communicate with the switch via Telnet protocol. The (source) port on the local host is automatically determined by Windows.
DC driver
See SPI driver. It uses the same mechanism, but different protocol for its operation.
SNMP driver
Typically uses UDP port 161 on the remote device, with a source UDP port that is dynamically assigned by Windows. For traps, localhost UDP port 162 is used.
These ports are currently fixed and cannot be changed in SDM2.
MX driver
Uses UDP port 8655 on the remote device, as well as on the localhost. Via this UDP port the MX/IP protocol communicates with the remote devices.
Additionally, SDM2 runs a localhost TCP remote control service on TCP port 8656. Via this localhost remote link, SDM2 can spawn multiple internal processes to independently communicate via MX/IP. Connection attempts from remote hosts to this service are actively refused.
In case the MX device cannot be reached using unicast communications, the MX driver has a fallback mode, in which it tries to establish the connection using limited broadcasting.
UPnP detector
Uses UPnP SSDP services. Uses multicast address 239.255.255.250, uses UDP port 1900 on the remote device. The (source) UDP port on the localhost is dynamically assigned by Windows.
WS-Discovery detector
Uses multicast address 239.255.255.250, it uses TCP and UDP port 3702. The (source) port on the localhost is dynamically assigned by Windows.
ISAPI detector
Uses multicast address 239.255.255.250, uses UDP port 37020 on the remote device. The (source) UDP port on the localhost is also UDP port 37020.
MX detector
See MX driver. Uses limited as well as directed broadcasting to detect MX devices.
DcLegacy detector
Uses UDP broadcasting towards UDP port 6666. The (source) UDP port on the locahost for these transmitted broadcasts are dynamically assigned by Windows.
For the reception of responses from the remote devices, localhost UDP port 6667 is opened.
Additional to the drivers and detectors mechanisms, following SDM2 functions:
Manual Scan
This function allows for scanning a given IP range, using one of the following protocols:
PING - will attempt to PING each IP address in the given range
HTTP - will attempt TCP connect to remote port 80 for each IP address in the given range
Telnet - will attempt to TCP connect to remote port 23 for each IP address in the given range
FTP - will attempt to TCP connect to remote port 21 for each IP address in the given range
RTSP - will attempt to TCP connect to remote port 554 for each IP address in the given range
SPI - same as HTTP but also tries to log in using Admin/1234
In all cases the (source) TCP port on the localhost is dynamically assigned by Windows.