 |
 |
Margaret, What we're dealing with here is still the effects of the Welchia worm/virus. We haven't had the resources to contact everyone whose computer is infected, and have them correct the problem. We're working on another round of notifications, so once those go out, and we get some compliance, things should be better. I suspect that one of the reasons the ACD DSL service is better is because there are more customers on the MSU IP's than the ACD IP's. Or perhaps ACD has an easier time contacting their customers which are infected (MUCH smaller user base). For the record, yesterday evening, my monitor picked up 4 infected computers in ACD's East Lansing territory. That's apparently more than enough to swamp the network. Doug > I had an ACD DSL connection for one year prior to switching to an MSU ACD > DSL connection when it became available. For that year, I experienced > stellar network performance. And for quite a while after switching to MSU > DSL, network performance was just as good. However, since the outage the > entire 7/4 weekend (MSU's fault), performance has been very spotty, mostly > slow. Several outages, a couple lasting *days*. I know these to be the > fault of MSU, because each time ACD switched me over to their network, and I > had that stellar connection back once again. (I was switched back to MSU's > network once the DSL connection resumed function.) I don't know what's > going on lately, but I'm *really* disapppointed in MSU DSL. During the last > outage, I went out and bought a modem, and I'm sorry to say that I've had to > make use of it several times over the past couple months. > > Fortunately for me again today, I was able to contact ACD before they > closed, and they switched me over to the ACD network. Immediately prior to > this, my MSU connection died completely, so I fired up my modem to check my > mail. Upon disconnecting my modem connection, I found that my router had > lost its (DSL) IP address, so I power-cycled my router thinking it had just > freaked out. When it came back up, I had an IP address of 0.0.0.0, thus > *no* connection to MSU's DHCP server. The ACD tech did some troubleshooting > but ultimately had to switch me to ACD's network to get me a connection for > tonight. Tomorrow it's back to MSU, which doesn't thrill me. And I *never* > thought I'd say that. :-( > > Margaret > > ----- Original Message ----- > From: "Rich Wiggins" <[log in to unmask]> > To: <[log in to unmask]> > Sent: Wednesday, September 24, 2003 7:19 PM > Subject: Re: MSU Internet Access Problems? > > > > I'm also an MSU ACD DSL customer. My experience over the last couple > > months has been very mixed. I've had several outages, which seem > > to be prone to begin on weekends when the tech support window is about > > to close. When I subscribed to the ACD/MSU service, I thought it > > was an ideal short path to a very fat broadband pipe. > > > > Sometimes problems might be with the ACD side of things, and sometimes > > they might be with the MSU side of things. The irony is, if there are > > problems with MSU's network, that's likely to be a time when I really > > need my Internet access to work well! I'm wondering if Margaret and > > other NAG folks feel that way too. > > > > As for any changes in whether ICMP or Ping work from MSU/ACD > > connections, I'm not aware of any. I believe the MSU/ACD addresses > > are treated as if "on campus". I've been using Ping from > > my connection throughout the Days of Blaster and Welchia, > > and don't recall any evidence of being blocked. > > > > Over the years I've relied on 35.8.2.41 as THE place to ping > > to, no matter where I am, to see if I've got connectivity. > > When helping a friend set up SBC Yahoo DSL yesterday, I instinctively > > typed that IP address. Took me a second to realize: not an > > MSU origination address, so I'm blocked at the border. > > > > /rich > > > > >On Wed, 24 Sep 2003, Margaret Wilson wrote: > > > > > >> I have been able to ping 35.8.2.3 all day, getting anywhere from > between 0 > > >> and 100% packet loss. It wasn't till 5:03 this evening that 35.8.2.3 > > >> started generating 100% packet loss continuously. Maybe they're > blocking > > >> ICMP now, but they weren't earlier today.... > > >> > > >> Regards, > > >> > > >> Margaret > > >> [...] > > > > > >Maybe they were experimenting with lifting the block (which may explain > > >some of the on-campus sluggishness today) and decided to put it back on; > > >http://help.msu.edu/status/ still says off-campus ICMP packets are being > > >blocked. > > > > > >------------------------------------------------------------------------- > > >George J Perkins http://www.pa.msu.edu/people/perkins/ > > >1209B BPS Bldg, MSU Phone: 517-355-9200 ext 2567 > > >East Lansing, MI 48824-2320 FAX: 517-353-4500 > Doug Nelson [log in to unmask] Network Manager Ph: (517) 353-2980 Computer Laboratory http://www.msu.edu/~nelson/ Michigan State University