|
Home > Archive > alt.certification.network-plus > September 2003 > Strange problem with hub
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Strange problem with hub
|
|
|
| I have two computers hooked to an HP 8 port hub. The hub is cascaded to a
large switch on the lan. The two computers could not ping anything on the
lan. I noticed by looking at the lights on the hub that the cascade port
was having major activity. I unplugged the cable going to the switch and
plugged it back in, then all was well. The light went back to normal
activity and the two computers could then communicate with all on the lan.
I had never seen this before. Anybody have a guess as to what causes this?
Dave
| |
| BeeBoy 2003-09-27, 9:25 pm |
| It sound like either you have a network broadcast via a faulty NIC or you
have the same IP address assigned to both machines!!
"DaveL" <dave1027@comcast.net> wrote in message
news RqdnZbxA9phJ-iiXTWJjw@comcast.com...
> I have two computers hooked to an HP 8 port hub. The hub is cascaded to a
> large switch on the lan. The two computers could not ping anything on the
> lan. I noticed by looking at the lights on the hub that the cascade port
> was having major activity. I unplugged the cable going to the switch and
> plugged it back in, then all was well. The light went back to normal
> activity and the two computers could then communicate with all on the lan.
> I had never seen this before. Anybody have a guess as to what causes
this?
>
> Dave
>
| |
| Gordon Findlay 2003-09-27, 11:24 pm |
| Well, since it worked after uplugging and replugging the cascade
cable, it clearly is not an IP addressing issue. And almost certainly
not a NIC, since again, it's going fine now and he didn't do anything
to the NICs
I suspect that something provoked the port at one end of the cascade
cable - can't say which - into some sort of broadcast mode.
Alternatively the switch or hub was rebroadcasting for some reason -
getting an error report perhaps? or the cable wasn't properly seated
the first time.
It's stopped now, and if it's any consolation I've seen this many
timnes, and seldom has the symptom ever recurred.
On Sun, 28 Sep 2003 01:27:22 +0100, "BeeBoy"
<wbrooks2000@ukgateway.net> wrote:
>It sound like either you have a network broadcast via a faulty NIC or you
>have the same IP address assigned to both machines!!
>
>
>"DaveL" <dave1027@comcast.net> wrote in message
>newsRqdnZbxA9phJ-iiXTWJjw@comcast.com...
>> I have two computers hooked to an HP 8 port hub. The hub is cascaded to a
>> large switch on the lan. The two computers could not ping anything on the
>> lan. I noticed by looking at the lights on the hub that the cascade port
>> was having major activity. I unplugged the cable going to the switch and
>> plugged it back in, then all was well. The light went back to normal
>> activity and the two computers could then communicate with all on the lan.
>> I had never seen this before. Anybody have a guess as to what causes
>this?
>>
>> Dave
>>
>
| |
| Netwerkz 2003-09-28, 1:24 am |
| "DaveL" <dave1027@comcast.net> wrote in message
newsRqdnZbxA9phJ-iiXTWJjw@comcast.com...
> I have two computers hooked to an HP 8 port hub. The hub is cascaded to a
> large switch on the lan. The two computers could not ping anything on the
> lan. I noticed by looking at the lights on the hub that the cascade port
> was having major activity. I unplugged the cable going to the switch and
> plugged it back in, then all was well. The light went back to normal
> activity and the two computers could then communicate with all on the lan.
> I had never seen this before. Anybody have a guess as to what causes
this?
>
> Dave
>
Are your switch ports set to autonegotiate?
You should lock everything down if you can.
100Mbps/Full Duplex/Autonegotiate disabled.
NICs/Switched/Hubs (your hub may be stuck
at half duplex).
Also, it's a good idea to lock frametypes.
|
|
|
|
|