Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.3: Check network speed to resolve connection issues' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.3: Check network speed to resolve connection issues
Authored by: SirDrinksAlot on Feb 02, '04 02:07:03AM

If you have to change the connection speed its not a problem with Panther or MacOS, the problem is with your cables. If your cables are bad in some way (not all the wires are connected or are in the wrong order) this will happen.

Before blaming MacOS, check your cables.



[ Reply to This | # ]
10.3: Check network speed to resolve connection issues
Authored by: geordie on Feb 02, '04 08:43:49AM

Actually this is usually an issue with spanning tree. Or more specifically portfast (the cisco term other vendoors call it other things) not being turned on. http://docs.info.apple.com/article.html?artnum=30922 talks a little about it from the appletalk perspective, but is also a problem with link negotiation.

Basically the problem is that the switch port is not enabled until a check for a network loop is finished. On a modern fast computer auto-negotiation has finished before the link is actually enabled. Some clueless administrators then set the port to a fixed rate and then auto-negotiation is guaranteed to fail although as long as the host is set for the right settings things work fine. The correct thing to do is to set the port to turn on immmediately and only turn off if a loop is detected. Turning the port on first is the so called portfast feature. All of that is of course a gross simplification. If you want to know more do a search on spanning tree/802.1d/Portfast etc.



[ Reply to This | # ]
10.3: Check network speed to resolve connection issues
Authored by: Cerberus on Feb 02, '04 01:41:59PM

I will insert my comment here and leav it to you all to tag off it. I have a problem where my DEC based 10/100 card is only beign detected as a 10baseT card.

This ONLY started with Panther and it stops when I revert to X.2. This is not to disparage anyone but it can be so hard to find the answer and I think you are all right (in the proper situation). If it works in 9 and X.2 but does not in X.3 then it is not a cable. Apple did update the DEC kext and it is not backward compatible.

It is a Asante 10/100 card and when I try to use ifconfig to change ANY parameters it tells me OPERATION NOT PERMITTED.

--:~ --$ ifconfig en1
en1: flags=8863 mtu 1500
inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:00:94:a4:3e:fd
media: autoselect (10baseT/UTP) status: active
supported media: 10baseT/UTP 100baseTX 10baseT/UTP 100baseTX autoselect autoselect 10baseT/UTP
--:~ --$ ifconfig en1 media 100baseTX
ifconfig: SIOCSIFMEDIA: Operation not permitted
--:~ --$ ifconfig en1 media 100baseTX mediaopt full-duplex
ifconfig: SIOCSIFMEDIA: Operation not permitted
--:~ --$ ifconfig en1 media 100baseTX full-duplex
ifconfig: SIOCSIFMEDIA: Operation not permitted
--:~ --$

same thing as root (JIK) an I have tried to FORCE it within NETWORK in SYSTEM PREFERENCES but no luck. As an adendum, I can see in my system.log that the card is announcing (at statup) that 10baseT LINK OK but nothing after that (100baseTX LINK OK etc). I do have ONE, ONE lone start at which (apparently) it shows 100baseTX LINK OK but that is out of about 50-100 restarts.



[ Reply to This | # ]