DisplayNet Logo
Skip to main content

DisplayNet Server

If there is a problem with the DisplayNet Server, first ensure that power is connected and that the server is powered ON. If the server appears to have locked up, immediately take note of the exact time when the lockup occurred. If necessary, reboot the server using the restart button on the front panel. After rebooting, review the Logs for errors that occurred around the time of the problem. If you have logging set to None, now is a good time to change it to Verbose Mode to get the most information available should the problem reoccur.

This log can provide valuable troubleshooting information to help determine the cause of the problem. Perform a logging search for the time of the lockup and look for any errors or warnings that may have occurred. You can export to a file and send it to DVIGear technical support for further assistance.

Password Security and Recovery

By default, the server is set up with a user account named "DisplayNet" that is password protected using the password "displaynet" (without quotes). In the event that any user account password is forgotten, a user with Admin access can reset the password for the "DisplayNet" user account or any other account.

If you're still unable to access your server, please contact DVIGear technical support for further assistance.

If a third-party control device cannot connect to the server, the control device may be using incorrect network settings to target the server. If so, please update the settings in the control device and any third party interface devices (as needed) and attempt to reconnect to the server. If the DisplayNet Manager software cannot connect to the API Engine, verify that the settings in the software are correct and attempt to reconnect to the engine. If the control device and/or DisplayNet Manager software cannot detect the DisplayNet devices on the network, then the server’s network settings may be incorrectly configured. Additionally, check the Ethernet cables for any problems such as damage, broken tabs, or loose connections.

If none of these solutions resolve the issue, there may be an problem with DisplayNet Server, if this is the case, contact DVIGear technical support.

Software Startup​

While DisplayNet Server software is starting up, the software will attempt to connect to the DisplayNet API running on the DisplayNet server. This is done using the IP address (or the host name) of the server and the appropriate port number (7000 by default). If the software cannot connect to the API Engine at startup, then the API Connection Status Bar will display "Disconnected."