Maintenance for the week of December 15:
• PC/Mac: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• Xbox: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PC/Mac: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• Xbox: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
Game consultant ping unpingable IP addresses
So when you have a connection issue, customer support ask you to create a game consultant. Fine. It's normal.
Then they check the game consultant and tell you "you have an issue with your connection, the game consultant show a failed ping":
Pinging launcher.bethesda.net [54.217.220.128] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
And then you loose hours and days trying to address an issue that doesn't exist, rather than trying other solutions that may solve the problem.
After 3 months they didn't realize yet the issue is that Zenimax firewalls block that ping?
Seriously ?
Please either remove this test, or replace it with a connection test to http port 80 or change your firewall rule to allow ping.
Then they check the game consultant and tell you "you have an issue with your connection, the game consultant show a failed ping":
Pinging launcher.bethesda.net [54.217.220.128] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
And then you loose hours and days trying to address an issue that doesn't exist, rather than trying other solutions that may solve the problem.
After 3 months they didn't realize yet the issue is that Zenimax firewalls block that ping?
Seriously ?
Please either remove this test, or replace it with a connection test to http port 80 or change your firewall rule to allow ping.
0
-
fromtesonlineb16_ESO✭✭✭✭✭
✭You're sure it was ZOS endpoint that was dropping pings I assume.
LOL, sorry, but it's amusing and so in-keeping with their other actions that a programmer wrote a program that did something without checking with those responsible to find out it wouldn't work.0 -
Yes sorry, forgot to mention that, but I tested this from 8 different Internet Service Providers in 4 different European country, without any firewall that could block the ping.
(but cannot test from other continents).0 -
Seravi✭✭✭✭✭Request timed out here in the US on that IP as well.Edited by Seravi on June 26, 2014 11:25AM0 -
Dolnor✭✭✭I've tried pinging all the addresses that the Launcher uses when downloading updates and all time out. It looks like the connections are monitored and ignore pings since they are configured to stream as much content one-way only...probably for efficiency.
TQQdles™0