Allowing Remote Connections to the LoggerNet Server

LoggerNet is a 32-bit client/server application, and therefore, the server can run on one computer while a client application can be run on a separate computer attached to the same network. Campbell Scientific offers client applications for LoggerNet that take advantage of this remote access capability. If Allow Remote Connections is enabled, you can run LoggerNet on one computer, and use a remote client application to display data remotely on a different computer or save a copy of the data on the remote computer. If remote connections are denied, data access from a remote computer is not possible.

Remote Connections is enabled from the LoggerNet Toolbar’s Tools > Options menu item. Select the Allow Remote Connections check box to allow remote connections. Conversely, when the check box is not selected, Remote Connections will be denied. After the change is made, LoggerNet must be restarted for the change to take affect.

Though this may be a desirable feature, enabling Allow Remote Connections also makes your LoggerNet network configuration vulnerable to changes by other parties on the network.

Therefore, if using standard LoggerNet (not LoggerNet Admin), we strongly recommend that you select Remote Connection Security Enabled and input (and confirm) a password. (The username cannot be changed.) The username and password will then be required before other parties on the network can connect to the LoggerNet server.

If using LoggerNet Admin, we strongly recommend that the Security Manager be used to set up account access with password protection to limit the ability to make changes to the datalogger network.