![]() |
|
#2
|
|||
|
![]() same issue. also at&t. vpn also worked as workaround.
| ||
#3
|
|||
|
![]() Well since AT&T seems to be the common thread and there's obviously a significant amount of people unaffected and able to play it seems that we need some route to bring this to their attention to get it addressed.
Unfortunately I do not know the channels to use to do so. AenorVZ indicated the issue isn't limited to AT&T, but it must have something to do with the routing they are using or something since it is specifically affecting those of us with their service and not apparently the other 1400+ people logged in nightly. | ||
#4
|
|||
|
![]() I am having the same issue as everyone else here. I am unable to log in between about 6pm and 10 pm CST, otherwise it seems ok. signed Frustrated ATT internet guy
| ||
#5
|
|||
|
![]() Tethering is an option to try, even if ATT cell service maybe the issues are only with their internet service.
If ATT doesn't allow tethering you could try one of many apps that hide the tether usage from the cell provider.. I use EasyTether Pro, PDAnet is another good one I've used before.
__________________
< Knights Who Say Ni >
Qeynos questing and leveling (all quests nerfed) | Off the beaten path 24-40. | ||
#6
|
|||
|
![]() Others have reported tethering does in fact work, as does using a vpn in some cases.
While workarounds are great for the interim, I believe the majority of us are more interested in getting this corrected so that a such things are not needed. If anyone has a method of reporting this type of connectivity issue to AT&T it sounds like that is what we really need. The tech support I had on the phone was uninterested in the specifics of what I was having issues connecting to and was unwilling to escalate it further but perhaps I will try again. And in a sense I cannot blame them. In all likelihood nationwide this is probably only affecting a few hundred users at most and likely does not demand significant investment of time and resources for them to investigate further. | ||
#7
|
|||
|
![]() I AM NOT on AT&T and am having the issue, and it’s only happening to me at peak times. I’ve had no issue logging in or zoning during the day, when server pop is low. I know the server has seen an spike in population here lately, so I just thought it might be on P99’s end. Everything I’ve checked on my end seems to be fine, and I haven’t had any issues with any other sites/games.
| ||
#8
|
|||
|
![]() How can i get a vpn without getting scammed or a virus? I cant stand this anymore.
| ||
#9
|
|||
|
![]() I don't know if this will work for everyone, but I worked with the OP to try to narrow this down. The first clue we received was when I had him change the eqhost.txt file where it says Host=login.eqemulator.net:5998 to Host=160.72.227.52:5998
When that got him to server select with a populated server list, I suspected whatever DNS his IP was using was not resolving the P99 server correctly. So we followed this and had him set his DNS to the Google Public DNS 8.8.8.8 and 8.8.4.4: https://www.hellotech.com/guide/for/...er-windows-mac My understanding is that he has had significantly less issues, so it might be worth a try for some of you experiencing the same issue. Write down the DNS settings so you can revert back to default if it doesn't solve anything for you.
__________________
Another witty, informative, and/or retarded post by:
![]() "You know you done fucked up when Yendor gives you raid commentary." - Tiggles | ||
#10
|
|||
|
![]() I tried all of these things you mentioned previously, and while it seemed like it made a difference I think it was more or less just luck. The problem simply returned some time later. The issues seem intermittent and seem to correlate with server population but that may just be coincidence. I suspect it is just based on prime time heaviest traffic.
Unfortunately, while I initially had great success using VPN to get around the issue, even that has started to be affected by the same symptoms. My hope is the problem is getting worse and as a result may be easier for someone to find and correct the issue. | ||
![]() |
|
|