Things that cause Error7

The massive error 7 complaints has caused me to create this thread to explain some of the reasons for error7ing.

These are the most obvious reasons:

1) WireLess Network - I can't stress the fact of how many people are on a wireless network and have no idea that it is the main reason for their error7. When you lose signal strenght you WILL error7. I myself have been suffering through this problem because im staying at a wireless networked home for the summer and my GW out of nowhere error7s my total error7 count on a wired network has been 6 from may 6, 2005 to june 3, 2006, but on my wireless network sometimes I error7 4 times in one day.

2) Port issues - not many are so knowledgable of how to actually open your ports on your router or firewall. If left default your router ip that you can type into your browser to connect to your router is 192.168.1.1 or 192.168.0.1 . The default username is admin and sometimes the default password is left blank or it may be admin again. Check your router manual for the IP address to your router as well as the default username and password to connect. Once your in it is very simple to open the port for guild wars. Guild Wars needs port 80 and port 6112 to be open. Check your firewall settings and open the same ports or create a exception for guild wars.

3) Uploading - Do not upload at maximum speed while you are torrenting or any other fileshare you may use. As your upload reaches its ISP limit your downspeed slows down and if it remains that way an error7 is imminent not to mention some severe lag.

That's all I can think of right now if there is any other reasons for error7 or if you just want to rant about your error7s because they have no explaination then say so ^_^. Please add to the "Things that cause error7" list.

I've had 2 error 7's and they all occurred during the release of factions and none of these reasons apply to me.

Are you certain about port 80 ? I only ever opened 6112 on my machine (port 80 drops), and Guild Wars runs just fine.

I've had no disconnects in months and months <can't even remember the last time> and have done nothing to my settings. AT&T DSL in AZ, not on wireless, no filesharing going on, never had to mess with ports or any other settings.

port 80 is the port used for the hyper text transfer protocol (HTTP) which is needed for you to surf the web. Under normal coniditions in home PCs it is open by default. So you do not need to manually open it.

You can open all ports and leave it to your software firewall by making your pc on your network the DMZ (Demiliterized Zone).

You know, aside from those three things (which, like others, do not apply to me,) it could be a very real problem that exists for players that have never had an issue before.

You know, just a suggestion.

The error 7's that are being experienced are due to strain on arena.nets system.

You can easily check this by alt tabbing out of the game as you notice you are lagging, you'll see that arena net is no longer streaming the information to you. Which in turn causes you to be dropped with the error 007.

In the big picture it's probably due to a change, new equiment during the last maintainence update.

There are at least 2 distinct types of err7:
1] You get lag and can't move; client finally realizes it has lost connection.

2] You change zones or similar, and INSTANTLY get err7; no lag involved.

#2 is almost certainly ANet, #1 could be anything.

on my wireless network my error7s are the first type where you lag up and your skills dont go through. Sometimes it pulls through after 3 or so seconds of jamming up but most of the time it freezes for approximately 6 seconds then you get a error7 message

Speaking of ports, I have reason to believe that some of the servers are now ignoring port 80 and ICMP (spelling? the 'ping packets') requests and only respond to things on port 6112.

I recently did an install of GW as a vain attempt to get it to work when it surprisingly got through. After testing a bit more, I found that my older version of GW was requesting on port 80 (even after repairs and updates), while a newly installed or downloaded version of GW (after updates) will request on port 6112. These servers won't even respond to pings, but are connectable.

So, I have reason to believe that somewhere along the line, people's copies of GW got messed by an update, and subsequent updates aren't fixing the problem for some reason; the .dat files become persistent in using port 80 to communicate to GW.

Question, can these 07 errors cause your modem to go offline
briefly and then re-connect on-line ?? I have been having alot
of this happening lately, and I am not sure if it is just Comcast
dropping off or the game causing it ??? On a wireless network,
but the modem is going off-line......

thx for any help....