Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Full duplex question

0 views
Skip to first unread message

G. Lam

unread,
Jul 22, 2002, 9:36:50 PM7/22/02
to
We are running our accounting system with a NW3.12 server. I noticed the
Full/Col LED on the 16 port switch for the server port is off. That means
the server is on half duplex mode. How can I turn it to full duplex mode?
Thank you in advance.
Gary


Dave Lunn

unread,
Jul 22, 2002, 10:46:22 PM7/22/02
to
In order to run full dux you need 100baseT NICs server and WS, a Switch, and
cat5 *functional* cabling. If the cabling has problems it won't go.

Once you have all that, then you start by setting the NIC at each end to
Auto for speed/duplex. If any component doesn't meet spec in the link you
can't get there, and the next step is forcing them to 100 half dux. Trying
to force 100 full dux is a waste of time if it won't auto negotiate to full.
--
Dave Lunn
NSCV Sysop
http://support.novell.com


Barry Schnur

unread,
Jul 23, 2002, 2:27:33 AM7/23/02
to
What sort of NIC here? Also, is 3.12 fully patched?

Barry Schnur
Novell Support Connection Sysop

Please post replies ONLY via the Newsgroup

Billy Ko

unread,
Jul 23, 2002, 9:45:02 AM7/23/02
to
Usually, you can specify forcing full duplex when you call the NIC driver by
adding the option to the NIC line in your autexec.ncf.

Although it's not recommended, because if it were capable of full duplex, it
usually chooses it, the reason why you might want to try it is because I said
*usually*. Occasionally, the N-way sensing doesn't work correctly, and you
end up with it being misconfigured (sometimes to the point where it can't
connect, as in the NIC configured itself for full duplex, but the hub could
only do half).

But, as was mentioned earlier, make absolutely certain that all your
equipment is capable of full duplex before trying to force it.

Bill

On Tue, 23 Jul 2002 02:46:22 GMT, Dave Lunn wrote:

:>In order to run full dux you need 100baseT NICs server and WS, a Switch, and

:>
:>

0 new messages