User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4
Nick Kutzko wrote:
Oops, didn't realize it wasn't sending to the list when I hit reply.
Ok, so I'll answer all those in oder.
1) The OD master is a G5 Xserve with 2GB RAM running 10.5.1. Homes are
stored on that server.
More ram on this one might make a difference.
2) Yes, there is a replica server, a G4 Xserve with 2GB of RAM. This
server also shares a student applicans folder.
3) Yes, DNS is functioning properly. I've tested it several times and
everything resolves forward and back.
Where is DNS? On the XServe or somewhere else. I've seen slow DNS wreak havoc in cases like this.
4) The clients are a mix. There are G4 eMacs from 700MHz-1GHz, G5 iMacs,
Intel iMacs. All machines are running 10.5.1 (yeah, I know the 700s are
below the requirements, but it still runs fine).
5) There are no hubs or switches other than the Cisco 100baseT switches in
the data closets. We also use Cisco wireless Aps. There is no difference
between wired and wireless clients in regards to the problem I'm seeing.
Is there anyway you can beg/borrow/steal a gig switch for a while to see how that goes?
6) No, there is no possible way clients are trying to connect via anything
but the built-in ethernet or wireless. All machines were imaged using the
same image.
I would also like to add that the issue seems random. Sometimes, an entire
class will login just fine and the next will take 25 minutes. I have
noticed that the problem is worse when another team is using their laptops,
which would essentially mean about 60 clients trying to log in at the same
time, but that was never as large of a problem before Leopard. Actually,
those laptops are still running 10.4.9 or 10.4.10.
Try turning off the ARD client on the servers. I've run into an issue with this and I'm suspicious that it's the cause of some long standing AFP issues some folks are having.
