[NTLUG:Discuss] ntlug.org back from the dead again

[Johnie Stafford]

As with anything else, it depends on what you're doing. If we're
talking 10Mb/s, then Auto+Auto usually works, depending on who
implements the negotiation.

If you're talking 100Mb/s, things are totally different. I've never
known Auto+Auto to work in a Cisco FastEthernet (100Mb/s)
environment. You will almost always get a duplex mismatch. Auto+Hard
usuall works, although they usually just go with Hard+Hard in our shop
to make sure everything is running at 100/Full.

Johnie



>>> On Tue, 05 Jul 2005 18:46:25 -0500, Robert Thompson <ntlug at thorshammer.org> said:

 >> Auto+Auto=works
 >> Auto+Hard coded=no workie (theplanet.com)
 >> Hard coded+Hard coded=works if both set the same
 >> (this is what ntlug.org is doing now that
 >> I know they hard code their ports)

 rt> My experience has been:

 rt> Auto + Auto
 rt>      Might work if both devices know how to talk correctly.

 rt> Auto + Hard coded
 rt>      You might have a link, but with errors. Can actually work sometimes.

 rt> Hard Code + Hard Code
 rt>      Works the majority of the time on the majority of devices and
 rt> avoids any auto-negotiation problems.

 rt> YMMV,

 rt> =-= Robert Thompson


 rt> Chris Cox wrote:

 >> joseph beasley wrote:
 >> 
 >>> We normally force servers to 100/full and workstations to auto.  Unless
 >>> it is my desktop of course.  Then it's 100/full also.
 >> By definition if one side is auto and the other is fixed, you'll
 >> go end up with half.... however one side will probably believe
 >> it is full and the other half... and many switches will dumb
 >> it all the way down to 10baseT half because of all of the errors.
 >> Speak up network guys!
 >> My understanding from my own experience:
 >> Auto+Auto=works
 >> Auto+Hard coded=no workie (theplanet.com)
 >> Hard coded+Hard coded=works if both set the same
 >> (this is what ntlug.org is doing now that
 >> I know they hard code their ports)
 >> 
 >>> --- Chris Cox <cjcox at acm.org> wrote:
 >>> 
 >>> 
 >>>> I think theplanet.com folks have a very poor
 >>>> understanding of 802.3 auto negotiation.
 >>>> 
 >>>> Anyhow, they hard code all of their ports
 >>>> to 10BaseT-FD.  That's not going to work exactly
 >>>> right with a card doing auto negotiation.  I
 >>>> put in code to hard code our ntlug.org interface
 >>>> to 10BaseT-FD (otherwise it will collapse to
 >>>> 10Bast-T half duplex).
 >>>> 
 >>>> We're plugged into a really ugly switch (an old
 >>>> Intel switch).  I've worked with switches from
 >>>> that generation and can tell you absolutely beyond
 >>>> a shadow of doubt, that is NOT a good switch.
 >>>> 
 >>>> Paying customers get Cisco, but all ports are
 >>>> HARD CODED to 10BaseT-FD as well.... which I still find
 >>>> very interesting.  Maybe somebody can enlighten
 >>>> me on why that is a "best practice"... seems to
 >>>> me that will only cause trouble when the client
 >>>> is auto-negotiating.
 >>>> 
 >>>> Anyway, hopefully things are back up again for
 >>>> awhile.
 >>>> 
 >>>> Regards,
 >>>> Chris
 >>>> 
 >>>> 
 >>>> _______________________________________________
 >>>> https://ntlug.org/mailman/listinfo/discuss
 >>>> 
 >>> 
 >>> 
 >>> Joe Beasley
 >>> CNE, CCNP, MCSE, CCNA, AEIOU....
 >>> PGP/GPG key -- http://home.comcast.net/~joe.beasley/joebeasley.txt
 >>> AOL Messenger joebeasley3rd
 >>> Yahoo Messenger joe_beasley
 >>> MSN Messenger joebeasley3rd
 >>> 
 >>> 
 >>> 
 >>> 
 >>> __________________________________________________
 >>> Do You Yahoo!?
 >>> Tired of spam?  Yahoo! Mail has the best spam protection around
 >>> http://mail.yahoo.com
 >>> _______________________________________________
 >>> https://ntlug.org/mailman/listinfo/discuss
 >>> 
 >>> 
 >> _______________________________________________
 >> https://ntlug.org/mailman/listinfo/discuss
 >> 

 rt> _______________________________________________
 rt> https://ntlug.org/mailman/listinfo/discuss