Yes, the file server is in the same room as the switch and it's connected at
100/full. All other hosts are in a different room connected via cat3
cabling and running at 10/half (no autonegotiation). We have checked the
cabling distances are the longest cable was about 100 feet.
I have been pinging the hosts and server from a router that is also
connected to the switch at 10/half, and is also in the same room.
The switch is a Baystack 303, but i think just for grins I'll run up there
and replace it with a newer 310 to see what happens.
I would LOVE to have a sniffer and/or RMON probe right now, but alas, we
have neither. :-( I've got the software to analyze rmon information, but
nothing to analyze!
> Hmm, I can think of several things that may be going wrong, and (perhaps
> taken together) cause your problem. But first a few questions and
> suggested experiments (some of which you may have tried already):
>
> - Is the file server in the same room as the switch?
> - What are the endpoints of the IP traffic on the LAN? Clients and
> router (on the way to a remote server)? Clients and local server?
> - Where have you been pinging the hosts from?
> - Do you have port error stats with an IPX client going straight into
> the hub vs. at its appointed location? Packet captures under the same
> conditions that may throw some light on the sluggishness?
>
> Now for some possible causes:
>
> - Bad or marginal cable or connectors
> - Bad or marginal switch ports, cards, or backplane connectors
> - EMI from unexpected sources such as the switch's own power supply
> - Network diameter issues (you didn't specify 10/100/1000baseT)
>
> HTH.
>
> On Thu, 10 Aug 2000, John Neiberger wrote:
>
> > Okay, I'm going completely out of my mind. I am at the end of my rope
with
> > this problem and I have no idea where to go from here. Basically, I'm
> > begging for suggestions!
> >
> > Several PCs at one of our branches are having difficulty running a
certain
> > application, which uses IPX on 802.3 frames. We are also running IP on
this
> > LAN with arpa frames. There is a file server and printer on this LAN,
and
> > all IPX traffic is between the hosts and that file server.
> >
> > We are have ZERO problems with IP traffic on this LAN. I've been
pinging
> > the tar out the hosts and they act perfectly normal, except for the
file
> > server which had, at worst, a 98% success rate over time.
> >
> > On our ethernet switch, we are seeing alignment errors and CRC errors
coming
> > from the file server. The cable has been replaced and we verified that
it
> > is cat 5, but the problems still exist. This is a new file server with
a
> > new NIC.
> >
> > Okay, the problem is that this particular application takes forever to
run
> > from a desktop out in the building. yet, if you bring that very PC
back to
> > the room where the switch is, the application runs very quickly. This
led
> > us to believe that the cabling was bad. However, if the cabling were
bad,
> > why are we having no problems with IP traffic? None at all! That just
> > doesn't make any sense to me.
> >
> > Granted, the cabling out to the desks is Cat 3 and this branch has had
some
> > previous EMI problems in the room, but I just don't see how EMI could
> > selectively cause one application to fail without there being some
> > indication of problems with other applications.
> >
> > I've considered replacing the switch, but the problem only happens when
a PC
> > out in the main room uses the application, no matter what port it is
> > connected to. Bring a PC back to the switch room and connect it to any
port
> > and the program runs as advertised. So, I'm not going to waste my time
with
> > that. I've also considered replacing the NIC in the server since we're
> > seeing errors coming from it, but that would not explain the problems
we're
> > having, anyway, so that is probably pointless.
> >
> > any ideas? Our next step is to hire a very expensive data center
design
> > company to go up there and check things out. We've had electricians
check
> > the room and they said they could find no obvious sources of EMI, even
> > though we know that it is prevalent there.
> >
> > Help...please help....I'm dying here, and I'm quickly losing faith in
my
> > troubleshooting skills!
> >
> > TIA,
> > John
> >
> >
> >
> >
> >
> > _______________________________________________________
> > Say Bye to Slow Internet!
> > http://www.home.com/xinbox/signup.html
> >
> > ___________________________________
> > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> > FAQ, list archives, and subscription info: http://www.groupstudy.com
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
>
>
> --
> Bungee jumping and skydiving are for wimps. If you want to experience
> true gut-wrenching terror, have children. --Dusty Rhoades.
>
_______________________________________________________
Say Bye to Slow Internet!
http://www.home.com/xinbox/signup.html
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
