Games: Elite Dangerous

Problem

Description: While Steam launches and works fine, launching Elite Dangerous shows problems are at hand.

Symptom is an error message dialogbox: Unable to initialise network. Please check your connection

Context

• Experience Platform: Elite Dangerous (3.x) in Steam on Microsoft Windows 10 Professional (fully patched)

• Context Scope: this should work for any platform connected to the internet

• Valve Network: IPv4 and IPv6 prefixes documented here

• Frontier Cloud: Elite Dangerous Network requirements

Fix Procedure

• removed, rebooted and reinstalled .NET 4.7

• Validate the ports and prefixes to be open and available for UDP and TCP as documented here

• deleted AppConfigLocal.xml

• started Elite Dangerous from Steam GUI

Conclusion

While the Steasm/Valve IP prefixes and ports were correctly configured the port 19364/UDP was missing, it is unclear why this is missing in the documentation for Steam or if this is Elite Dangerous specific.

Also, two large subnet (/12 /13)were appended to the valve ip list.

Resources

• Delete AppConfigLocal.xml from the Frontier KB documented path for Elite Dangerous

• Valve Network and Elite Dangerous Network configuration requirements :

• Valve Prefixes IPv4 and IPv6

• Steamcommunity forum post on UDP Ports

Vendor Support : Follow up support request response from Frontier

+ Right click on the start menu and choose Command Prompt (Admin) from the menu.
+ Type in the command prompt ipconfig /flushdns and press enter (reboot after it completes)
+ Type in the command prompt netsh winsock reset and press enter (reboot after it completes)
+ Type in the command prompt netsh int ip reset c:\ipreset.txt and press enter (reboot after it completes)

status : error persists, no fix