mglc2ticl4

Here are the results:

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C>ping -n 50 google.com

Pinging google.com [216.239.39.99] with 32 bytes of data:

Reply from 216.239.39.99: bytes=32 time=1702ms TTL=245

Reply from 216.239.39.99: bytes=32 time=1018ms TTL=245

Reply from 216.239.39.99: bytes=32 time=982ms TTL=245

Reply from 216.239.39.99: bytes=32 time=978ms TTL=245

Reply from 216.239.39.99: bytes=32 time=961ms TTL=245

Reply from 216.239.39.99: bytes=32 time=921ms TTL=245

Reply from 216.239.39.99: bytes=32 time=933ms TTL=245

Reply from 216.239.39.99: bytes=32 time=920ms TTL=245

Reply from 216.239.39.99: bytes=32 time=932ms TTL=245

Reply from 216.239.39.99: bytes=32 time=899ms TTL=245

Reply from 216.239.39.99: bytes=32 time=898ms TTL=245

Reply from 216.239.39.99: bytes=32 time=886ms TTL=245

Reply from 216.239.39.99: bytes=32 time=879ms TTL=245

Reply from 216.239.39.99: bytes=32 time=857ms TTL=245

Reply from 216.239.39.99: bytes=32 time=853ms TTL=245

Reply from 216.239.39.99: bytes=32 time=840ms TTL=245

Reply from 216.239.39.99: bytes=32 time=2619ms TTL=245

Reply from 216.239.39.99: bytes=32 time=922ms TTL=245

Reply from 216.239.39.99: bytes=32 time=949ms TTL=245

Reply from 216.239.39.99: bytes=32 time=980ms TTL=245

Reply from 216.239.39.99: bytes=32 time=936ms TTL=245

Reply from 216.239.39.99: bytes=32 time=931ms TTL=245

Reply from 216.239.39.99: bytes=32 time=903ms TTL=245

Reply from 216.239.39.99: bytes=32 time=919ms TTL=245

Reply from 216.239.39.99: bytes=32 time=886ms TTL=245

Reply from 216.239.39.99: bytes=32 time=870ms TTL=245

Reply from 216.239.39.99: bytes=32 time=853ms TTL=245

Reply from 216.239.39.99: bytes=32 time=837ms TTL=245

Reply from 216.239.39.99: bytes=32 time=841ms TTL=245

Reply from 216.239.39.99: bytes=32 time=840ms TTL=245

Reply from 216.239.39.99: bytes=32 time=855ms TTL=245

Reply from 216.239.39.99: bytes=32 time=811ms TTL=245

Reply from 216.239.39.99: bytes=32 time=775ms TTL=245

Reply from 216.239.39.99: bytes=32 time=778ms TTL=245

Reply from 216.239.39.99: bytes=32 time=762ms TTL=245

Reply from 216.239.39.99: bytes=32 time=745ms TTL=245

Reply from 216.239.39.99: bytes=32 time=761ms TTL=245

Reply from 216.239.39.99: bytes=32 time=728ms TTL=245

Reply from 216.239.39.99: bytes=32 time=720ms TTL=245

Reply from 216.239.39.99: bytes=32 time=715ms TTL=245

Reply from 216.239.39.99: bytes=32 time=699ms TTL=245

Reply from 216.239.39.99: bytes=32 time=730ms TTL=245

Reply from 216.239.39.99: bytes=32 time=686ms TTL=245

Reply from 216.239.39.99: bytes=32 time=654ms TTL=245

Reply from 216.239.39.99: bytes=32 time=666ms TTL=245

Reply from 216.239.39.99: bytes=32 time=1636ms TTL=245

Reply from 216.239.39.99: bytes=32 time=966ms TTL=245

Reply from 216.239.39.99: bytes=32 time=951ms TTL=245

Reply from 216.239.39.99: bytes=32 time=947ms TTL=245

Reply from 216.239.39.99: bytes=32 time=887ms TTL=245

Ping statistics for 216.239.39.99:

I've had the DW6000 since Dec. 2003, and didn't have too many problems until about a week ago when I noticed that the browsing was very erratic (slow or not working sometimes for extended periods).  When I check the system status, there are non-operational notes for TCP and Web Aceleration statuses.  They sometimes clear on power cycling but the problem recurs.  I called their tech department in India, but they made me waste 30 minutes doing useless things like bypassing my router, clearing the cache, etc.  They transferred me to "advanced" tech support, who placed me on hold for over one hour.  They had me re-register, and it did work for a while, but now I'm having the same problems again.  They deny that the problem is at their end.  Has anyone had any similar problems?