WinXP and Ethernet "cable is unplugged" error

I'm an SBC DSL user. My ethernet card likes to connect, then as
quickly disconnect, giving the "A network cable is unplugged"
error.

When I first got DSL, all worked fine. After a week or so, this
error appeared and nothing worked since. For fun I reactivated it
yesterday and it worked great all day.

This morning, it did the same "network cable unplugged deal".
However it LOOKS like it connects, then after a second, once
again, gives the error and the red X.

System: Windows XP Ethernet: SiS 900 PCI (This is integrated
into the motherboard, so it really isn't a "card" per se.)

After the first error, it was verified the DSL router, and cable
were fine.

All windows troubleshooting tests worked fine.

I assume a misconfiguration or conflict of sorts.

Any ideas folks?

--Thanks... John

Nope! Sure sounds like your DSL Interface box is cutting out. Did you have a
power glitches in the houise? Is that device on UPS?
"John L. Wilkerson Jr." <johnwilkers@sbcglobal.net> wrote in message
news:Xns93B06BDA0606Bjohnwilkerssbc@206.141.193.32...
> I'm an SBC DSL user. My ethernet card likes to connect, then as
> quickly disconnect, giving the "A network cable is unplugged"
> error.
>
> When I first got DSL, all worked fine. After a week or so, this
> error appeared and nothing worked since. For fun I reactivated it
> yesterday and it worked great all day.
>
> This morning, it did the same "network cable unplugged deal".
> However it LOOKS like it connects, then after a second, once
> again, gives the error and the red X.
>
> System: Windows XP Ethernet: SiS 900 PCI (This is integrated
> into the motherboard, so it really isn't a "card" per se.)
>
> After the first error, it was verified the DSL router, and cable
> were fine.
>
> All windows troubleshooting tests worked fine.
>
> I assume a misconfiguration or conflict of sorts.
>
> Any ideas folks?
>
> --Thanks... John
>