20020424: network connectivity to rr.com (cont.)

>From: "Kevin Polston" <address@hidden>
>Organization: NOAA/NWS
>Keywords: 200204230009.g3N09Ia00698 IDD Unidata-Wisconsin

Kevin,

>Before Chiz had given me access to motherlode I tried to acquire the
>data I needed from here locally - first through the Training Center,
>then through AWC.  Each time we tried to get something set up it was
>always shot down because of the way the conenction is here. The problem
>being that here at the training center our connection runs through
>Central Region Headquarters (CRH).  In just setting up a simple
>transfer of just a single type of IR imagery...it created a serious
>problem in that it was using up too much bandwidth. This is because CRH
>not only feeds us but also all of the other central region offices.

So, you have been fighting bandwidth problems for quite some time.

>It
>did not matter if we tried to get the data from AWC (which would have
>been nice because they have a vast array of satellite data there)
>because ultimately we would still be clogging up CRH lines.

Understood.

>I found it
>hard to believe that just the basic GOES-EAST IR image would create
>such a problem. Not to mention trying to get the VIS data or any other
>type of imagery.  So the bottom line was we could not transfer the data
>because of taking up too much bandwidth.  That is the weather service I
>suppose.  -:(

Yes, but it is indicative of the overall networking situation there.

>And that is why I am using the kc.rr.com address.

Is the machine connected to rr.com in the training center?  Is it used
in your training activities, or is this for personal use?

After reading how Road Runner provides broadband access (cable modem),
I can understand how/why your connection to the outside world can
vary.  Internet access through cable modems is shared among all of the
users in the local area.  Less people on the local drop will typically
result in you getting a bigger share of the available bandwidth.  The
converse is also true: more people on the local drop typically means
that you will get a smaller share of the available bandwidth.  On top
of that, a number of ISPs impose limits on how much a user can transfer
to/from his/her machine.  This and/or a combination of this and the
number of users on the local drop may be what is causing your network
throughput to vary.  On top of this, I could imagine a situation where
the ISP is monitoring one kind of service (like http) but not others
(like FTP).  If they are limiting your bandwidth based on a metric that
they are not monitoring (like FTP, perhaps) then transferring data that
way would work better than for a method (perhaps LDM) that they are
monitoring and using to limit service.

Did you ever contact Road Runner and ask them if they could explain why
your bandwidth varies?  I would imagine that they maintain full
information on what bandwidth a customer is using, and may limit their
access based on the service agreement they have with the customer.
I know none of this as fact; it is only conjecture on my part.

The bottom line, however, is this: when your network connection
degrades, you should typically contact your ISP, not us since we may
have no way of effecting a remedy.

Tom