My FUDforum

Home »  » SocketServer and NS-Link » NS-Link versus SocketServer security
Re: NS-Link versus SocketServer security [message #1060 is a reply to message #1059] Mon, 22 October 2018 12:58 Go to previous message
Kurt is currently offline  Kurt
Messages: 264
Registered: July 2016
Location: Minnesota
Power User

Hi BobF,

I assume the driver you are referring to is one in the Devicemaster (DM) itself? Or is it something on the computer that is being used to connect to the DM? I was using the same computer to log into all of my Devicemasters when some showed NS-Link and others showed SocketServer. I like how on the DM's that showed SocketServer, it asked for the user and password. In your replies above, it almost seems as if I had the correct driver, it should show up as NS-Link and there would be no prompt for a password?

The driver referred to is for the DeviceMaster, see here:
http://downloads.comtrol.com/html/DM_PRO_RTS_SERIALHUB_drive rs.htm

If you configured a password it should ask for a password regardless of using a driver or when using Socket mode.

My concern is if someone had the IP address of my DM and they tried connecting, that they could then immediately see my config and port info if they had the "correct driver". I don't want to assume the ones that are prompting me for a username and password are secure if I am only being prompted because of a lack of a proper driver. The ones that are not prompting for a password are apparently using the proper driver since they show NS-Link.

Within the web page of the new firmware v11.x, you can go to "Network" -> "Security" create your password and select 'Enable Secure Config Mode'. Next, reboot.
This will enable https:// functionality and will require a password.

If using PortVision, you will be required to enter the username / password to get to the Properties GUI.

Telnet would require SSH on port 22. You will be asked the username and password

In the end I am hoping that there is a way to make the DM prompt for a user/password no matter the way you choose to connect to it. Using PuTTY via Telnet does prompt for a password on the ones I set up that way, but over a common web browser there is no password for those same DM's with the driver that allows it to show NS-Link.

You should be ok with the above suggestions.

If you want to do this via telnet, the command would be:

Command to set your password
password <your_password>

Command to set secureconf:
secureconf enable


Kurt Rees

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Older Versions
Next Topic: SocketServer and NS-Link Firmware Combined
Goto Forum:

Current Time: Fri Jan 22 05:39:26 CST 2021

Total time taken to generate the page: 0.01408 seconds