Connection error 7:11:3:191:101 [merged]

#3 - July 23, 2013, 2:37 p.m.

Hi harris – What kind of troubleshooting have you tried already? Usually this error code is the result of packet loss or an issue with the route your connection is taking to reach the game servers. Sometimes this could also be conflicting applications or potentially even an issue with your modem or router. Not passing the buck here, just giving you a few ideas of what the issue could be. For a more solid investigation and explanation I’d recommend submitting a technical support ticket. You should receive a response from our guys fairly quickly

#6 - July 24, 2013, 4:45 p.m.

Thanks for the update!

Definitely let us know if the issue returns. Glad to hear everything is working smoothly, at least for now (fingers crossed).

#11 - July 30, 2013, 4:39 p.m.

Hi Belfast Bad Boy – If this is happening with only one character definitely submit a technical support ticket and we’ll try and see what’s going on there.
https://forum-en.guildwars2.com/forum/support/tech/How-to-Submit-a-Technical-Support-Ticket-2/first#post3957

#64 - July 30, 2014, 3:50 p.m.

I have merged three threads into this one, just to keep things together.

I’ll ask our Technical Support folks if they have any information to provide on this. I note at least one post saying that he or she had submitted a ticket and was asked to contact the ISP on their end. That may be the answer, but I’ll see if there’s more to share.

Thanks for your patience.

#70 - July 31, 2014, 3:46 p.m.

For anyone receiving these error codes or reporting similar issues, please submit a support ticket:
https://help.guildwars2.com/anonymous_requests/new

#83 - Aug. 2, 2014, 12:36 p.m.

Anyone who is still receiving these errors can you please post your region, ISP, and server? This will help us narrow down any commonalities much more quickly.

Also, feel free to post traceroutes – this helps as well!

Thanks everyone for your patience and understanding.

#206 - Aug. 4, 2014, 8:11 a.m.

Hey all,

Thank you for the providing the information Ashley had requested. We are continuing to look into this and I will post an update here as soon as I have one.

Thanks
- Matt

#268 - Aug. 4, 2014, 6:16 p.m.

UPDATE: This is very much a known issue and the matter is under investigation by several team members. We apologize for the time it has taken to get the sitaution resolved and we will keep working on it until things are back to normal.

FYI: The issue is not isolated to Guild Wars 2, but is also impacting other games.

We will update here in the forums when we know more , but at this time, it is not necessary to submit a ticket.

#288 - Aug. 5, 2014, 1:50 p.m.

Dazzoe.7234:

Hello, i know this sounds dumb and you all may have tried this, but i was having this issue and all i did to fix it was restart my router and bam its fixed. So for thoose who havent done this and havent thought about it. give it a whirl it worked for me.

This is always a good idea, and it takes just a minute or two! I am not implying that everyone experiencing this issue can solve the problem with a router or modem reset, but this is my “go to” step, and it’s really surprising how often it works!

Thanks for posting the suggestion, Dazzoe.

#289 - Aug. 5, 2014, 1:53 p.m.

ApolloKing.6023:

Any news today on this update Gaile?

For those still experiencing the 7:11:3:191:101 error, the team is still on the case. I’ll update the internal e-mail thread to see if there’s any news and will post here if we have any updates.

#295 - Aug. 5, 2014, 4:01 p.m.

UPDATE as of 05 August 2014:

