Wild Fire Posted August 23, 2020 Member ID: 5468 Group: *** Clan Members Followers: 36 Topic Count: 19 Topics Per Day: 0.00 Content Count: 674 Content Per Day: 0.17 Reputation: 655 Achievement Points: 6445 Solved Content: 0 Days Won: 0 Joined: 02/04/13 Status: Offline Last Seen: Yesterday at 02:54 AM Birthday: 06/22/1965 Device: Android Share Posted August 23, 2020 Hey Gang, I felt this deserved a thread of its own. Something has changed on the MW2 Freeze tag server in the last two weeks. I went to join the MW2 freeze tag server on Saturday, and have been unable to access the server. Only the IP address shows in my favourites list, not the name, like it used to. I thought maybe the IP address changed so I deleted it from my fav list and added it back. No change. When I tried to join, it just spins it's wheels until I get the Error message "Server connection time out". So I tried to connect to the server from the console. Same result. Loco suggested I increase the cl_connectionAttempts to 30, so I tried that, and still get the error message. WldPenguin suggested I reboot computer modem and I have done both of those, and still no connect. I can see, and can connect to the Freeze tag 1 server, the Ace Mod, the DM server, and the test map server. So I can connect. BUT the MW2 freeze tag server, (as well as Zombie and MW #2 server) still remains inaccessible to me. It is so weird that I can connect to the other servers but not the MW2. Anybody have any suggestions? Link to comment Share on other sites More sharing options... Awards
Wild Fire Posted August 23, 2020 Member ID: 5468 Group: *** Clan Members Followers: 36 Topic Count: 19 Topics Per Day: 0.00 Content Count: 674 Content Per Day: 0.17 Reputation: 655 Achievement Points: 6445 Solved Content: 0 Days Won: 0 Joined: 02/04/13 Status: Offline Last Seen: Yesterday at 02:54 AM Birthday: 06/22/1965 Device: Android Author Share Posted August 23, 2020 I have run a tracer route a few times and to the MW2 server, results below. I then ran a tracer route to the DM server and the result was a bit better, with pings in the 70-90 ms area. traceroute 162.248.95.178 traceroute to 162.248.95.178 (162.248.95.178), 64 hops max, 52 byte packets 1 192.168.1.254 (192.168.1.254) 1.121 ms 0.628 ms 0.587 ms 2 10.145.160.1 (10.145.160.1) 5.723 ms 11.067 ms 5.826 ms 3 sttlwawbci01.bb.telus.com (75.154.217.106) 32.494 ms 26.978 ms sttlwawbci01.bb.telus.com (75.154.217.108) 27.388 ms 4 be-210-pe02.seattle.wa.ibone.comcast.net (23.30.206.109) 26.373 ms 28.744 ms 23.085 ms 5 be-10847-cr01.seattle.wa.ibone.comcast.net (68.86.86.225) 32.850 ms 26.472 ms 29.871 ms 6 be-301-cr11.champa.co.ibone.comcast.net (96.110.36.209) 65.356 ms 67.295 ms 62.108 ms 7 be-1311-cs03.champa.co.ibone.comcast.net (96.110.37.201) 61.148 ms 61.369 ms 55.887 ms 8 be-1413-cr13.champa.co.ibone.comcast.net (96.110.37.238) 62.081 ms 63.960 ms * 9 be-304-cr14.1601milehigh.co.ibone.comcast.net (96.110.39.14) 61.772 ms be-301-cr13.1601milehigh.co.ibone.comcast.net (96.110.36.194) 62.204 ms * 10 be-1414-cs04.1601milehigh.co.ibone.comcast.net (96.110.39.125) 61.341 ms be-1213-cs02.1601milehigh.co.ibone.comcast.net (96.110.39.101) 56.525 ms 54.737 ms 11 be-1111-cr11.1601milehigh.co.ibone.comcast.net (96.110.39.66) 56.481 ms be-1311-cr11.1601milehigh.co.ibone.comcast.net (96.110.39.74) 56.324 ms 54.713 ms 12 be-301-cr11.350ecermak.il.ibone.comcast.net (96.110.37.145) 70.831 ms be-303-cr11.350ecermak.il.ibone.comcast.net (96.110.37.153) 61.036 ms * 13 * be-1211-cs02.350ecermak.il.ibone.comcast.net (96.110.35.5) 60.639 ms 62.043 ms 14 be-1314-cr14.350ecermak.il.ibone.comcast.net (96.110.35.58) 56.139 ms 60.901 ms * 15 be-302-cr12.pittsburgh.pa.ibone.comcast.net (96.110.39.162) 72.918 ms 67.219 ms be-301-cr12.pittsburgh.pa.ibone.comcast.net (96.110.39.158) 81.540 ms 16 be-1112-cs01.pittsburgh.pa.ibone.comcast.net (96.110.38.145) 67.718 ms 66.411 ms 72.115 ms 17 be-1111-cr11.pittsburgh.pa.ibone.comcast.net (96.110.38.130) 72.468 ms 73.239 ms * 18 be-301-cr12.ashburn.va.ibone.comcast.net (96.110.39.165) 71.096 ms * * 19 be-1312-cs03.ashburn.va.ibone.comcast.net (96.110.32.209) 81.588 ms be-1112-cs01.ashburn.va.ibone.comcast.net (96.110.32.201) 76.383 ms be-1312-cs03.ashburn.va.ibone.comcast.net (96.110.32.209) 78.428 ms 20 be-1213-cr13.ashburn.va.ibone.comcast.net (96.110.34.150) 72.653 ms be-1313-cr13.ashburn.va.ibone.comcast.net (96.110.34.154) 71.418 ms be-1113-cr13.ashburn.va.ibone.comcast.net (96.110.34.146) 77.634 ms 21 be-301-cr12.newark.nj.ibone.comcast.net (96.110.36.114) 89.067 ms * 89.580 ms 22 be-1412-cs04.newark.nj.ibone.comcast.net (96.110.35.93) 81.971 ms be-1212-cs02.newark.nj.ibone.comcast.net (96.110.35.85) 77.237 ms 75.034 ms 23 be-1201-cr01.newark.nj.ibone.comcast.net (96.110.36.86) 89.759 ms be-1101-cr01.newark.nj.ibone.comcast.net (96.110.36.82) 76.725 ms 80.992 ms 24 * * * 25 be-10381-pe02.111eighthave.ny.ibone.comcast.net (68.86.86.250) 81.194 ms 90.516 ms 82.217 ms 26 96-87-8-82-static.hfc.comcastbusiness.net (96.87.8.82) 82.294 ms 75.387 ms 82.334 ms 27 border2-po2-bbnet2.nyj004.pnap.net (216.52.95.110) 85.482 ms border2-po1-bbnet1.nyj004.pnap.net (216.52.95.47) 85.495 ms * 28 inap-b2.e8.router.nyc.nfoservers.com (104.153.107.254) 82.423 ms inap-b1.e9.router.nyc.nfoservers.com (162.248.95.254) 81.359 ms inap-b2.e8.router.nyc.nfoservers.com (104.153.107.254) 80.652 ms 29 c-162-248-95-178.managed-ded.inap-nyc.nfoservers.com (162.248.95.178) 82.922 ms 88.368 ms 82.124 ms Link to comment Share on other sites More sharing options... Awards
Sharpe Posted August 23, 2020 Member ID: 23520 Group: *** Clan Members Followers: 30 Topic Count: 12 Topics Per Day: 0.00 Content Count: 737 Content Per Day: 0.24 Reputation: 820 Achievement Points: 7105 Solved Content: 0 Days Won: 1 Joined: 11/13/15 Status: Offline Last Seen: 14 hours ago Device: Windows Share Posted August 23, 2020 (edited) Seeing quite a few suggestions online about the dns cache. "For those who haven't fixed this problem, I got mine back to normal after switching back to my ISP's DNS instead of Google's and making sure that I was running the game on fullscreen mode. Not sure what's the issue with Google's DNS but I hope that this would help you." Could try that or changing the dns cache to google and see if that works. Could also try resetting the dns cache that seems to work for some people : https://www.youtube.com/watch?v=8GmHmkY2QDE&t=1s Some people were having a similar issue in the new cod and deleting their config : https://www.reddit.com/r/modernwarfare/comments/eaqc4r/fix_for_error_lost_connection_to_hostserver/ Not sure if this would work for cod4 but if you wanted to try just go into your cod4 folder, the "players" folder, then the "profiles" folder and move everything in that folder to dekstop. Then when the game restarts create a new profile and see if that worked. If it didn't you can just delete the new profile in the same folder and move the other folders back from the desktop. Could also try a vpn. Costs about $5-$10 for a month and seems to fix some peoples connection issues. Nord do an unlimited 30 day money back guarantee and are reputable. Hope something works. Edited August 23, 2020 by Sharpe Link to comment Share on other sites More sharing options... Awards
Wild Fire Posted August 25, 2020 Member ID: 5468 Group: *** Clan Members Followers: 36 Topic Count: 19 Topics Per Day: 0.00 Content Count: 674 Content Per Day: 0.17 Reputation: 655 Achievement Points: 6445 Solved Content: 0 Days Won: 0 Joined: 02/04/13 Status: Offline Last Seen: Yesterday at 02:54 AM Birthday: 06/22/1965 Device: Android Author Share Posted August 25, 2020 Thanks for the suggestions Sharpe. I cleared my cache and still no luck. I'm on a MAC so couldn't even find my config file. But I just tried again tonight and all was good. So I hope the issue is behind me. Thanks again Ruggerxi, Sharpe and piglo 2 1 Link to comment Share on other sites More sharing options... Awards
Recommended Posts