Solution to DETRICK - GEILENKIRCHEN error

[>>wArMoNgEr<<]

So I finally fixed the DETRICK-GEILENKIRCHEN error, with not connecting to online services. This is on PC/Win10, so I don't know about consoles, but likely will be a similar problem. This error MOST DEFINITELY has to do with Firewall/Anti-Virus issues. In my case, it is Kaspersky Internet Security issues, combined with a Windows Defender Firewall issue not letting the MW2 HQ load. So this is what worked for me:

1. Go to your router's homepage, login, and insure that you have a hardware firewall up and running. If you don't have a wireless router, and just have a modem, then check to see if you can enable a hardware firewall on it.

2. Go back to Windows, and EXIT your A/V program. Make sure it is closed and process is not running. And if you are running Norton, God help you. (lol, I hate that program).

3. Run the game.

4. If your system does the same as mine did, as the game loads, a Windows Defender Firewall window will popup, telling you that it prevented MW2 HQ from loading. Click "Allow Process".

5. Game should load, connect you to online services pretty quick, and get you to the main screen.

Now I tried like mad in KIS to allow all COD processes, ports, allow UDP and TCP, and nothing, no go. It will STILL not load the game if KIS is running at all. But exit it, and game loads right up. Someone will eventually find out how to set up KIS to allow all the processes and stop this nonsense, but in the meantime, I was able to get the game to work and finish the campaign. Simply, I just don't run KIS when I run the game. And it works. This may or may not help you, but it is worth a try! I believe that KIS was actually hiding and/or preventing the Windows Defender Firewall error, so it was a compound problem. Your A/V program may be doing the same. Good Luck.

[Fred Durst]

EXIT A/V HOW

[Sufyaan]

thank you so much this issue has been driving me nuts for 2 weeks

[>>wArMoNgEr<<]

Originally posted by Bnadit:

EXIT A/V HOW

Well what A/V program you run? In KIS it is simple: right click on the green K in the system tray and then click "exit". Whatever program it is, right click on it, or do whatever you have to to close it- in order to test this fix. It appears to have helped one person already, so there must be something to it. Certainly worked for me after endless hours searching all over for a fix.

[Cmdr. George L. Rockwell]

I dont use any third part AV, necessary ports are open, and my internet connection is functional, and I still have the issue.

[Animal]

i had to whitelist "prod-data-energon.infra-ext.activision.com" in pihole

[󠁳⁧⁧HotKnives]

Originally posted by ✪ ΛΝΙΜΛL™:

i had to whitelist "prod-data-energon.infra-ext.activision.com" in pihole

Did that with my AdGuard Home and still doesn't work

[Flin† Beas†wood]

Originally posted by >>wArMoNgEr<<:

So I finally fixed the DETRICK-GEILENKIRCHEN error, with not connecting to online services. This is on PC/Win10, so I don't know about consoles, but likely will be a similar problem. This error MOST DEFINITELY has to do with Firewall/Anti-Virus issues. In my case, it is Kaspersky Internet Security issues, combined with a Windows Defender Firewall issue not letting the MW2 HQ load. So this is what worked for me:

1. Go to your router's homepage, login, and insure that you have a hardware firewall up and running. If you don't have a wireless router, and just have a modem, then check to see if you can enable a hardware firewall on it.

2. Go back to Windows, and EXIT your A/V program. Make sure it is closed and process is not running. And if you are running Norton, God help you. (lol, I hate that program).

3. Run the game.

4. If your system does the same as mine did, as the game loads, a Windows Defender Firewall window will popup, telling you that it prevented MW2 HQ from loading. Click "Allow Process".

5. Game should load, connect you to online services pretty quick, and get you to the main screen.

Now I tried like mad in KIS to allow all COD processes, ports, allow UDP and TCP, and nothing, no go. It will STILL not load the game if KIS is running at all. But exit it, and game loads right up. Someone will eventually find out how to set up KIS to allow all the processes and stop this nonsense, but in the meantime, I was able to get the game to work and finish the campaign. Simply, I just don't run KIS when I run the game. And it works. This may or may not help you, but it is worth a try! I believe that KIS was actually hiding and/or preventing the Windows Defender Firewall error, so it was a compound problem. Your A/V program may be doing the same. Good Luck.