• The Error 7:11:3:191:101 problem is a known issue and the matter is under investigation by several team members.
• The issue is not isolated to Guild Wars 2, but is also impacting other games.
• You do not need to submit a ticket at this time.
• You might want to reset your modem and/or router to see if that helps you. (That will not resolve the situation for those experiencing the referenced error, but could help players experiencing a different issue.
• We will try to update here in the forums when we know more , but we suggest you may wish to attempt to log in from time to time in case the matter has been resolved before we are able to update.

We apologize for the time it has taken to get the situation resolved and we will keep working on the problem until things are back to normal.

#347 - Aug. 6, 2014, 2:25 p.m.

Hey guys,

We’re still looking into this issue, but is there anyone that is still having issues with logging into specific characters still?

Edit: Just to add, it sounds like some of you are reporting very different issues. As it’s better for us to see exactly what’s going on, rather than piping up with a “me too,” the more information that each of you are able to provide in regards to this issue the better.

Thanks for your patience!

#352 - Aug. 6, 2014, 2:49 p.m.

Please note. We would like to know the following:

• Your ISP
• Your location (country and, if possible, general location within the country, such as state, region, etc.)
• Your territory or region: NA or EU
• Your Game World (such as Fort Aspenwood, Desolation, Arborstone, etc.)
• The full Error Code you are receiving. (A partial code will not aid the investigation.)
• The number of characters with the problem
• The map name(s) on which the character or characters are trying to load

Thank you for providing that information.

#386 - Aug. 6, 2014, 5:16 p.m.

mrgn.9183:

They have just sent an email which they say to login my account and try a few things with my permission and i ve said ok. Hope this is not a common thing and they really do something.

That’s a good thing, and thank you for giving permission. The programmers need to see exactly what’s taking place, so your help can be instrumental in the resolution of this issue.

Many thanks.

#458 - Aug. 7, 2014, 4:42 p.m.

Update: 7 August 2014

Testing has confirmed that for many players, resetting their modem may correct this issue. To be clear, this does not work for every player. However, if you would kindly give this a try, it may get things back to normal for you.

In the meantime, this issue still is under investigation and we hope to have it fully resolved soon. Thank you for your continued patience!

#680 - Aug. 11, 2014, 2:50 p.m.

Update 11 August 2014

The Connection Error 7:11:3:191:101 issue is still under review and will be corrected for everyone as soon as a fix is developed, tested, and implemented into the game. At this time, you should not submit a ticket because the matter will be corrected for all when the game is updated. We will be closing all existing tickets on this matter with a general update.

We apologize for this inconvenience and thank you for your understanding. (Please note our update of 7 August which suggested that for a few players, resetting their modem corrected the matter.)

#704 - Aug. 12, 2014, 5:39 p.m.

Update: 12 August 2014

Our programming team has developed some troubleshooting steps that we’d like a few players to try as part of the analysis and resolution process. What we’re going to do it grab a handful of existing tickets and send out a message that outlines the process, then await a response from those players who choose to help with the troubleshooting.

If you don’t get a request about troubleshooting today, no worries! We just need a handful of files and screenshots and we’ll be good, therefore we don’t need to reach out to everyone who is experiencing this issue. All players who have submitted tickets about this issue will get an e-mailed update today, but it’s covered in forums posts so those of you active on this thread already will have the latest in updates. I’ll provide more information as it becomes available.

Please note: I am posting this in the English-language forum only because the troubleshooting requests are going out in English-language tickets to expedite the process. But please be assured that we are keenly aware that this issue impacts players in many countries, and the resolution will help everyone.

We’ll update as we have more to share. Thanks.

#706 - Aug. 12, 2014, 7:36 p.m.

Kamata.5762:

That last update (believe it or not) actually fixed it for me.

That is very good news. Can you keep us updated over a bit of time? I’d like to know if the problem creeps up again for you or if it truly appears to be fully resolved.

Thanks for the note.

#709 - Aug. 12, 2014, 7:44 p.m.

zonic.5261:

Think that it was fixed for my wife aswell, will test it myself tonight, if after 2 hours I do not get a locking screen will repost here. Since the issue started I havent been able to play more than 30 minutes (while changing zones) without getting kicked out.

Furion.9850:

I just finished, Dragon’s Reach Part 2 with no disconnection as “yet”. Still have to check dungeons and fractals. So far its looking great. Usually when I move from one server map to another server map I will disconnect. This did not happen for Tequatl, which is a good sign to me Will post updates.

Crossing fingers here. Do keep us informed about this, and thanks for posting.

#751 - Aug. 18, 2014, 2:38 p.m.

Brother Grimm.5176:

Jigain.8231:

Comments such as “can’t even play for 5 minutes” and “dropping back to character select screen every 3-5 minutes” or “dc-ing every few minutes” hint at the respective issues being distinctively separate from the issue that the thread was created for.

I agree with the quote….I’m not discounting or in any way disregarding people posting here with connection issues, but these issues ARE not the same as the issue that appears to have been (mostly) addressed by the last patch. Characters getting STUCK at loading screens indefinitely with this thread title error message involved.

I get the disconnect error is the same, but that’s like diagnosing a car that wont start and lumping all the potential issues together as “related”. Some may be, but most can have no effect on the others (ex: out of fuel and a cracked distributor cap).

BTW, anyone having issues during their local peak times (early evening hours), might want to check with their ISP for potential throttling….yes, it could be an Anet issue, but if your ISP is messing with your bandwidth during peak hours (when the are MOST likely to do so), a simple conversation with them that includes the term “throttling” often clears the problem right up (even if they deny it or pretend they don’t know what you are talking about). At the very least, it’s worth a conversation with them.

This makes a lot of sense.

I’d like to suggest that those posting here do so only if they are getting the precise Error Code found in the subject line. In addition, if you are posting about a disconnection issue, the first thing we really need to know is the Error Code you are getting.