On 12/04/2013 09:57 AM, Paul Robert Marino wrote:
> Well while the NIC firmware may be an issue I would suspect some of
> the switch settings.
> base on the message "... failed; no link present." here are a few more
> things to check.
> 
> 1) Please make sure every thing is set to full auto on both sides,

They are.

> and
> if you can linit the advertises auto negotiation rates and duplex to
> just the one you want. Almost all business class switches can be
> configured to do this. Do not hard set the speed and duplex because
> that causes other intermittent problems due to the fact that it also
> disables other safety checks which require the auto negotiation
> process, for example many copper switches and NIC's and all fiber
> optic switches and NIC's have a built in TDR (Time Delay
> Reflectomiter) to detect cable problems. The TDR requires at least
> limited support for reflecting the signal on the opposite sides to
> work and that is determined during the auto negotiation process.
> 
> 2) check if the switch has any flapping prevention hold down timers if
> so disable them. the writers of these features often assume MS.
> Windows like behavior which in similar to how Network Manager would
> handle a delayed link up, but  traditional *ux detects it as a failure
> to bring the interface up on boot.

This is a simple dumb TRENDNet switch in the lab. I have no such
settings on it.

Thanks anyway for the advice!
~Stack~