5 replies to this topic

[-3cHo^]

I have the steam version of the game.

Had the 'could not login to kane's wrath online' problem

I using windows 7

 

I think the problem could be with my country's ISP

 

Error log:

----- C&C:Online Launcher Start -----

Game: Kane's Wrath

Kane's Wrath Install Path: C:\Program Files (x86)\Steam\steamapps\common\Command and Conquer 3 - Kane's Wrath\

Started game with: ""C:\Program Files (x86)\Steam\steamapps\common\Command and Conquer 3 - Kane's Wrath\CNC3EP1.exe" -config "C:\Program Files (x86)\Steam\steamapps\common\Command and Conquer 3 - Kane's Wrath\CNC3EP1_english_1.2.SkuDef" "

Caught CREATE_PROCESS_DEBUG_EVENT from Kane's Wrath. Detaching...

ERROR: game.dat process not found.

 

 

----- C&C:Online Launcher Start -----

Game: Kane's Wrath

Kane's Wrath Install Path: C:\Program Files (x86)\Steam\steamapps\common\Command and Conquer 3 - Kane's Wrath\

Started game with: ""C:\Program Files (x86)\Steam\steamapps\common\Command and Conquer 3 - Kane's Wrath\CNC3EP1.exe" -config "C:\Program Files (x86)\Steam\steamapps\common\Command and Conquer 3 - Kane's Wrath\CNC3EP1_english_1.2.SkuDef" "

Caught CREATE_PROCESS_DEBUG_EVENT from Kane's Wrath. Detaching...

Found game.dat process. PID 2584

*** Starting CA public key patching routine ***

CA public key is expected value.

Successfully patched CA public key.

*** Starting hostname hooking routine ***

Injecting DLL into game.dat process...

Result of injection: Code -1073741582

[ToxicShock]

Yes, unfortunately, you're right. Your ISP, Tm.net blocks TCP port 6667 which these games need to use to connect at the moment. That is an age old problem, I'm afraid (gamespy used that port too). We've been looking at a way of avoiding using that port, but that is not likely to be available for a few months, at least. All I can suggest at the moment is using a different ISP (or mobile internet) or looking for a service that tunnels out of your network using a different port. You should google "TCP port 6667" to see if you can find anything that way.

[-3cHo^]

Thanks for the help and advice.

[xezon]

Yes, unfortunately, you're right. Your ISP, Tm.net blocks TCP port 6667 which these games need to use to connect at the moment. That is an age old problem, I'm afraid (gamespy used that port too). We've been looking at a way of avoiding using that port, but that is not likely to be available for a few months, at least. All I can suggest at the moment is using a different ISP (or mobile internet) or looking for a service that tunnels out of your network using a different port. You should google "TCP port 6667" to see if you can find anything that way.

 

Why would that require a few months? What is blocking it so much?

[ToxicShock]

Once we settle on a way of sending Peer Chat to an alternate port and implement it, we are going to have to test that, as well as the server changes on the dev server. As it is the core of the multiplayer in these games, we can't afford for it not to work so we're going to have to test it thoroughly.

[RTS*(Champion)]

Thank you toxic. Hope to be online till then