| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
The problem with duplex negotiation is not unique to OS X; see here for_______________________________________________
a decent explanation:
http://www.cites.uiuc.edu/network/autosense.html
Basically you need to either set everything to auto, or configure
everything manually. Going halfway will create problems.
- Ben
* Sellers <email@hidden> [2004-04-05 10:05] wibbled:tim,
Check the Duplex and Speed of your network cards. MacOS X has been
known
to have problems with duplex negotiation on the network. If your
network gear is set to 100 FDX (full duplex) then your MacOS X server
machine will go to 100 half - causing every other packet to get lost.
The best solution from Apple is to have both the Network Switch and the
Machine set to AUTO-NEGOTIATE mode. (there are also some fixes for
10.2 and supposedly 10.3.3 but I found auto was the easiest solution)
How to test this? Well, connect from Machine A to Machine B using SCP
or even AFP. Transfer a large file 100MB or more. See how long it
takes - and watch your network gear for warning lights about
transmissions problem (i.e. goes yellow all the time).
Then, go from Machine B to Machine C where B and C are in the same
network in the lab - and see if the speeds are any better.
On Apr 5, 2004, at 8:55 AM, Timothy K. Wilkinson wrote:
I'm helping someone who has a new OS X server and they need to do a_______________________________________________
setup
I've never done before.
They are in a building which has a VERY shaky network. It goes up and
down
regularly. Now that all of their Macs authenticate against the OS X
server
when the network goes down they have problems.
The solution we'd like to use is two NIC's in the machine. One NIC
will be
serving DHCP to a private network within the lab. The other NIC has
their
worldly address on the campus network.
I've gotten the NIC on the internal network to server up DHCP
addresses and
had the local Macs authenticate against it but it's VERY slow.
However,
even with NAT turned on I can't get those machines to see the outside
world.
I'm sure it's just a configuration problem on my part but I'm not sure
where
to look. I've tried making the gateway for the "internal" NIC the IP
of the
card going outside. I've turned on NAT and set it to the NIC that is
one
the "outside". However nothing seems to work.
Has anyone had any success doing this? Anyone have a page that
details how
to do this? I'd appreciate any help or suggestions.
Tim Wilkinson
ITC-ACHS
University of Virginia
email@hidden
_______________________________________________
maclabmanager mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/maclabmanager
Do not post admin requests to the list. They will be ignored.
maclabmanager mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/maclabmanager
Do not post admin requests to the list. They will be ignored.
--
/--
| Ben Staffin
perpetual nerd |
--/
| References: | |
| >Dual NIC's on an OS X server (From: "Timothy K. Wilkinson" <email@hidden>) | |
| >Re: Dual NIC's on an OS X server (From: Sellers <email@hidden>) | |
| >Re: Dual NIC's on an OS X server (From: Ben Staffin <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.