Ruze is a veteran of the PC Beta, lived through the year one drought, survived the buy-to-play conversion, and has stepped foot in the hells known as Craglorn. He mained a nightlbade when nightblades weren't good, and has never worn a robe. He converted from PC during the console betas, and hasn't regretted it a moment since.
He'd rank ESO:TU (in it's current state) a 4.8 out of 5, loving the game almost entirely.
It started this morning for me, after leaving Cyrodyll. Had the Loading screen boss, so I force quit through task manager. After attempting to log on a few times afterwards, I thought it might just be the internet. After trying several hours later, I still cannot log in. I cannot even make a ticket for it so it can be fixed.
Start -> Run -> Type: cmd -> [Enter] C:\> tracert live-services.elderscrollsonline.com
So is this a problem with their ISP, mine?
This started two days ago, before that everything was fine. Havent changed anything in my system.
cr#.dlstx.ip.att.com xxx#.dlstx.ip.att.com -- Timeout --
I trried the tracert and it ended with
16 152 ms 144 ms 138 ms ggr3.dlstx.ip.att.net [12.122.138.25]
17 * 12.250.XX.XX reports: Destination net unreachable.
Trace complete.
I'm not sure what that actually means though.
For the 3 packets we sent, the times to get to '12.112.138.25' were:
152 miliseconds
144 miliseconds
138 miliseconds
It started this morning for me, after leaving Cyrodyll. Had the Loading screen boss, so I force quit through task manager. After attempting to log on a few times afterwards, I thought it might just be the internet. After trying several hours later, I still cannot log in. I cannot even make a ticket for it so it can be fixed.
For fun and entertainment, what's the output of (from a cmd shell (I'm assuming Windows here)):Start -> Run -> Type: cmd -> [Enter] C:\> tracert live-services.elderscrollsonline.com
If it goes through, it should (probably) end at an att.com route (XXXXX.dlstx.ip.att.com) before timing out (and timing out here is fine).
It's possible there's a route between you and the server down. But from other threads with a similar error seems unlikely.
But it would at least be something to rule out.
-M
SBR_QuorTek wrote: »well it say the reciever is not available when tracing, something has gotten really wrong or something.
Depechenova wrote: »Cant log in either am getting " Error 310 transfer failed " message.
I barely log in any more, just once a day to collect hireling mats. Now I cant even do that. Zenimax u truly suck butt.
HelpingHand wrote: »Depechenova wrote: »Cant log in either am getting " Error 310 transfer failed " message.
I barely log in any more, just once a day to collect hireling mats. Now I cant even do that. Zenimax u truly suck butt.
You do realize that error 310 means that you were not handed off properly due to large log in requests. You seriously need to just try logging in again, and you should get past it. ZOS doesn't suck butt as you state, they simply only have a log in server that can handle so many requests. I would wager this is related to the large amount of people attempting to log back in after something happened, or a large amount of people simply attempting to log in at the same time. A symptom of a large player base mind you, because this really is possible. You need to drink something to relax yourself.
We have moved this thread to the Customer Support section of the forums where it'll be more likely seen by veteran players who can help out.
I would wager not. I've been trying to login since yesterday. Quit telling people that they have no right to be annoyed by not getting what they've paid for.