Unknown Error - possible fix, pls let me know if this helps.

raojalaeb17_ESO
okay just finished building new computer for my friend and finished installing teso (aphew took long enough with those 240++ windows updates -.- ) anyways, eso wasn't working at all because of unkown error, and i googled a bit about my isp and the connection i use and about teso and i found this, note that i am translating this from fin > eng so i apologise in advance if it seems a bit unclear.

I found this helpfull, after about 4 or 5 unknown errors and being stuck on requesting character load i did this and zone changes dont seem to get me stuck anymore, anyways, if people have the knowhow and the courage to try this out, i would really love to hear if it helps so maybe other people might get past the unknown erros and stucks and whatnot this might solve.

!Important note, Be absolutely sure you know what you are doing before attempting any of this, or get someone to do it for you if you do not have the necessary know how to revert these settings, or don't do it at all!
Unknown error issue seems to be happening when you log in or switch zone and ESO server changes one process ip adress, which isp eso connection doesn't react properly, either too slowly or it block the new connection and packets dont get trough, own client still trying to send packets. Everything works fine as long as eso server doesn't need to change ip address during gameplay.

Problem may be caused by game's new megaserver technology, basically client creates several (0-20) http connections to closest players who are nearby, i think that, that might messup ISP to think that someone is running a server or someone is sharing a torrent so they shut it down.

using windows firewall.

1. Open tcp ports 24100-24131, 24500-24507
2. flush dns in commandline with "ipconfig /flushdns"
3. shut down modem
4. go to your adapter settings and change your dns settigns from automatic to ones provided from your isp website and/or customer service.
5. disable and then enable your adapter
6. restart your modem.

no ipconfig /renew seems to be needed since the modem does that on restart.

*notes
** isp == internet service provider, if their website doesn't give you dns address for your adapter, try calling to their customer service, explain the situation and ask for a dns address.

Original post to people who know finnish: http://yhteiso.elisa.fi/t5/Mobiililaajakaistat/4G-LTE-NAT-ja-Elder-Scrolls-Online/td-p/355735
Edited by raojalaeb17_ESO on April 10, 2014 1:51AM
  • raojalaeb17_ESO
    bumb
  • raojalaeb17_ESO
    doesn't seem to have any real effect, only thing i have found helpfull is ipconfig /release and /renew in command line and repeat till it works.
  • raojalaeb17_ESO
    okay even the release renew doesn't have any effect unless it actually changes ip which it seems it doesn't always seem to do...
  • Avalon
    Avalon
    ✭✭✭✭✭
    Tried changing DNS, tried using obtain automatically, tried release/renew, tried flushdns, tried IPv6 instead, tried disabling heuristics and more, etc etc... I've even done a system restore figuring it may be something badly installed... after doing everything I can on my end, I am left with only one thing I can think of: Zenimax's end. They need to fix this, too many people from too many ISPs are having issues, the only possibility is with their end not ours.

    ZOS, get it fixed, your loyal and loving players are absolutely unable to play the game, and it is getting really old really fast. Fix it, then give us more time or something, because we've lost DAYS sitting here unable to play.
  • raojalaeb17_ESO
    its not in zenimax's end, i think its somewhere between, trace shows 14 steps from my computer to the megaserver in texas, that is if it gets in, sometimes it says destination net unreachable... i hear using a proxy works (i have my suspicions that even proxy can fail, all dependent on the trace) but the latency becomes a real issue then (like double or triple latency from the current 200 - 300 i already get) can't really do anything else than to wait zinemax's networking team to fix this up somehow, hopefully it will be soon.
Sign In or Register to comment.