Well i tell u what happed to me.. i updated w10, i got anoyed about the new w10 layout
coz it is too 3rd party active, i got some twiks and some security improvement like blocking 3rd parties, i have no firewall no antivirus, all my game are working fine, except for this one, so i can confirm that Activision are actually rapeing ur privacy in order to make ur product work, it is the only game that doesn't roll if i don't acept theyr intrusive 3rd partys on my hardware; it is not a problem of antivirus, i guess ur av tried to counter this security intrusively breaching application; this guys are collecting personal data about u outside the game, like browsing history and stuff like that and sells them to private company on your own expense

[Vyrex]

Geilen kirchen literatly means hot church in german Lol

[[LOC] JiKeidan]

Just so you know, before you read, I got this insanity to work... but you aren't going to like how:

This is some exceptional ♥♥♥♥♥♥♥♥. I have troubleshot, and troubleshot this stupid ♥♥♥♥ over and over for the last 3 hours, and here's the combination of efforts:

I don't like windows updates, I don't like invasive ♥♥♥♥♥♥♥♥ at all, that rips control of my system away from _me_ and puts it in the hands of whomesoever deems I needed xyz update at their time of their choosing... thus - I don't use windows defender, and use tinywall instead... so I can manually block even system processes if I choose, from making outbound talky talk to Microsoft servers... that said
1) I evaluated the COD.exe process as a blocked process.
2) I unblocked that process
3) I observed the various ip/port combinations in use, and those are:
a. 51740 localhost to 51741 localhost
b. 51741 localhost right back into 51740 localhost... why? (i'm sure they have their reasons)
c. udp listen 3074 on 0.0.0.0 - why?... because I'm not punching any holes in my firewall so a connection can originate from the outside and bombard my system.. figure out a better way - it isn't actually very difficult, given my personal experience with socket programming. If I'm hosting a server for the public to play around in, then sure... but this aint that kind of software you jackasses.
AND finally:
d. 51742 lan NIC to 34.111.232.148:443 - there's our reasonable connection guys...
all of the above, allowed by my local firewall.

4) I checked the activision site for maintenance or outages... All green

5) I scurried the net for a while only to find that people were ACTUALLY forwarding all of the recommended ports from activision ( https://support.activision.com/articles/ports-used-for-call-of-duty-games ) straight to their machines!...
a. Set a reminder to myself to start scanning residential public ip spaces for these services opened to the public, cuz... DAMN.
b. I said, to hell with it... forwarded UDP 3074 to my local machine, for testing... set up a virtual ip in my firewall and linked it all together.
c. Tried the connection again to find absolutely no other connections were established from cod.exe... still the same 51740-51741 and 3074 just sitting there listening doing nothing. This means, that my outbound and initial communication to the activision servers did not result in a recognized new client, and a response to the recommended listening UDP port 3074. Great... now what?... are any of those other ports actually being used instead before 3074?
d. To hell with it

6) I went ahead and disabled my firewall completely and then ran the tests again... no change

7) I actually hopped in line to make my network vulnerable to the world, for testing purposes of course... and forwarded EVERYTHING (listed under "steam"): 3074, 27015, 27036 3074, 27015, 27031-27036 all to my vulnerable little machine just dying to say hello to all the friendly new probes.
a. Re-ran the tests... guess what guys? No difference whatsoever, in ANY of the readings.

8) I went ahead and verified files for the game in steam, and to my surprise, 37 of the files needed to be re-downloaded... this was hopefull! at long last, the complicated issue, a simple fix.
a. repaired files, started back up... still didn't work - DAMNIT ALL!

9) Went back to the drawing board:
a) And... ... Added, yup!... the PC version port recommendations: PC 3074, 4000, 6112-6119, 20500, 20510, 27014-27050, 28960 then... UDP 3074, 3478, 4379-4380, 6112-6119, 20500, 20510, 27000-27031, 27036, 28960

and it worked...

Although I had my firewall disabled this whole time, I did not turn it off entirely, I kept it up watching the connections initiating...

I noticed NO inbound connections coming in to the cod.exe process... fwiw

8) I immediately started my local firewall/router back up and disabled my hardware firewall policies allowing all of those ports straight into my poor computer at my gateway/edge whatever you want to call it these days... and EVERYTHING continued to work.

9) I immediately joined a quick match real quick just to do it and ensure that all was still operational...
a. It found the match, joined me up, and I was off in MW2 world just like that...

My best guess, guys.. .is that one or the other of the ports was accessed externally and inbound by a completely different service on my computer somehow in order to transfer some kind of information, completely outside of the scope of steam or cod, in order to get my account logged in with Activision. Once I was logged in, Game Over. Didn't need it anymore...

