Well, the point isn't about disabling Appletalk. It's a necessary part of that network for the time being. I'm trying to figure out why it has mysteriously slowed down...
Main Topics
Browse All TopicsI have two AppleshareIP 6.3.2 servers sitting on one end of the room, and two Mac OS X 10.2 workstations on the other side of the room. Whenever I try to connect to the servers and copy files, it's ridiculously slow. 100MB worth of files takes two hours.
The problem seems to have gotten progressively worse. It's always been a bit slow, which I blamed on using Appletalk (a holdover from when we had more workstations running OS 9 and lower). Now it's just unusable. I've restarted the servers and workstations numerous times. Nothing has changed hardware wise with the hubs or the switches or the workstations or the servers.
Now, if I copy files between one server to another - which are on the same switch - it's lightning fast. If I string a cable across the room and plug a workstation into that same switch, copy speeds are also just as fast. To me this kind of rules out Appleshare IP server configuration problems, or a problem with that switch.
There is a pretty new Netgear hub in the network closet which handles all the traffic from all the wall jacks. OS X machines go into the wall, go up to the hub. Server traffic goes into their switch, and up to the hub.
TCP/IP speed tests from any system in that room are just as fast as ever, which makes me think that it's not a Netgear hub problem. I have a couple of Windows XP PCs in that room which don't have any speed issues to and from my Windows 2000 network. OS X straight TCP/IP stuff, like FTP and web browsing and downloading, is fast and fine. Those Windows PCS even connect and copy to those AppleshareIP servers (via windows file sharing protocol built into Appleshare IP) without any speed problems, and they're not on the same switch as the servers.
I hook up another OS 9.2.2 system in that room, and try to copy to/from the OSX workstations via plain old File Sharing and the speeds are terrible. This all makes me think that something has gone terribly wrong with the Appletalk protocol. I figure I would simply turn off Appletalk from the server side, disable it on the OS X machines, and connect everything via straight TCP/IP - but then the workstations never connect to the servers, they time out with an error. Even so, this is not an ideal solution as I still have a couple of older computers that sometimes need to be plugged in and get on the network via Appletalk.
For now I'm going to move the switch to the other side of the room and connect both OSX workstations directly into it. However that can only be a temporary solution, and I'm wondering what else I can do or what else I can look into.
Any ideas from any Mac experts?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Well, I eventually replaced a hub with a switch in the upstairs network closet. No idea why that would make a difference, but the "Collisions" meter on the hub was usually pretty high, and the new switch solved the problem. It's still frustrating, because if I had nothing but an old Appletalk network - or legacy printers or whatnot - that did not give me any TCP/IP options, I'd still have the problem. Something was just flooding the hell out of the network with apparently bad appletalk packets, causing the delay.
I'm going to leave this topic open for a few more days to see if anyone has any ideas regarding the Appletalk only side of this problem... that info might come in useful if I decide to ever hook up any legacy printers or whatnot.
Are you sharing any firewire drives on those slow desktops?
If so, check for an odd clicking niose. I had that happen once when a new firewire driver coflicted with a different make firewire drive on the network. That drive slowed to a crawl and everything else on the network slowed down too. When I pulled the bad drive things got back up (it made a clicking noise as it tried to work). It had to be sent in for warranty repair. Came back ok. I don't use the drive or driver that messed things up on the network.
Also, or maybe first, I did have a couple OS9 machines that just would not log in without a terrible wait. It was after some new wires were dropped in from the ceiling. The wire guys said everything was fine, tested the wires and they showed as good. No matter, I jumped a line from a different drop point and things worked great. Must have been something the wires ran past in the ceiling those machines didn't like. Electronic disturbance maybe. Didn't show up on the instruments they used. But it was definitely not happening before they ran new lines.
Worth a try,
Business Accounts
Answer for Membership
by: WIF567Posted on 2004-02-01 at 10:40:06ID: 10247710
Try shutting off the connect via Appletalk option on server and then try connecting from the connect to server using the ip address of the server. It could be that you are using the orignal appletalkj protocol to connect which is slower than appletalk over IP.