gofrm76 Posted July 4 Posted July 4 (edited) Hello, since yesterday, I'm having problems logging into DCS World. Looking into the logs it seems I'm getting a timeout while trying to connect to api.digitalcombatsimulator.com. It doesn't look like a DNS issue since resolving the IP address is working and I also double checked the IP resolution using a different ISP with which I can normally log in to DCS. So for some reason the IP 185.195.197.20 (api.digitalcombatsimulator.com) is being blocked somewhere on the way from my ISP (Germany) to xelon.ch (Swiss) which seems to be the datacenter that hosts the DCS servers. I already called my ISP and they are looking into this issue from their side. I just wanted to ask if it could also be something DCS Server related. www.digitalcombatsimulator.com, which resolves to 93.115.211.146, also hosted at Xelon, is working fine btw. regards Christian Edited July 4 by gofrm76 AH-64D | AV-8B | A-10C II | A-4E | F-4E | F-5E | F-14B | F-15E | F-16C | F/A-18C | M-2000C | UH-1H | Mig-21bis | L-39 | F-86F | P-47D | P-51D | BF 109 | Spitfire | BS3 | FC3 | SC | CA Intel® Core™ i7-13700K | NVIDIA RTX 4090 | 64 GB DDR5 RAM | Aorus Elite Z790 | 50“ UHD LG Monitor | Windows 11 Pro VPC Rotor TCS Plus Base | VPC Apache-64 Collective Grip | VPC Hawk-60 Collective Grip | VPC MongoosT-50CM3 Base | TM F-16/A-10 Stick | TM F/A-18 Stick TM HOTAS Warthog (DSE Slew Upgrade) | TM Hotas Cougar (FSSB) | TM Pendular Rudder | HP Reverb G2 | TrackIR 5
MAXsenna Posted July 4 Posted July 4 Make traceroute, a s you can see exactly where it stops. If can, try with VPN, if that works it's your ISP.It's not a site issue. It's been up for me for years, except planned and unplanned maintenance.Cheers! Sent from my SM-A536B using Tapatalk
silverdevil Posted July 4 Posted July 4 15 hours ago, gofrm76 said: Hello, since yesterday, I'm having problems logging into DCS World. Looking into the logs it seems I'm getting a timeout while trying to connect to api.digitalcombatsimulator.com. It doesn't look like a DNS issue since resolving the IP address is working and I also double checked the IP resolution using a different ISP with which I can normally log in to DCS. So for some reason the IP 185.195.197.20 (api.digitalcombatsimulator.com) is being blocked somewhere on the way from my ISP (Germany) to xelon.ch (Swiss) which seems to be the datacenter that hosts the DCS servers. I already called my ISP and they are looking into this issue from their side. I just wanted to ask if it could also be something DCS Server related. www.digitalcombatsimulator.com, which resolves to 93.115.211.146, also hosted at Xelon, is working fine btw. regards Christian by chance have you edited your HOSTS file? there was a strange issue previously, that a workaround was to edit this file. C:\Windows\System32\drivers\etc 1 AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
sky66 Posted July 5 Posted July 5 Hello, do you already have a solution to this problem? Or how can I change my host IP? Thanks André
silverdevil Posted July 5 Posted July 5 55 minutes ago, sky66 said: Hello, do you already have a solution to this problem? Or how can I change my host IP? Thanks André hello. you will need to explain further. i am unsure what you mean. 1 AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
gofrm76 Posted July 5 Author Posted July 5 15 hours ago, silverdevil said: by chance have you edited your HOSTS file? there was a strange issue previously, that a workaround was to edit this file. C:\Windows\System32\drivers\etc I also tried this but this isn‘t a DNS Problem. Its the DCS Server Ip that is beeing blocked… 1 AH-64D | AV-8B | A-10C II | A-4E | F-4E | F-5E | F-14B | F-15E | F-16C | F/A-18C | M-2000C | UH-1H | Mig-21bis | L-39 | F-86F | P-47D | P-51D | BF 109 | Spitfire | BS3 | FC3 | SC | CA Intel® Core™ i7-13700K | NVIDIA RTX 4090 | 64 GB DDR5 RAM | Aorus Elite Z790 | 50“ UHD LG Monitor | Windows 11 Pro VPC Rotor TCS Plus Base | VPC Apache-64 Collective Grip | VPC Hawk-60 Collective Grip | VPC MongoosT-50CM3 Base | TM F-16/A-10 Stick | TM F/A-18 Stick TM HOTAS Warthog (DSE Slew Upgrade) | TM Hotas Cougar (FSSB) | TM Pendular Rudder | HP Reverb G2 | TrackIR 5
silverdevil Posted July 5 Posted July 5 3 hours ago, gofrm76 said: I also tried this but this isn‘t a DNS Problem. Its the DCS Server Ip that is beeing blocked… hello again, this is my nslookup results. i have verizon in eastern US. Default Server: dns.google Address: 8.8.8.8 > www.digitalcombatsimulator.com Server: dns.google Address: 8.8.8.8 Non-authoritative answer: Name: digitalcombatsimulator.com Address: 93.115.211.146 Aliases: www.digitalcombatsimulator.com > api.digitalcombatsimulator.com Server: dns.google Address: 8.8.8.8 Non-authoritative answer: Name: api.digitalcombatsimulator.com Address: 185.195.197.20 maybe change your DNS to 8.8.8.8 and 8.8.4.4 and see what happens. AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
gofrm76 Posted July 6 Author Posted July 6 8 hours ago, silverdevil said: Non-authoritative answer: Name: api.digitalcombatsimulator.com Address: 185.195.197.20 maybe change your DNS to 8.8.8.8 and 8.8.4.4 and see what happens. Thanks for the help. As mentioned above, I tried the DNS solution already - while logged in with Giganetz ISP as well as with my backup ISP (where the DCS login is working). In both cases, a nslookup would return the correct IP, which is, as you also mentioned, 185.195.197.20. So DNS is ruled out, the IP itself is blocked or not routed correctly, or whatever. AH-64D | AV-8B | A-10C II | A-4E | F-4E | F-5E | F-14B | F-15E | F-16C | F/A-18C | M-2000C | UH-1H | Mig-21bis | L-39 | F-86F | P-47D | P-51D | BF 109 | Spitfire | BS3 | FC3 | SC | CA Intel® Core™ i7-13700K | NVIDIA RTX 4090 | 64 GB DDR5 RAM | Aorus Elite Z790 | 50“ UHD LG Monitor | Windows 11 Pro VPC Rotor TCS Plus Base | VPC Apache-64 Collective Grip | VPC Hawk-60 Collective Grip | VPC MongoosT-50CM3 Base | TM F-16/A-10 Stick | TM F/A-18 Stick TM HOTAS Warthog (DSE Slew Upgrade) | TM Hotas Cougar (FSSB) | TM Pendular Rudder | HP Reverb G2 | TrackIR 5
MAXsenna Posted July 6 Posted July 6 Thanks for the help. As mentioned above, I tried the DNS solution already - while logged in with Giganetz ISP as well as with my backup ISP (where the DCS login is working). In both cases, a nslookup would return the correct IP, which is, as you also mentioned, 185.195.197.20. So DNS is ruled out, the IP itself is blocked or not routed correctly, or whatever.That's why you want to perform a traceroute so you can tell your ISP where it stops. Sent from my SM-A536B using Tapatalk
africatom Posted July 6 Posted July 6 Hi gofrm76, i have exactly the same problem and hope that someone can solve it. I also tried all the things above including reinstall. i5-13600KF, Gigabyte B760 Gaming X DDR4, Gainward RTX 4070 12GB, 64GB DDR4, Win11, TIR 5, Thrustmaster HOTAS Warthog, Simped Ruderpedale
MAXsenna Posted July 6 Posted July 6 (edited) 3 minutes ago, africatom said: Hi gofrm76, i have exactly the same problem and hope that someone can solve it. I also tried all the things above including reinstall. A re-installation will never help with that issue. Even better, you can perform a repair that will take minutes and reset all the core files. And if rename your DCS Saved Games folder, the game will be completely reset to vanilla. Perform a traceroute, and it will tell you where the problems are on the route to the site. Open a command line window, type tracer address and press enter, and off you go. Edited July 6 by MAXsenna
africatom Posted July 6 Posted July 6 I got an Timeout after decix.as8758.net [80.81.196.173] i5-13600KF, Gigabyte B760 Gaming X DDR4, Gainward RTX 4070 12GB, 64GB DDR4, Win11, TIR 5, Thrustmaster HOTAS Warthog, Simped Ruderpedale
gofrm76 Posted July 6 Author Posted July 6 3 hours ago, MAXsenna said: That's why you want to perform a traceroute so you can tell your ISP where it stops. Good point. I will add this info when I call the provider next week. 50 minutes ago, africatom said: I got an Timeout after decix.as8758.net [80.81.196.173] same here: traceroute to 185.195.197.20 (185.195.197.20), 30 hops max, 60 byte packets 1 fritz.box (192.168.178.1) 0.662 ms 0.745 ms 0.823 ms 2 100.83.142.145 (100.83.142.145) 5.390 ms 5.331 ms 5.503 ms 3 100.83.140.62 (100.83.140.62) 5.802 ms 5.553 ms 5.611 ms 4 100.83.140.234 (100.83.140.234) 5.714 ms 5.645 ms 7.061 ms 5 100.83.140.33 (100.83.140.33) 7.106 ms 100.83.140.95 (100.83.140.95) 7.156 ms 6.968 ms 6 100.83.140.128 (100.83.140.128) 6.923 ms 3.343 ms 100.83.140.242 (100.83.140.242) 5.396 ms 7 decix.as8758.net (80.81.196.173) 10.530 ms 10.350 ms 11.719 ms 8 * * * 9 * * * AH-64D | AV-8B | A-10C II | A-4E | F-4E | F-5E | F-14B | F-15E | F-16C | F/A-18C | M-2000C | UH-1H | Mig-21bis | L-39 | F-86F | P-47D | P-51D | BF 109 | Spitfire | BS3 | FC3 | SC | CA Intel® Core™ i7-13700K | NVIDIA RTX 4090 | 64 GB DDR5 RAM | Aorus Elite Z790 | 50“ UHD LG Monitor | Windows 11 Pro VPC Rotor TCS Plus Base | VPC Apache-64 Collective Grip | VPC Hawk-60 Collective Grip | VPC MongoosT-50CM3 Base | TM F-16/A-10 Stick | TM F/A-18 Stick TM HOTAS Warthog (DSE Slew Upgrade) | TM Hotas Cougar (FSSB) | TM Pendular Rudder | HP Reverb G2 | TrackIR 5
sky66 Posted July 6 Posted July 6 exactly the same with me Routenverfolgung zu 185-195-197-20.static.xelon.ch [185.195.197.20] über maximal 30 Hops: 1 2 ms 2 ms 1 ms fritz.box [192.168.178.1] 2 * 4 ms 6 ms 100.83.142.141 3 27 ms 5 ms 2 ms 100.83.140.62 4 * 5 ms 4 ms 100.83.140.234 5 35 ms 4 ms 5 ms 100.83.140.33 6 5 ms 5 ms 5 ms 100.83.140.242 7 * 11 ms 21 ms decix.as8758.net [80.81.196.173] 8 * * * Zeitüberschreitung der Anforderung. 9 * * * Zeitüberschreitung der Anforderung. 10 * * * Zeitüberschreitung der Anforderung. 11 * * * Zeitüberschreitung der Anforderung.
silverdevil Posted July 6 Posted July 6 56 minutes ago, gofrm76 said: Good point. I will add this info when I call the provider next week. same here: traceroute to 185.195.197.20 (185.195.197.20), 30 hops max, 60 byte packets 1 fritz.box (192.168.178.1) 0.662 ms 0.745 ms 0.823 ms 2 100.83.142.145 (100.83.142.145) 5.390 ms 5.331 ms 5.503 ms 3 100.83.140.62 (100.83.140.62) 5.802 ms 5.553 ms 5.611 ms 4 100.83.140.234 (100.83.140.234) 5.714 ms 5.645 ms 7.061 ms 5 100.83.140.33 (100.83.140.33) 7.106 ms 100.83.140.95 (100.83.140.95) 7.156 ms 6.968 ms 6 100.83.140.128 (100.83.140.128) 6.923 ms 3.343 ms 100.83.140.242 (100.83.140.242) 5.396 ms 7 decix.as8758.net (80.81.196.173) 10.530 ms 10.350 ms 11.719 ms 8 * * * 9 * * * so we can compare. this is results of my tracert. Tracing route to api.digitalcombatsimulator.com [185.195.197.20] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 4 ms 4 ms 4 ms lo0-100.NRFLVA-VFTTP-314.verizon-gni.net [96.225.167.1] 3 5 ms 6 ms 6 ms 100.41.26.70 4 * * 11 ms lag-2.ASBNVAEG-PPR01-CC.ALTER.NET [140.222.9.49] 5 * * * Request timed out. 6 11 ms 13 ms * ash-bb2-link.ip.twelve99.net [62.115.141.51] 7 * * * Request timed out. 8 106 ms 108 ms 107 ms ffm-bb2-link.ip.twelve99.net [62.115.122.139] 9 * 112 ms 110 ms zch-b1-link.ip.twelve99.net [62.115.138.47] 10 111 ms 123 ms 111 ms nine-ic-337845.ip.twelve99-cust.net [80.239.160.27] 11 111 ms 110 ms 112 ms e1-1.c-r1.es13.nine.ch [5.148.160.173] 12 110 ms 111 ms 111 ms 185.88.239.2 13 244 ms 138 ms 131 ms 109-106-19-246.static.xelon.ch [109.106.19.246] 14 112 ms 112 ms 112 ms 185-195-197-20.static.xelon.ch [185.195.197.20] Trace complete. 1 AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
Recommended Posts