Browse By Category: | Look Up Error Number: | Search: |
Glossary | Contact Us |
Rating: 66
Description: DinkeyServer not detected on the network.
Either DinkeyServer is not running or it is being blocked by a firewall. Failure to correctly configure your firewall(s) could result in DinkeyServer being inaccessible by client machines.
Your firewall must allow both TCP and UDP traffic through to DinkeyServer. It must also allow DinkeyServer to accept incoming connections on the IP Address and Port that you chose when setting up DinkeyServer.
For most firewalls (including Windows Firewall) this just involves adding DinkeyServer to the list of exceptions. To do this for Windows Firewall go to Control Panel | Windows Firewall.
Note - some anti-virus programs can also include a firewall as part of the package.
Note - if you have protected a Universal Windows Pltaforms App (formally called a Windows Store App or Metro App) then you can get this error if you have not enabled the "Private Networks (Client and Server)" Capability in your package manifest.
Alternatively it can also occur if DinkeyServer is version 5.6.1 or higher and the protected runtime module is earlier than this version (or vice versa). It is recommended that both runtime code and DinkeyServer is at least version 5.6.1.
If your computer has more than one network adapter (including virtual adapters) then try disabling them until one works.
Finally, on a very few rare cases if auto-discovery does not work across the network then you can use the <prodcode>.ini file to specify the location of the dongle server. See manual for details.
If this article did not help you to solve your problem, please use the menu at the top of the page to browse or search more articles, or to contact our support team.
Error 401 | |
Error 671 | |
Error 923 | |
Error 400 | |
Error 402 | |
Error 403 | |