Nature of the problem: Trying to Connect to online services. Keep getting Unable to Connect Error
Game Version 6.20 (511811)
- No mods activated, Mods used only through Steam Workshop, no manual installs.
- Steam account already linked to my egosoft account.
- Venture Extension downloaded and says validated successfully (v1.23)
Attempted:
- Already checked Windows Firewall, permissions for both public and private networks for X4 present.
- Double checked user credentials and password; I am able to log in and out of forums no issue.
- Able to visit Egosoft main website with no issues; checking if it might be a server availability issue.
Any possibly relevant changes you have made to your game, system, or software before the issue occurred.
- Recently purchased COP CE edition, but I've had the Non-CE Edition before.
- Game freshly installed recently
Unable to Connect Error when logging in in-game for Online Features
Moderator: Moderators for English X Forum
-
theanorak
- Posts: 1
- Joined: Wed, 6. Jul 22, 07:37
-
Daemonjax
- Posts: 288
- Joined: Tue, 27. May 14, 01:54
Re: Unable to Connect Error when logging in in-game for Online Features
My first thought is that it's probably firewall related. Do you run a software firewall (other than windows firewall, because that doesn't really do anything)?
EDIT:
Ok, you mention windows firewall, so you're probably not running a real software firewall.
Not sure... but... I would still check to verify that lsass.exe can connect to the server it wants to because (weirdly, IMO) it needs to for the connection to work (not just x4.exe).
There's an old post I made about this, I'll see if I can find it (it was in another person's thread)...
Here you go (someone else also mentions cryptographic services, but that should always be enabled and doesn't require a firewall rule IIRC, but read the thread because I'm drunk):
viewtopic.php?f=180&t=456869&p=5200913#p5200913
Personally... I'm not a fan of the windows firewall user interface... particularly looking at the logs for pass/fail (good luck)... the base filtering engine service is fine, though. I use wfc as a windows firewall GUI for my home PC. Another fine alternative gui is tinywall, but even with that the logging is insufficient for my needs (but at least there's something), in addition to not have all the other functionality for rule creation I need (it's really basic -- best used for cases where you just need to block/allow .exe's and nothing more). On the other hand, wfc needs some tweaking to disable logging when the GUI app isn't running otherwise it causes a systemwide performance hit (via custom scripting), but I'm all about squeezing every drop of performance on my gaming PC so maybe I'm being fussy.
Edit2: And I re-read the cryptsrv comment, and I know for a FACT allowing outbound traffic for cryptsrv over port 80 isn't required because my home router's firewall rules actually blocks all outbound traffic over port 80. Cryptsrv will WANT to connect over port 80, but want isn't the same as need. Well, maybe maybe it needs to connect just once for the keys... but no, my router's firewall would not allow that.
EDIT:
Ok, you mention windows firewall, so you're probably not running a real software firewall.
Not sure... but... I would still check to verify that lsass.exe can connect to the server it wants to because (weirdly, IMO) it needs to for the connection to work (not just x4.exe).
There's an old post I made about this, I'll see if I can find it (it was in another person's thread)...
Here you go (someone else also mentions cryptographic services, but that should always be enabled and doesn't require a firewall rule IIRC, but read the thread because I'm drunk):
viewtopic.php?f=180&t=456869&p=5200913#p5200913
Personally... I'm not a fan of the windows firewall user interface... particularly looking at the logs for pass/fail (good luck)... the base filtering engine service is fine, though. I use wfc as a windows firewall GUI for my home PC. Another fine alternative gui is tinywall, but even with that the logging is insufficient for my needs (but at least there's something), in addition to not have all the other functionality for rule creation I need (it's really basic -- best used for cases where you just need to block/allow .exe's and nothing more). On the other hand, wfc needs some tweaking to disable logging when the GUI app isn't running otherwise it causes a systemwide performance hit (via custom scripting), but I'm all about squeezing every drop of performance on my gaming PC so maybe I'm being fussy.
Edit2: And I re-read the cryptsrv comment, and I know for a FACT allowing outbound traffic for cryptsrv over port 80 isn't required because my home router's firewall rules actually blocks all outbound traffic over port 80. Cryptsrv will WANT to connect over port 80, but want isn't the same as need. Well, maybe maybe it needs to connect just once for the keys... but no, my router's firewall would not allow that.