On Thu, 4 May 2000 [EMAIL PROTECTED] wrote: > > with a flip cable and the sparc is locked at 100BaseTX-FD and mii-diag > > showed that the Intel interface that was on the otherside was also > > 100BaseTX-FD.. > > OK. This increases confusion. 8) Yes, it's still not clear that the duplex is set correctly. Forcing full duplex is almost always wrong. Forcing either 100Mbps or full duplex turns off or breaks autonegotiation. If the equipment cannot autonegotiate full duplex, it should be left at its normal state, half duplex. For background info read http://scyld.com/expert/NWay.html You should check /proc/net/dev to see what errors you are getting. Donald Becker [EMAIL PROTECTED] Scyld Computing Corporation 410 Severn Ave. Suite 210 Annapolis MD 21403 - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
- Possible TCP Problem with RH6.2 talking to Solaris2.6/2.7 shane
- Re: Possible TCP Problem with RH6.2 talking to Solar... Alan Cox
- Re: Possible TCP Problem with RH6.2 talking to Solar... kuznet
- Re: Possible TCP Problem with RH6.2 talking to S... shane
- Re: Possible TCP Problem with RH6.2 talking ... kuznet
- Re: Possible TCP Problem with RH6.2 talk... shane
- Re: Possible TCP Problem with RH6.2... kuznet
- Re: Possible TCP Problem with R... Gregory Maxwell
- Re: Possible TCP Problem with RH6.2 talk... Donald Becker
- Re: Possible TCP Problem with RH6.2 talking to S... shane
- Re: Possible TCP Problem with RH6.2 talking ... James Sutherland
- Re: Possible TCP Problem with RH6.2 talking ... Jes Sorensen
- Re: Possible TCP Problem with RH6.2 talk... James Sutherland
- Re: Possible TCP Problem with RH6.2 talking ... kuznet
- Re: Possible TCP Problem with RH6.2 talk... Donald Becker
- Re: Possible TCP Problem with RH6.2... kuznet
- Re: Possible TCP Problem with R... Richard Gooch
- Re: Possible TCP Problem wi... kuznet
- Re: Possible TCP Problem wi... Richard Gooch
