Forum Discussion
5 Replies
- proxos6667 years agoHero+
What antivirus are you using ?
2018-04-09 15:22:31 INFO Login failure #-134 recorded
2018-04-09 15:22:31 ERROR Server did not properly respond to authenticate: -134Is generally seen with antivirus issue so first place to check
ESET - disable protocol settings
Kaperskey - disable scan secure/encrypted connections
Nortons (firewall) set exception to allow instead of auto
@proxos666
I'm using Avast Free atm. Don't think it regulates my firewall though--that's Windows Defender I think. Do you know the settings for that?I've tried adding the entire SWTOR folder to the FIleShield and WebShield exclusion list, to no avail.
Edit: I've uninstalled Avast. Still the same errors (I can login now, but then it still shows error 206 on the bottom left of the launcher). Reinstalled, no dice.
- proxos6667 years agoHero+
Ok it appears your dns is resolving strangely , have you ever altered your host file ?
can you try using 8.8.8.8 as a DNS server and see if any change
In parts of your log it resolves manifest and cdn-patch to the same IP address and that is incorrect
http://cdn-patch.swtor.com/patch/eualas/eualas_-1to0.solidpkg (156.154.176.215 156.154.175.215 )
http://manifest.swtor.com/patch/patcher2017.patchmanifest (156.154.176.215 156.154.175.215 )
Yet it gets it right once in the log
http://manifest.swtor.com/patch/patcher2017.patchmanifest (159.153.92.50 )
- Changed DNS and it works now. Thanks!
- EA_Kipling7 years ago
EA QV Team
@rex7034 Excellent, hope patching goes smoothly for you now!