From: "Geo." 

It's hard to tell what could be affecting what from the description but my
bet is still on the switch being the problem.

I'm guessing from the entries below about fiber gigabit that there is more
hardware than just a switch so the network guy is really going to have to
figure out how to test to the different points to see where the network is
failing.

One thing you could ask him to do is see if it's possible (it may not be)
to put your desktop and the server in question on the same network segment
so you bypass the switch, then run your test and I bet you find no drops.

Geo.

"Ellen K"  wrote in message
news:b09718.c66801{at}harborwebs.com...
> I couldn't figure out the diagrams at ServerGuy's desk and neither he nor
> NewlyMintedNetworkGuy are answering their cellphones.  However, on looking at
> the results of the monitoring tool posted on the intranet (which only shows a
> 3600 between the outlying folks and the 6509) I see that the entire 5th floor
> in TJ is down, so I guess they have their hands full with that.
>
> Could the 6509 itself be bad?
>
> On the intranet thing I also see a bunch of warnings and alerts but I don't
> know what most of it means.  Like, there will be an entry
"Ellen's Gateway is
> warning" and then the next one is "Ellen's Gateway is up".
>
> The latest two entries are:
> 9:51
> Reset: Percent Utilization of LA-6509-Port 3/1 ù short wave fiber gigabit
> ethernet has returned to normal. Current traffic load of this interface is
> Received : 210 Kbps Transmitted : 4865 bps
>
> 9:53
> Alert: Transmit Percent Utilization of LA-6509-Port 3/1 ù short wave fiber
> gigabit ethernet is 4 %. Current traffic load of this interface is Received :
> 299 bps Transmitted : 44 Mbps
>
> ???
>
> > From: "Geo." 
> > "Ellen K."  wrote in message
> > news:kub6c0lqrnmqbr0cfim0ech6sdcl4c7q2b{at}4ax.com...
> >> I think there is one thing (can't remember exactly, is there such a
> >> thing as a 3600?) between my desktop and the big switch.  I'm
leaving to
> >> work now, will try to see if I can figure out the diagram at
ServerGuy's
> >> desk after I get in.
> > Yes, there is a cisco 3600 series router
> >http://www.cisco.com/warp/public/cc/pd/rt/3600/ but imo that's probably not
th
> > cause unless it has a bad port or something, I think that's possible but
> > unlikely. Easy enough to check the uptime and see if it's rebooting or
> > something. In fact that might be a good check for the switch as well, have
> >network guy check uptime on both devices, if one appears to have rebooted
abou
> > the time of the drops then you found the problem.
> > I'd still suspect the switch, routers are usually very dependable, it's the
> >switches that nobody ever pays attention to setup that end up causing
problems
> > like this. (that's why I hate switches)
> > Geo.

--- BBBS/NT v4.01 Flag-5