Robert,
This is true. I have recently done some tweaks on our new Cisco 4006's
which we have installed in the network closets. Included in the items I
researched were: Enabling portfast on ports connected to servers and
workstations. Disabling Etherchannel and trunking (which I found out, are
set to autonegotiate by default on Cisco Switches). And also, hardsetting
the port switches to match the capabilities of the NIC cards. I had to do
this for most of my Linux/Unix users as they were seeing the errors more
than my PC users. Here are some links to some information from the Cisco
website that I came across while doing my research:
http://www.cisco.com/warp/public/473/3.html
http://www.cisco.com/warp/public/473/46.html
Hope this information helps!
Heather Buri
-----Original Message-----
From: Fowler, Robert J. [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 11:34 AM
To: [EMAIL PROTECTED]
Subject: Duplex setting
I've read in messages, and in books, about setting the duplex to full/half
vs. auto. I knew that it was flaky, but no specifics. We had a machine
losing connectivity, and it turns out this was the reason. I changed the
port from auto to full duplex, and everything seems to work great. Is there
any specific information as to what can cause this? For instance, maybe the
auto-detect detects it as half then changes to full, causing a brief outage
in connectivity?
Thanks,
Joey Fowler
We are told that talent creates its own opportunities. But it sometimes
seems that intense desire creates not only its own opportunities, but its
own talents.
- Eric Hoffer (1902-1983 American Author & Philosopher)
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
