Servers Are Undergoing Maintenance...try Again Later.
#141
Posted 15 July 2014 - 04:01 PM
#142
Posted 15 July 2014 - 04:02 PM
Date: Tue Jul 15 23:59:29 2014
DNS IP: 77.96.4.65 (GB) (AS5089 Virgin Media Limited)
Client IP: 92.233.170.205 (GB) (AS5462 Virgin Media Limited)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Cookies: no
Edge IP: 88.221.87.147 88.221.87.143
Latency: 23ms
Speed: 1647.8Mbps
I do not have a clue how to do the Google DNS thingy, I tried it and it failed. I understand about as much about setting these kind of things up as...
Switch on pc----Check
Click MWO icon----Check
OMFG it is not working WTF-----Check
Sit staring at screen thinking were the heck are my kids when I need them????
Then realising ooh well I guess some Mech pilots get a break tonight from me Ripping them on the battlefield.
Oh and if possible could you fix something by later today as I would like to put a few inner-sphere mechs on the scrapheap.
#143
Posted 15 July 2014 - 04:02 PM
#144
Posted 15 July 2014 - 04:04 PM
Bulvar Jorgensson, on 15 July 2014 - 04:02 PM, said:
Date: Tue Jul 15 23:59:29 2014
DNS IP: 77.96.4.65 (GB) (AS5089 Virgin Media Limited)
Client IP: 92.233.170.205 (GB) (AS5462 Virgin Media Limited)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Cookies: no
Edge IP: 88.221.87.147 88.221.87.143
Latency: 23ms
Speed: 1647.8Mbps
I do not have a clue how to do the Google DNS thingy, I tried it and it failed. I understand about as much about setting these kind of things up as...
Switch on pc----Check
Click MWO icon----Check
OMFG it is not working WTF-----Check
Sit staring at screen thinking were the heck are my kids when I need them????
Then realising ooh well I guess some Mech pilots get a break tonight from me Ripping them on the battlefield.
Oh and if possible could you fix something by later today as I would like to put a few inner-sphere mechs on the scrapheap.
Try a good old fashioned reboot of your computer and router; this has solves certain issues.
#145
Posted 15 July 2014 - 04:04 PM
Kell Commander, on 15 July 2014 - 04:01 PM, said:
I don't wanna make light of your situation....but a router cycle sounds rad. Wifi on the go! Bet they'd love you at bike raves. Online presence everywhere.
#146
Posted 15 July 2014 - 04:06 PM
Zimmy, on 15 July 2014 - 03:57 PM, said:
They havn't broken anything, DNS issues are an internet related issue. It's like a company releasing a new product, which you ordered, and the mail company screws up.
#147
Posted 15 July 2014 - 04:10 PM
WarGanisM, on 15 July 2014 - 04:06 PM, said:
They havn't broken anything, DNS issues are an internet related issue. It's like a company releasing a new product, which you ordered, and the mail company screws up.
Correct, and we have thousands of users in game and playing. We were able to see that it's something with Verizon and Virgin nodes; I'm working with them to get a resolution to this issue once and for all.
#148
Posted 15 July 2014 - 04:10 PM
Date: Wed Jul 16 00:10:18 2014
DNS IP: 77.96.6.193 (GB) (AS5089 Virgin Media Limited)
Client IP: 82.34.140.172 (GB) (AS5089 Virgin Media Limited)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0
Cookies: yes
Edge IP: 88.221.87.131 88.221.87.127
Latency: 14ms
Speed: 19.4Mbps
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\DG>nslookup patcher.mwomercs.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 23.63.98.18
23.63.98.26
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net
C:\Users\DG>tracert patcher.mwomercs.com
Tracing route to a1982.d.akamai.net [62.252.168.67]
over a maximum of 30 hops:
1 6 ms 6 ms 5 ms 10.97.148.1
2 5 ms 6 ms 5 ms gate-core-2a-ae6-608.network.virginmedia.net [80
.0.145.17]
3 8 ms 7 ms 7 ms leed-bb-1c-ae7-0.network.virginmedia.net [213.10
5.159.165]
4 8 ms 9 ms 9 ms seac-icdn-1-ae0-0.network.virginmedia.net [62.25
3.174.230]
5 9 ms 9 ms 9 ms m67-mp1-cvx1b.lan.ntl.com [62.252.168.67]
Trace complete.
C:\Users\DG>tracert static.mwomercs.com
Tracing route to e5782.g.akamaiedge.net [2.17.26.41]
over a maximum of 30 hops:
1 8 ms 7 ms 6 ms 10.97.148.1
2 6 ms 6 ms 5 ms gate-core-2b-ae6-709.network.virginmedia.net [80
.0.145.149]
3 16 ms 14 ms 14 ms manc-bb-1c-ae10-0.network.virginmedia.net [213.1
05.159.169]
4 19 ms 20 ms 18 ms manc-bb-2a-ae2-0.network.virginmedia.net [62.254
.42.113]
5 15 ms 14 ms 21 ms manc-bb-1d-ae0-0.network.virginmedia.net [62.254
.42.118]
6 14 ms 14 ms 20 ms tcma-ic-2-ae0-0.network.virginmedia.net [62.253.
174.178]
7 14 ms 17 ms 15 ms 170-14-250-212.static.virginm.net [212.250.14.17
0]
8 15 ms 13 ms 16 ms 2.17.26.41
Trace complete.
Edited by Belphegore, 15 July 2014 - 04:13 PM.
#149
Posted 15 July 2014 - 04:12 PM
daemur, on 15 July 2014 - 10:55 AM, said:
Fixed mine! thanks!
#150
Posted 15 July 2014 - 04:15 PM
So it sounds like this will eventually get resolved without me having to do anything? I'd rather not switch to google dns and I'd also rather not submit a ticket if you guys are already aware and working with those Verizon knuckleheads to get the issue resolved...
Edited by TitanLord, 15 July 2014 - 04:15 PM.
#151
Posted 15 July 2014 - 04:16 PM
#153
Posted 15 July 2014 - 04:19 PM
#154
Posted 15 July 2014 - 04:19 PM
- Power down your computer
- Unplug your modem (and router, if that's a separate device)
- Wait 1 minute
- Plug in your modem (wait until the lights indicate it's online)
- Plug in your router (again, this is only required if it's a separate device, and, again, wait for it to come online)
- Once everything above is back online, then power up your computer again.
#155
Posted 15 July 2014 - 04:22 PM
I know this is going to sound kind of mean but....do you not think I have tried doing that at least a dozen times over the course of this evening.
I shall wait until one of my tech savvy kids turns up tomorrow and try the Google work round, with the hope PGI and Virgin media can work out what the heck the issue is before I log back in.
In the mean time....I wonder if my premium time has been frozen (muhahahahah, not)
#156
Posted 15 July 2014 - 04:24 PM
Belphegore, on 15 July 2014 - 04:10 PM, said:
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\DG>nslookup patcher.mwomercs.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
Non-authoritative answer:
Name: a1982.d.akamai.net
Addresses: 23.63.98.18
23.63.98.26
Aliases: patcher.mwomercs.com
patcher.mwomercs.com.edgesuite.net
C:\Users\DG>tracert patcher.mwomercs.com
Tracing route to a1982.d.akamai.net [62.252.168.67]
over a maximum of 30 hops:
1 6 ms 6 ms 5 ms 10.97.148.1
2 5 ms 6 ms 5 ms gate-core-2a-ae6-608.network.virginmedia.net [80
.0.145.17]
3 8 ms 7 ms 7 ms leed-bb-1c-ae7-0.network.virginmedia.net [213.10
5.159.165]
4 8 ms 9 ms 9 ms seac-icdn-1-ae0-0.network.virginmedia.net [62.25
3.174.230]
5 9 ms 9 ms 9 ms m67-mp1-cvx1b.lan.ntl.com [62.252.168.67]
Trace complete.
C:\Users\DG>tracert static.mwomercs.com
Tracing route to e5782.g.akamaiedge.net [2.17.26.41]
over a maximum of 30 hops:
1 8 ms 7 ms 6 ms 10.97.148.1
2 6 ms 6 ms 5 ms gate-core-2b-ae6-709.network.virginmedia.net [80
.0.145.149]
3 16 ms 14 ms 14 ms manc-bb-1c-ae10-0.network.virginmedia.net [213.1
05.159.169]
4 19 ms 20 ms 18 ms manc-bb-2a-ae2-0.network.virginmedia.net [62.254
.42.113]
5 15 ms 14 ms 21 ms manc-bb-1d-ae0-0.network.virginmedia.net [62.254
.42.118]
6 14 ms 14 ms 20 ms tcma-ic-2-ae0-0.network.virginmedia.net [62.253.
174.178]
7 14 ms 17 ms 15 ms 170-14-250-212.static.virginm.net [212.250.14.17
0]
8 15 ms 13 ms 16 ms 2.17.26.41
Trace complete.
If you look carefully, the Virgin's DNS servers say to hit 23.63.98.18, which is owned by Akamai (our CDN), HOWEVER if you look at your traceroute to the patcher, it final IP it hits is 62.252.168.67 which is owned by Virgin Media Ltd and not Akamai. So Virgin's servers is responding to patcher.mwomercs.com.
#157
Posted 15 July 2014 - 04:25 PM
Bulvar Jorgensson, on 15 July 2014 - 04:22 PM, said:
No, I'm not underestimating anyone, I just wanted to be explicitly clear that power cycling your router without turning off your computer sometimes doesn't do the trick (I've been through that myself). Sorry if I came across as condescending, but if there's anyone that benefits from the abundance of instruction, then it's worth it.
#158
Posted 15 July 2014 - 04:27 PM
For the record, i'm from North Jeresy (near NYC) and have Verizion Fios. so.... i guess there's just some issues somewhere.
Cheers to you Mr. Kyle, and OP
#159
Posted 15 July 2014 - 04:28 PM
Can't get into the Patcher
DNS Flush didn't work
Only thing that worked was the Google public DNS (Which I don't like)
Whats the ETA on a fix? this is the first time in many many years I have seen this.
#160
Posted 15 July 2014 - 04:30 PM
Krist Smith, on 15 July 2014 - 04:04 PM, said:
I actually started thinking about a way to make that work lol. Contacts on the wheels could use the friction to charge a battery to provide power. Not 100% convinced on the profitability though.
6 user(s) are reading this topic
0 members, 6 guests, 0 anonymous users