Setting up a player to connect to Cloud, you may run into troubles connecting. Below is a checklist for common connection problems:

  • The server has no IP address or a different one than expected
    If it has been dynamically assigned, is there a possibility it has changed recently?
    To determine the IP address of the server, bring up a command window (Windows + r > cmd) and type "ipconfig". The IP address is visible under the connection.
    If using DHCP and the IP address starts with "169" it has not been able to connect to the DHCP server and instead been assigned a private address.

  • Once you know the IP address of the server computer, proceed to ping it from the player to see if there is a network problem preventing you from reaching it.
    To ping, bring up a command window Windows + r > cmd) and type "ping <server IP address>".
    If you can reach it you should see something like "Reply from X.X.X.X: Time=0ms TTL=128".

  • The address has been specified but the name server cannot be reached.
    Check by pinging the address or by bringing up a command window and type "nslookup", then type the address.

  • If the server has a software firewall, you need to make an exception for the port used for the connection.
    The port(s) used is often configurable, for example, by default when connecting to a MySQL database, the port 3306/TCP is used. You should have to open up only the port that the server is listening on.
    Please consult your firewall manual for more information.

  • If you are connecting to a server behind a router using NAT, you may need to open/forward ports correctly in the router.
    Please consult your router manual, or visit "" for more information.

Network share

  • When experiencing problems saving to a network share, please make sure that the server is properly patched with the latest service packs.

  • Web page objects in your content require the internet access in order to display correctly. Please check your network connection.
    There is an option in the web page object, under the Advanced tab, Make object transparent if loading fails. In case the network connection is down, the web page object will not be shown.

  • In some rare cases, a faulty router or proxy causes files to be corrupted while downloading to the player, and DISE cannot load or render them properly.
    Please try a different router and see if that solves the problem.


Network message for triggering or synchronization are typically sent out using multicast. In some cases and if players are not on the same subnet multicast requires router configuration, else the packets will be intercepted and not reach the subscribers to the multicast. Consult the network administrator and/or your router manual for information about how to go about this.

There may also be a firewall or packet filter that blocks the multicast signal. Temporarily disable any firewall (including the Windows built-in) or antivirus software and check if messages come through.