|
[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[NMLUG] speaking of Comcast... saturated upload kills connection
like you jason, i've played with both OS's at home. analyzed network
traffic, bought a new cable modem, different ethernet card and USB setups
with modem, played with my netcard settings, dhcp client settings, turned
off iptables, scanned for virus's, not sure what else to try. the comcast
person on the phone said they would check the line. my cable ran
without problems until last april.
i mentioned before that i''ve posted on the comcast user forums, and it
appears this problem and these types of problems are shared with other
users.
i was really hoping a comcast network admin was on this list :)
at this point i may give dsl a shot.
greg
On Sun, 6 Jun 2004, Jason Schaefer wrote:
> Date: Sun, 06 Jun 2004 11:47:38 -0600
> From: Jason Schaefer <js@jasonschaefer.com>
> Reply-To: New Mexico Linux Users Group Mail List <nmlug@nmlug.org>
> To: nmlug@nmlug.org
> Subject: [NMLUG] speaking of Comcast... saturated upload kills connection
>
> I have been looking into this problem for some time now and have tested
> it using about 5 different modems+connections+configurations. When you
> upload some place with higher download than you, 75-99% of packets are
> lost to or from any other connections. Same thing happens, of course,
> when someone downloads from you with a higher speed than your upload. I
> have used ftp, ssh and http to transfer files. Im using ping from a
> third host to verify the packet loss. Example: If a friend is
> downloading files from my computer I have to kill their transfer to get
> back on irc, check mail etc. If I am away I have to wait, for however
> long, to ssh in. Its that bad and its not just me.
>
> Comcast has sent people out 3 times. They test signal strength and the
> modem and make a bunch of calls and tells me its my internal networks
> fault. In other words they are not responsible for anything but the
> modem... so naturally. No one has a clue:-( They put me in contact with
> the manager and he had to clue what I was even saying, so he asked if I
> would write up some details. I haven't heard back. I think it must be an
> inherent problem, being a shared network. They insist this is not the
> case and they have NEVER seen it before. Has anyone else seen this
> problem? If you have cable give it a try and let me and, more
> importantly, comcast know what you find.
>
> Jason
|
|
