hmm, this is an odd one.  i have an additional fastethernet card in my
ultra2.  it's acting up.

when i rebooted, the nic was intermittant in response.  here's the output:

------------------
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.200.4: bytes=32 time=2ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time=1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
----------------------

eventually, the card becomes inresponsive and doesn't respond to anything.
i've configured it properly, and the ultra2's onboard fastethernet works w/o
any hiccups.

so i don't get what's going on with this one.

is there anyway to test the hardware to see if the card's defective?

On Thu, 29 Jan 2004, Sameer wrote:

> hmm, this is an odd one.  i have an additional fastethernet card in my
> ultra2.  it's acting up.
>
> when i rebooted, the nic was intermittant in response.  here's the output:
>
> ------------------
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time=2ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time=1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> ----------------------
>
> eventually, the card becomes inresponsive and doesn't respond to anything.
> i've configured it properly, and the ultra2's onboard fastethernet works w/o
> any hiccups.
>
> so i don't get what's going on with this one.
>
> is there anyway to test the hardware to see if the card's defective?

Are you sure its the card?
Have you done all other tests?

* checked that cable is properly attached and not broken?
* changed cable anyway, just to check.
* checked that switch/hub/cross is ok?
* try connecting the working cable from the other port (or other system)
  and see if you get proper link ups and such.
  Direct connect to another system (any with an ethernet) to take all else
  out of the loop.

If all thoose doesnt make any diff, then I would suspect a broken card or
possibly that you need a patch/fw for the card.

/Johan A

Sameer a =E9crit :
> =

> hmm, this is an odd one.  i have an additional fastethernet card in my
> ultra2.  it's acting up.
> =

> when i rebooted, the nic was intermittant in response.  here's the outp=
ut:
> =

that looks like a problem I see from time to time : duplicate ip
adresses
on your lan. try unplugin that station an pinging the ip again.

Regards, Marc