Maintenance for the week of June 17:
• PC/Mac: NA and EU megaservers for patch maintenance – June 17, 4:00AM EDT (8:00 UTC) - 9:00AM EDT (13:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – June 17, 10:00PM EDT (June 18, 2:00 UTC) - June 18, 5:00AM EDT (9:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – June 17, 10:00PM EDT (June 18, 2:00 UTC) - June 18, 5:00AM EDT (9:00 UTC)

"Login timeout"

n0de
n0de
Soul Shriven
After todays patch I seem to be getting a issue where everytime I try to login it gives me the error message "Login timeout" or "Error 301", I've tried all the suggested problem solvers to this cause, i.e, Re-installing, Repairing and the Game Consultant but no luck. I've posted several posts regarding this issue and decided to post it here just incase I'm being ignored due to the fact it's actually being posted in the wrong category. If I could get help with this without it being any of the suggestions previously stated above I would greatly appreciate it, thankyou.
  • Moonraker
    Moonraker
    ✭✭✭✭
    n0de wrote: »
    After todays patch I seem to be getting a issue where everytime I try to login it gives me the error message "Login timeout" or "Error 301", I've tried all the suggested problem solvers to this cause, i.e, Re-installing, Repairing and the Game Consultant but no luck. I've posted several posts regarding this issue and decided to post it here just incase I'm being ignored due to the fact it's actually being posted in the wrong category. If I could get help with this without it being any of the suggestions previously stated above I would greatly appreciate it, thankyou.
    Hi @n0de.

    The official Support kb article for this says:
    I AM GETTING A "LOGIN ERROR: ERROR 301" WHEN ATTEMPTING TO LOGIN TO THE GAME. WHAT SHOULD I DO?

    Updated 04/14/2014 04:03 AM Published 11/22/2013 06:32 PM

    This error is occurring due to the large volume of logins. The issue should be resolved relatively soon. This error could also be related to lobby crashes. In either case, we recommend attempting to log in to the game again after a period of around 10 minutes.

    Sometimes, firewalls can also interfere with logins. Try disabling or reducing the firewall, and then attempt to log in again.

    Players can also try logging out, resetting their modems, and then logging back in.
    First can you post details for your Mac including OS X version, Model etc.;

    Apple icon (top left of menu bar) > About This Mac > More info…

    Can you confirm what internet connection you have?
    Location (i.e. home, college) & is it wifi or ethernet cable connection to router?

    Have you tried shutting down your Mac, rebooting the router and trying again?

    Try a traceroute to the login server, easiest via Network Utility;

    /System/Library/CoreServices/Applications/Network Utility.app

    Select the address for whichever Megaserver you use;

    Europe = live-eu-services.elderscrollsonline.com

    NA = live-services.elderscrollsonline.com

    Post back if you are unsure how to do the traceroute or what it means. But basically it should show any issue between you and the ESO login server and that you can actually connect to it OK.

    Here are some things to try which are for these general errors, if it is not just the volume of logins currently:

    Disable OS X Firewall

    Also worth ensuring the OS X Firewall is switched off during download and that any router firewall is not blocking it in some way.

    System Preferences > Secuirty & Privacy > Firewall

    This is in OS X 10.9 Mavericks, It may be slightly different in other versions.

    Reset DNCP lease

    System Preferences > Network > Select the network you are connected to (indicated by green circle)> Click Advanced > Click Renew DHCP Lease

    Change your DNS

    Change your DNS settings to a public DNS server (non-ISP).

    I used Google: 8.8.8.8, 8.8.4.4

    On the Mac, to change the DNS server IP addresses go to:

    System Preferences > Network > Advanced… > DNS

    Note the existing ones usually automatically added by your ISP then change them for the Google ones of other you prefer. Remember to Apply changes after clicking OK when done.

    Uncheck Auto Proxy Discovery

    - Navigate to the System Preferences under the Apple Menu.
    - Open up Network in System Preferences. (Usually located in the third row, third icon.)
    - Make sure the network connection with a green dot next to it is selected.
    - Click the Advanced button in the lower right corner
    - From the drop down menu, click on Proxies.
    - In the "Select a protocol to configure" list
    - Uncheck "Auto Proxy Discovery”

    Good luck. if none of this helps, it may just be as it says and login queues. I am not sure how long you have had the issue for.
    Options
  • n0de
    n0de
    Soul Shriven
    Thanks for the reply, it was all working fine for me before the patch but as soon as it had launched after maintenance I had encountered this problem along with a good few people too, that's why I'm having a hard time believing it's anything to do with my mac. I currently did the Traceroute test you had suggested anyway just to clarify and these are the results I found -

    Traceroute has started…

    traceroute to live-services.elderscrollsonline.com (198.20.198.110), 64 hops max, 72 byte packets
    1 * * *
    2 10.34.56.1 (10.34.56.1) 11.619 ms 10.166 ms 7.885 ms
    3 watf-core-2b-ae6-713.network.virginmedia.net (80.3.1.165) 8.037 ms 7.375 ms 8.131 ms
    4 popl-bb-1b-ae1-0.network.virginmedia.net (62.253.175.94) 14.808 ms 9.057 ms 9.893 ms
    5 popl-bb-2a-ae2-0.network.virginmedia.net (62.254.42.89) 10.759 ms 9.036 ms 10.007 ms
    6 nrth-bb-2a-ae0-0.network.virginmedia.net (62.254.42.69) 74.044 ms 10.599 ms 11.729 ms
    7 nrth-bb-1c-ae0-0.network.virginmedia.net (62.254.42.134) 15.902 ms 14.688 ms 11.682 ms
    8 62.253.174.189 (62.253.174.189) 21.886 ms 21.296 ms 21.732 ms
    9 ae4.cr1.ams10.nl.above.net (64.125.32.73) 46.570 ms 32.532 ms 22.392 ms
    10 ae1.mpr3.lhr3.uk.above.net (64.125.27.221) 22.145 ms 21.588 ms 89.760 ms
    11 ae2.mpr2.lhr2.uk.above.net (64.125.22.74) 22.425 ms 22.346 ms 21.787 ms
    12 ge-3-3-0.mpr1.la5.us.above.net (64.125.26.37) 88.410 ms 89.340 ms 89.693 ms
    13 ae1.cr2.lga5.us.above.net (64.125.29.38) 87.859 ms 119.828 ms 93.799 ms
    14 * * *
    15 192.205.36.105 (192.205.36.105) 100.910 ms 100.640 ms 108.640 ms
    16 cr2.n54ny.ip.att.net (12.122.130.170) 134.299 ms 145.229 ms 131.973 ms
    17 cr2.wswdc.ip.att.net (12.122.3.38) 134.629 ms 163.103 ms 137.154 ms
    18 cr1.wswdc.ip.att.net (12.122.2.29) 135.196 ms 136.385 ms 135.441 ms
    19 cr2.dlstx.ip.att.net (12.122.28.174) 137.267 ms 136.918 ms 158.970 ms
    20 ggr3.dlstx.ip.att.net (12.122.138.25) 171.079 ms 131.759 ms 135.849 ms
    Moonraker wrote: »
    n0de wrote: »
    After todays patch I seem to be getting a issue where everytime I try to login it gives me the error message "Login timeout" or "Error 301", I've tried all the suggested problem solvers to this cause, i.e, Re-installing, Repairing and the Game Consultant but no luck. I've posted several posts regarding this issue and decided to post it here just incase I'm being ignored due to the fact it's actually being posted in the wrong category. If I could get help with this without it being any of the suggestions previously stated above I would greatly appreciate it, thankyou.
    Hi @n0de.

    The official Support kb article for this says:
    I AM GETTING A "LOGIN ERROR: ERROR 301" WHEN ATTEMPTING TO LOGIN TO THE GAME. WHAT SHOULD I DO?

    Updated 04/14/2014 04:03 AM Published 11/22/2013 06:32 PM

    This error is occurring due to the large volume of logins. The issue should be resolved relatively soon. This error could also be related to lobby crashes. In either case, we recommend attempting to log in to the game again after a period of around 10 minutes.

    Sometimes, firewalls can also interfere with logins. Try disabling or reducing the firewall, and then attempt to log in again.

    Players can also try logging out, resetting their modems, and then logging back in.
    First can you post details for your Mac including OS X version, Model etc.;

    Apple icon (top left of menu bar) > About This Mac > More info…

    Can you confirm what internet connection you have?
    Location (i.e. home, college) & is it wifi or ethernet cable connection to router?

    Have you tried shutting down your Mac, rebooting the router and trying again?

    Try a traceroute to the login server, easiest via Network Utility;

    /System/Library/CoreServices/Applications/Network Utility.app

    Select the address for whichever Megaserver you use;

    Europe = live-eu-services.elderscrollsonline.com

    NA = live-services.elderscrollsonline.com

    Post back if you are unsure how to do the traceroute or what it means. But basically it should show any issue between you and the ESO login server and that you can actually connect to it OK.

    Here are some things to try which are for these general errors, if it is not just the volume of logins currently:

    Disable OS X Firewall

    Also worth ensuring the OS X Firewall is switched off during download and that any router firewall is not blocking it in some way.

    System Preferences > Secuirty & Privacy > Firewall

    This is in OS X 10.9 Mavericks, It may be slightly different in other versions.

    Reset DNCP lease

    System Preferences > Network > Select the network you are connected to (indicated by green circle)> Click Advanced > Click Renew DHCP Lease

    Change your DNS

    Change your DNS settings to a public DNS server (non-ISP).

    I used Google: 8.8.8.8, 8.8.4.4

    On the Mac, to change the DNS server IP addresses go to:

    System Preferences > Network > Advanced… > DNS

    Note the existing ones usually automatically added by your ISP then change them for the Google ones of other you prefer. Remember to Apply changes after clicking OK when done.

    Uncheck Auto Proxy Discovery

    - Navigate to the System Preferences under the Apple Menu.
    - Open up Network in System Preferences. (Usually located in the third row, third icon.)
    - Make sure the network connection with a green dot next to it is selected.
    - Click the Advanced button in the lower right corner
    - From the drop down menu, click on Proxies.
    - In the "Select a protocol to configure" list
    - Uncheck "Auto Proxy Discovery”

    Good luck. if none of this helps, it may just be as it says and login queues. I am not sure how long you have had the issue for.

    Edited by n0de on April 16, 2014 1:10AM
    Options
  • n0de
    n0de
    Soul Shriven
    Processor 2.7 GHz Intel Core i5 Memory 8 GB 1600 MHz DDR3 Graphics NVIDIA GeForce GT 640M 512 MB Software OS X 10.9.2 (13C64)
    Options
  • Moonraker
    Moonraker
    ✭✭✭✭
    n0de wrote: »
    Thanks for the reply, it was all working fine for me before the patch but as soon as it had launched after maintenance I had encountered this problem along with a good few people too, that's why I'm having a hard time believing it's anything to do with my mac. I currently did the Traceroute test you had suggested anyway just to clarify and these are the results I found -

    Traceroute has started…

    traceroute to live-services.elderscrollsonline.com (198.20.198.110), 64 hops max, 72 byte packets
    1 * * *
    2 10.34.56.1 (10.34.56.1) 11.619 ms 10.166 ms 7.885 ms
    3 watf-core-2b-ae6-713.network.virginmedia.net (80.3.1.165) 8.037 ms 7.375 ms 8.131 ms
    4 popl-bb-1b-ae1-0.network.virginmedia.net (62.253.175.94) 14.808 ms 9.057 ms 9.893 ms
    5 popl-bb-2a-ae2-0.network.virginmedia.net (62.254.42.89) 10.759 ms 9.036 ms 10.007 ms
    6 nrth-bb-2a-ae0-0.network.virginmedia.net (62.254.42.69) 74.044 ms 10.599 ms 11.729 ms
    7 nrth-bb-1c-ae0-0.network.virginmedia.net (62.254.42.134) 15.902 ms 14.688 ms 11.682 ms
    8 62.253.174.189 (62.253.174.189) 21.886 ms 21.296 ms 21.732 ms
    9 ae4.cr1.ams10.nl.above.net (64.125.32.73) 46.570 ms 32.532 ms 22.392 ms
    10 ae1.mpr3.lhr3.uk.above.net (64.125.27.221) 22.145 ms 21.588 ms 89.760 ms
    11 ae2.mpr2.lhr2.uk.above.net (64.125.22.74) 22.425 ms 22.346 ms 21.787 ms
    12 ge-3-3-0.mpr1.la5.us.above.net (64.125.26.37) 88.410 ms 89.340 ms 89.693 ms
    13 ae1.cr2.lga5.us.above.net (64.125.29.38) 87.859 ms 119.828 ms 93.799 ms
    14 * * *
    15 192.205.36.105 (192.205.36.105) 100.910 ms 100.640 ms 108.640 ms
    16 cr2.n54ny.ip.att.net (12.122.130.170) 134.299 ms 145.229 ms 131.973 ms
    17 cr2.wswdc.ip.att.net (12.122.3.38) 134.629 ms 163.103 ms 137.154 ms
    18 cr1.wswdc.ip.att.net (12.122.2.29) 135.196 ms 136.385 ms 135.441 ms
    19 cr2.dlstx.ip.att.net (12.122.28.174) 137.267 ms 136.918 ms 158.970 ms
    20 ggr3.dlstx.ip.att.net (12.122.138.25) 171.079 ms 131.759 ms 135.849 ms
    Hop 14 of the traceroute shows it's probably just not responding to traceroute ping. Seems OK.
    You chose the North America login server is that becuase you are connecting to that rather than the Europe server?

    Options
  • Moonraker
    Moonraker
    ✭✭✭✭
    n0de wrote: »
    Processor 2.7 GHz Intel Core i5 Memory 8 GB 1600 MHz DDR3 Graphics NVIDIA GeForce GT 640M 512 MB Software OS X 10.9.2 (13C64)
    OK, just wanted to check mostly the OS X version which is fine.

    It's either just busy (as support article) or you can try the other suggestions. One thing from above traceroute was to know if you are using the NA install and connecting to the NA Megaserver (which tends to be busier and have more issues at peak times) or the EU install connecting to the Europe Megaserver? It should have set it correctly if you selected the right location using the Install of the Launcher.
    Edited by Moonraker on April 16, 2014 1:42AM
    Options
  • n0de
    n0de
    Soul Shriven
    No that's just purely due to my friends being on the NA server apposed to the EU server as they are American. So what does that actually mean? It's not a problem on my end? and if so how do I get my launcher to update this patch?
    Options
  • Moonraker
    Moonraker
    ✭✭✭✭
    n0de wrote: »
    No that's just purely due to my friends being on the NA server apposed to the EU server as they are American. So what does that actually mean? It's not a problem on my end? and if so how do I get my launcher to update this patch?
    As long as you have the NA install and it's selected in Launcher and that updated correctly to version

    Like I said, you can choice to wait and see if it is just server congestion/ login queue which they say. Or you can try the suggested fixes to see if there is another issue.

    If it worked fine before usually it is probably just congestion. But sometimes error occur because of something during the patching or on the Mac. There is no way to know for sure. The choice really is yours.

    I would probably just try every 10-20 minutes or so and see it is connects as usual. If it's still giving the error tomorrow try the suggestions.
    Edited by Moonraker on April 16, 2014 1:48AM
    Options
  • n0de
    n0de
    Soul Shriven
    Although my problem hasn't been solved I really appreciate you taking your time out to try your best to help me with a solution, I just wish there were many more of you around :) Thankyou kindly.
    Options
  • Moonraker
    Moonraker
    ✭✭✭✭
    n0de wrote: »
    Although my problem hasn't been solved I really appreciate you taking your time out to try your best to help me with a solution, I just wish there were many more of you around :) Thankyou kindly.
    No problem @n0de. Just hope it either clears up for you or if those suggestions don't help post back.

    Good luck with it.
    Options
  • ethyreal
    ethyreal
    Its funny I get this same error after the patch also. yet when I boot into bootcamp on the same machine it loads up just fine.
    Options
  • CrypticPower
    I'm having same issue. it is not PC related, I checked on 3 different machines. It MAY be related to either the ISP OR your router that needs to be rebooted, I did both (releasing and renewing IP address and restarting router with no success) so sounds like an Account or Login issue with the Game. Please advise, thanks.
    Options
  • Moonraker
    Moonraker
    ✭✭✭✭
    ethyreal wrote: »
    Its funny I get this same error after the patch also. yet when I boot into bootcamp on the same machine it loads up just fine.
    Try the suggestions posted above. if it works on PC via Bootcamp on same computer then it's more likely a setting or old IP address on the Mac cache etc.
    Options
  • Moonraker
    Moonraker
    ✭✭✭✭
    One thing I did not have on that list from last night was to flush the DNC Cache:

    Reset the DNS Cache

    Step 1: Open the Terminal

    Navigate to Applications -> Utilities -> Terminal

    Step 2: Flush DNS - Type the following command and hit enter.

    Mac OSX 10.9 (Mavericks): dscacheutil -flushcache;sudo killall -HUP mDNSResponder

    Mac OSX 10.7 & 10.8 (Lions) : sudo killall -HUP mDNSResponder

    Press Return and enter password at prompt. Then try. or reboot then try.
    Options
Sign In or Register to comment.