Some serious ♥♥♥♥♥♥♥ ♥♥♥♥♥♥♥♥.

EDIT:
Here I am 3 days later and I am mid-game... get the TRAVIS - RILEA error... (and seriously wtf is up w/ these error codes? Why not just respond with the actual error - network timeout... destination unreachable... etc - grow the ♥♥♥♥ up). This specific error is a sign-in error and so I went back to retrace my troubleshooting steps. I came to discover that my inbound policies for all of those ports, actually have 0B of data transited...

I'm assuming folks, that all of this is purely server-side... Don't adjust your firewall, don't restart your router. If you have network connectivity, it sounds like you just need to wait until they sort out their issues on their end and try again later. I can't find any evidence that suggests otherwise. This would also probably indicate that their "server status" page is manually driven - otherwise why wouldn't it show an issue?

In summation, I think the only real takeaway here is that Activision wouldn't be hurting us any if they decided to expound on their error responses a bit. It would sure help me to know what my part to play actually is.

AN HOUR LATER:
Sure enough... no reboots, policies, firewall tampering or otherwise... and turned the game back on and it logged right in.

[Vreydensbyrg]

Originally posted by LOC JiKeidan:

...

Fu** Activision, I can't play, probably some ipv4/6 routing problems because of ds-lite. I'm still having the maintenance symbol in the bnet client and opening port's wont work, because of the ipv6-to-ipv4-tunnel...

[Pure & Rustic]

Originally posted by Vreydensbyrg:

Originally posted by LOC JiKeidan:

...

Fu** Activision, I can't play, probably some ipv4/6 routing problems because of ds-lite. I'm still having the maintenance symbol in the bnet client and opening port's wont work, because of the ipv6-to-ipv4-tunnel...

Set IPv6 in router as passthrough. That works fine for me.

[Vreydensbyrg]

Originally posted by Pure & Rustic:

Originally posted by Vreydensbyrg:

Fu** Activision, I can't play, probably some ipv4/6 routing problems because of ds-lite. I'm still having the maintenance symbol in the bnet client and opening port's wont work, because of the ipv6-to-ipv4-tunnel...

Set IPv6 in router as passthrough. That works fine for me.

passthrough ipv6? what? I don't use ipv6 in my LAN, on won't for now :P
But I fixed it. I'm using simplewall, and IMO a recent update caused that error.
What I have to do is allowing plain HTTP connections (port) as a user rule for an initial connection, then it'll work for every run or you can just disable all the firewalls completely and start the game, connect/update in-game and enable the fw again.

[[LOC] JiKeidan]

Oh Activision... you are just so unworthy. At the very least, I shouldn't have to have a network connection to putz around in campaign mode... piss poor leadership. I think the dollars I spent on the game to begin with entitle me to that much... but alas. You take direction from the wrong sources. Garbage.

Wait... how am I posting this?! DETRICK - GEILENKIRCHEN after all!!

[Pure & Rustic]

Originally posted by Vreydensbyrg:

Originally posted by Pure & Rustic:

Set IPv6 in router as passthrough. That works fine for me.

passthrough ipv6? what? I don't use ipv6 in my LAN, on won't for now :P
But I fixed it. I'm using simplewall, and IMO a recent update caused that error.
What I have to do is allowing plain HTTP connections (port) as a user rule for an initial connection, then it'll work for every run or you can just disable all the firewalls completely and start the game, connect/update in-game and enable the fw again.

If it works for you... good... But i will NOT advise anyone to disable firewall anywere.

i have it enbled firewall in PC, Router and for IPv6 in my homesentral (were the fiber ends inside my home and split internet, tv and IP-tlf).

[Vreydensbyrg]

Originally posted by Pure & Rustic:

Originally posted by Vreydensbyrg:

passthrough ipv6? what? I don't use ipv6 in my LAN, on won't for now :P
But I fixed it. I'm using simplewall, and IMO a recent update caused that error.
What I have to do is allowing plain HTTP connections (port) as a user rule for an initial connection, then it'll work for every run or you can just disable all the firewalls completely and start the game, connect/update in-game and enable the fw again.

If it works for you... good... But i will NOT advise anyone to disable firewall anywere.

i have it enbled firewall in PC, Router and for IPv6 in my homesentral (were the fiber ends inside my home and split internet, tv and IP-tlf).

My routers fw was still enabled, only local access was possible for that short time :)