Just to let people know, in my expiriance, if you are on a University network, you may have problems playing in the day because some universities close off ports and restrict access to others during the day depending on usage and bandwidth availabilities. If you come to your dorm room and you are sitting there trying to zone and guild wars logs out or never zones, this may be the reason.
Only ways I know to remedy this are to hope your network administrator gets lazy about ports or to play at night, usually full fledged file transfer is allowed and encouraged at night. This is when the best time to play is, usually from 8 or 9 p.m. untill 7 or 8 a.m. at least thats how it is at my university.
If anyone has other info or knows how to circumvent this PLEASE post.
Slow ports at Colleges
Amsterdam
EternalTempest
Unless you know an admin or you exploit some hole in there network (which will most likely get you in a heap of trouble) not much you can do.
They could also have what is known as packet "shaping" where your bandwidth is slowed down (or certain ports, like streaming music, audio, or common game ports) based on how busy there network is. If there reaching there bandwidth limit, things like games start getting slowed down so mission critical still work and function.
They could also have what is known as packet "shaping" where your bandwidth is slowed down (or certain ports, like streaming music, audio, or common game ports) based on how busy there network is. If there reaching there bandwidth limit, things like games start getting slowed down so mission critical still work and function.
swaaye
P2P is mainly to blame honestly. People just blast that school network. Napster utterly destoryed our school LAN back in the day.
saab
I think the network admin here may have completely disabled the ports needed to connect to anet. I haven't even been able to get past the connecting screen and after a few minutes I'll get an err=58.
EternalTempest
Quote:
|
Originally Posted by saab
I think the network admin here may have completely disabled the ports needed to connect to anet. I haven't even been able to get past the connecting screen and after a few minutes I'll get an err=58.
|
ftp://ftp.guildwars.com/diag/netinfotool_allos_gw.exe
Narada
If speed is only an issue on certain ports, perhaps you could try using a port tunneler?
saab
Quote:
|
Originally Posted by EternalTempest
Here's a utility from Anet to check (it will produce a log file)
ftp://ftp.guildwars.com/diag/netinfotool_allos_gw.exe |
Code:
############### Beginning: Updaters & Login Port Tests. Check: 6112 auth1.arenanetworks.com (206.127.148.88) --> problem connecting to "206.127.148.88", port 80: Unknown error Check: 6112 auth1.arenanetworks.com (206.127.148.109) --> problem connecting to "206.127.148.109", port 80: Unknown error Check: 6112 auth1.arenanetworks.com (206.127.148.45) --> problem connecting to "206.127.148.45", port 80: Unknown error Check: 6112 auth1.arenanetworks.com (206.127.148.48) --> problem connecting to "206.127.148.48", port 80: Unknown error Check: 6112 auth1.arenanetworks.com (206.127.148.46) --> problem connecting to "206.127.148.46", port 80: Unknown error Check: 6112 auth1.arenanetworks.com (206.127.148.92) --> problem connecting to "206.127.148.92", port 80: Unknown error Check: 6112 file1.arenanetworks.com (216.107.241.21) --> successful Check: 6112 file1.arenanetworks.com (216.107.241.20) --> successful Check: 6112 file1.arenanetworks.com (206.127.148.41) --> problem connecting to "206.127.148.41", port 80: Unknown error Check: 80 diag.arenanetworks.com (206.127.148.93) --> problem connecting to "206.127.148.93", port 80: Unknown error Check: 80 diag.arenanetworks.com (206.127.146.41) --> successful Check: 80 diag.arenanetworks.com (206.127.146.55) --> successful Check: 80 diag.arenanetworks.com (222.231.12.55) --> successful Check: 80 diag.arenanetworks.com (222.231.12.41) --> successful Check: 80 diag.arenanetworks.com (206.127.148.47) --> problem connecting to "206.127.148.47", port 80: Unknown error Check: 6112 diag.arenanetworks.com (206.127.148.93) --> problem connecting to "206.127.148.93", port 6112: Unknown error Check: 6112 diag.arenanetworks.com (206.127.146.41) --> successful Check: 6112 diag.arenanetworks.com (206.127.146.55) --> successful Check: 6112 diag.arenanetworks.com (222.231.12.55) --> successful Check: 6112 diag.arenanetworks.com (222.231.12.41) --> successful Check: 6112 diag.arenanetworks.com (206.127.148.47) --> problem connecting to "206.127.148.47", port 6112: Unknown error