: [EMAIL PROTECTED]
Subject: Re: Ethernet Troubleshooting Woes
I agree that this appears to be a cabling issue, but if that were the case
why does our IP traffic not suffer at all? There are zero errors with our
IP traffic, but this one single application that uses IPX doesn't function
well
Original Message -
> From: "David Jones" <[EMAIL PROTECTED]>
> To: "'John Neiberger'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, 10 August, 2000 17:20
> Subject: RE: Ethernet Troubleshooting Woes
>
>
> > The
I agree that this appears to be a cabling issue, but if that were the case
why does our IP traffic not suffer at all? There are zero errors with our
IP traffic, but this one single application that uses IPX doesn't function
well over that cabling. So, does that necessarily mean that the problem
John,
You may have already answered your question by asking it to the group.
"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
er
auto" associated with it.
>
> Kevin Wigle
>
> - Original Message -
> From: "David Jones" <[EMAIL PROTECTED]>
> To: "'John Neiberger'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, 10 August, 2000 17:20
>
gards
Rob
-Original Message-
From: John Neiberger [mailto:[EMAIL PROTECTED]]
Sent: Friday, 11 August 2000 7:56 AM
To: [EMAIL PROTECTED]
Subject: Ethernet Troubleshooting Woes
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
ed with it.
Kevin Wigle
- Original Message -
From: "David Jones" <[EMAIL PROTECTED]>
To: "'John Neiberger'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, 10 August, 2000 17:20
Subject: RE: Ethernet Troubleshooting Woes
> The firs
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 ping
, August 10, 2000 3:56 PM
To: [EMAIL PROTECTED]
Subject: Ethernet Troubleshooting Woes
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 bra
If the cable length is not too long, perhaps the NIC in the server is weak
and is making wimpy little IPX frames that don't make it all the way out to
the workstations.
Try changing the NIC before you call in the marines.
That's my story and I'm sticking to it.
Vlan2
>
>Okay, I'm going comp
: John Neiberger [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 10, 2000 2:56 PM
> To: [EMAIL PROTECTED]
> Subject: Ethernet Troubleshooting Woes
>
>
> Okay, I'm going completely out of my mind. I am at the end
> of my rope with
> this problem and I have no ide
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 a
12 matches
Mail list logo
