{WoW} New Game/Patch -> Doesn't Log InFollow

-----
Purchased a new copy of WoW < 24h ago; installed, patched, executes smoothly, even giving me Server Alerts. However, all attempts to log in time out, and I can't post this on the TS Forum because I don't have a character...because all attempts to log in time out. :\
-----
I've tried a myriad of suggestions from disabling Windows and AVAST Firewalls to enabling DMZ but nothing seems to connect to WoW while the rest of the internets (web sites, poker servers, FFXI [2 months ago]) give me no hassle.

Ran Ad-Aware in Safe w/o Networking and cleared everything out; currently running an Avast Thorough Scan, but I don't expect to see any viruses.
-----
Hardware:
Processor type/speed: Intel P4 2.0 GHz
Total/Free hard drive space: 74.4 GB/13.2 GB
Amount of Ram: 512 MB
Video card type: GeForce4 MX 420
Operating system: Windows XP (Service Pack 2)
Computer model number (if it has one): DELL Dimension 4500
Frequency of problem: Continuous/Current
---
The Connection:
Linksys Wireless Adapter - Drivers 'sorta' updated: When I installed this on XP I had to utilize some backdoor trickery. (See the 2nd review here: http://cannotlinkto.com/5r7jp)
For the latest drivers I stopped the WUSB11, cut-n-pasted all new drivers into the applicable Linksys folder, and restarted the WUSB11. No new problems, but doesn't fix WoW connections.
-----
Routing Computer:
Linksys Router BEFW11S4 - Firmware 1.50.14 (newest)
Motorola Surfboard Modem (4000s, can't check right now)
ISP: Comcast Digital Cable
I have to check on the Surfboard modem but a couple of tests (netStat) as well as the readouts on downstream/upstream give no indiciation that there were flagrant modem errors to speak of.
-----
"Suggestions"
Tracert:



1 * * * Request timed out.
2 12 ms 11 ms 12 ms
3 15 ms 10 ms 10 ms
4 12 ms 11 ms 12 ms
5 13 ms 14 ms 14 ms 12.118.149.5
6 15 ms 17 ms 14 ms tbr1-p010501.n54ny.ip.att.net [12.123.3.10]
7 36 ms 38 ms 37 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.2]
8 78 ms 77 ms 76 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
9 77 ms 77 ms 76 ms gbr6-p100.sffca.ip.att.net [12.122.11.78]
10 91 ms 77 ms 77 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
11 85 ms 85 ms 86 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255.254]
12 85 ms 86 ms 85 ms mdf1-bi8k-2-eth-1-2.lax1.attens.net [12.129.192.46]
13 * * * Request timed out.
14 * * * Request timed out.
...
30 * * * Request timed out.

---
NETSTAT = C:\>netstat
Active Connections were all Established

-s -p tcp

C:\>netstat -s -p tcp

TCP Statistics for IPv4

Active Opens = 269
Passive Opens = 123
Failed Connection Attempts = 11
Reset Connections = 54
Current Connections = 4
Segments Received = 24935
Segments Sent = 23563
Segments Retransmitted = 5

So I don't believe packet loss is the issue here.
-----
I yield the floor.

Edited, Sat Feb 26 08:13:16 2005 by Zoelef