AFP slowdowns

AFP slowdowns, Dual G5 2Ghz, 4GB Ram.
Have 1 to 200 clients logging in, have a throughput of 4MB to 6MB/sec, then slows down to 200KB/sec. Takes the kids a while to login, word takes forever
Not sure what is casing the slowdown but its really ******* off me and the network users. 10.4.11, didn't have this problem till upgraded to 10.4.11.
Anyway does anyone have any ideas?
Message was edited by: Rob@Bis

Do you still have only 7% free on your RAID? If so, that is definitely a problem. I wage a constant battle for free space on my RAID. When it gets below 200GB (2.7TB RAID) it crawls.
I came to this discussion because I have a similar problem. I have a server ( Dual 2.3 GHz PPC, 2GB RAM) that is an AFP and FTP server. FTP is always fast, but AFP file transfers slow down after a while. I have found that changing the link speed on the network adapter fixes the issue temporarily; say a week or two. The server is in a DMZ attached to a gigabit switch. But the switch is connected to a 100 BaseT port at the firewall. I have changed the port speed on the switch that the server uses. I will see if this is a permanent fix.
I'm not sure if any of this is germane to the discussion, but I hope it helps.

Similar Messages

Updating Server 10.4.7 to 10.4.8 hangs every time

We are running a Mac network with around 150 clients with home and sharepoints on a Dual 2.3Ghz/8GB Ram XServe and have had some major issues with AFP slowdowns.
We are eager to get 10.4.8 installed, but every way we've tried it (locally using Software Update, Combo Update download, regular update download, installing from Server Admin from another computer), it just hangs either at "Locating the software to update" or during the middle of the installation progress.
Can anybody help, and if so what other info do you need? (logs, etc)
Thanks.
jon
XServe Dual 2.3Ghz/8GB Ram Mac OS X (10.4.7)

Sorry I haven't updated this, I forget that it doesn't send an email when someone replies. We were able to install the update using Server Admin from a different computer. Don't ask me why this worked, but somehow it did. We are still having an issue with the server which we were hoping would be cured by this, but I will detail that in an AFP thread.
Thanks!
jon

Significant slowdown of Time Machine after upgrade to Lion; indexing problem

After upgrading to Lion over the weekend I notice a significant slowdown of Time Machine processing. I assumed the first backup or two would take some time but it's been a couple of days. The process always hangs up at the "Indexing backup" stage. It takes a couple of hours to finish.
I found several threads relating to slowed down backups on Lion, most seem to hang at the "Preparing" stage (not the same symptom) but I did find some good diagnostic pointers. I installed the widget to see what kind of messages were being produced and found a few dozen "Waiting for index to be ready (100)" messages at the end of the stream. Further research - this is not a good thing :-) It seems a couple of such messages can be ok, but this many usually indicates a problem. I'm going to discount the possibility of a hardware failure because everything was perfectly fine up to the point I made the upgrade. Plus the prepare and copy seem to proceed at the expected speed (I watched the most recent cycle just to be sure).
Here is the full message log (it's still running at the moment):
Starting standard backup
Attempting to mount network destination URL: afp://Paul%[email protected]/Paul%20DiMarzio's%20Tim e%20Capsul
Mounted network destination at mountpoint: /Volumes/Paul DiMarzio's Time Capsul using URL: afp://Paul%[email protected]/Paul%20DiMarzio's%20Tim e%20Capsul
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Paul DiMarzio's Time Capsul/Paul DiMarzio’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
12.15 GB required (including padding), 490.69 GB available
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
I further found the advice and instructions on how to run the disk utility on the sparsebundle. I did a verify and repair, and the results came back that the drive appears to be ok (it did not say that it explicitly repaired anything).
But the problem remains.
I use a 1TB Time Capsule with plenty of free capacity (only half full). The TC and my MacBook are both hardwired into the home network, networking speed has never been an issue.
I'd sure hate to delete the backup file and start from scratch, there's over a year's worth of data there and I have, occassionally, wanted to go in there and pick up a downlevel or subsequently deleted file.
Any advice on other diagnostics or repair options to take? Thanks!
Paul

After posting I decided to keep trying to slog my way through the troubleshooting guide. Some of the steps are beyond my understanding but I did follow the advice in #D2 to delete the .Spotlight-V100 file from the sparsebundle. That action does seem to have done the trick, the backups are now completing in normal time. I ran a couple just to be sure. I've verified the backups with BackupLoupe and entered the Time Machine, all appears to be in order and as expected. The only odd side effect is that the backup volume is no longer ejected after completion but that might just be an artifact of all my mounting/de-mounting and playing with Finder. Anyway a very small price to pay for what looks to be a working system again.
Hopefully the good behavior will last through a few days and a few reboots :-)
ps - if you're reading this and don't know about the troublshooting guide it's here: http://web.me.com/pondini/Time_Machine/Troubleshooting.html (thanks pondini)

Dramatic slowdown of wifi during transmission

I have a 2009 Mac Pro (20 GB of RAM) with a 450 Mb Wifi card that has been working great. I have a 3rd Gen Time Capsule with the 2.4 and 5 GHz channels separate. I extend the network with a 3rd generation Airport Express that is also set to have separate 2.4 and 5 GHZ channels and I connect to the 5 GHZ channel. I share files from a 2012 i7 iMac connected by Ethernet to the Time Capsule and file sharing is also set up on the Mac Pro. I connect from the iMac to the Mac Pro via smb (also tried afp) in order to transfer a very large file (iPhoto Library that is 130 GB). When I drag the library over to the Mac Pro the transfer starts out very very fast - in fact the first 433 MB transfer over in just a few minutes and I am seeing transfers running from 4.5 to 2 MB/Sec. Then, about the time I get to 433 to 480 MB the transfer rate slows down to to about 140 KB/s and just stays there. I have killed and rejoined the 5Ghz channel (no nearby networks are using the same channel number for the 5 GHz channel) with the same result. Nothing is running on the Mac Pro or on the iMac that started to slow things down. And yet I have done this 3 times now with the same results. The Wifi report shows no congested network and yet this dramatic slowdown always occurs and sticks to the lower rate. Both machines are running Mavericks 10.9.5.
Anyone have an idea what might be going on and how I might attack it?
TIA

Does the same thing happen with a direct Ethernet connection? What about transfers in the other direction?

Using an Xserve AFP Share as a 'Scratch Disk'

Many thanks in advance for any advice anyone can give me.
I run a 100 client network at a media college where i work, and all of our students login to clients with Open Directory and their User Shared folder is shared via AFP.
Our students currently each have a portable firewire hard drive to store 'Final Cut Express' projects on. Long story short, they have to go, and we need a networked solution, effectively setting the Final Cut scratch disk settings to an AFP sharepoint.
Now on paper this SHOULD be possible. In Final Cut Express they only work with DV-PAL, which is around 30-35mbit/sec, we have a 1gbit/sec CAT6 network, and only a maximum of 12 students will be working on video at any one time. Our main storage XServe Intel server (2008 model) has 2 link aggregated 1gbit/sec ports effectively giving us 2gbit/sec. Our switches are not cheap unmanaged switches but proper rack mounted managed switches costing £4000/$6000 each.
Now as i said on paper this should be possible, but would it work in practice? I've tried a few tests with some test setups, and everything seems nice and fast so far, but of course reality is very different.
A lot of people will say that we need fibre networking and massive RAID arrays, but we simply cannot afford it. We're stuck with what we've got.
The best we could probably afford is an 'Xserve RAID Card' and then setup RAID 0 across our 3 SATA Apple Drive modules in our XServe, would that improve performance that much for FCE compared to the software RAID we currently have setup?
Is the whole idea ridiculous?
Thanks again for any help you can give me.

Going back to CS, I tested this on a Toshiba laptop. It worked, with about a 20% slowdown, IIRC. Could not find my benchmarks (probably still on that old Toshiba).
I agree with Chris - way too slow, and with rapid reads/writes, USB 2.0 devices are prone to errors, especially the dreaded Delayed Write Error. That can be death with image, or video editing.
Using eSATA is a much, much better solution, and I find that FW-800 works OK (though I have never needed to put the PS Scratch Disks on it), even doing intensive video editing.
Good luck,
hunt

Mac Server slowdown

Can anyone tell from these logs if something is causing our major slowdown?
Mac OS Server error log:
to repair
Apr 23 10:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 10:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 11:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 11:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 11:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 11:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 12:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 12:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 12:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 12:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 13:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 13:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 13:38:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 13:38:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 14:08:53 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 14:08:53 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 14:14:11 Xserve shutdown: halt by admin:
Apr 23 14:14:13 Xserve SystemStarter[1860]: authentication service (1887) did not complete successfully
Apr 23 14:14:13 Xserve SystemStarter[1860]: IP Failover (1893) did not complete successfully
Apr 23 14:14:17 Xserve SystemStarter[1860]: The following StartupItems failed to properly start:
Apr 23 14:17:11 localhost kernel[0]: standard timeslicing quantum is 10000 us
Apr 23 14:17:11 localhost memberd[47]: memberd starting up
Apr 23 14:17:11 localhost kernel[0]: vmpagebootstrap: 509395 free pages
Apr 23 14:17:11 localhost kernel[0]: migtable_maxdispl = 70
Apr 23 14:17:11 localhost kernel[0]: 94 prelinked modules
Apr 23 14:17:11 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Apr 23 14:17:11 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Apr 23 14:17:11 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Apr 23 14:17:11 localhost kernel[0]: DART enabled
Apr 23 14:17:11 localhost kernel[0]: Enabling ECC Error Notifications
Apr 23 14:17:11 localhost kernel[0]: FireWire (OHCI) Apple ID 42 built-in now active, GUID 001124ff fe407782; max speed s800.
Apr 23 14:17:11 localhost kernel[0]: Security auditing service present
Apr 23 14:17:11 localhost kernel[0]: BSM auditing present
Apr 23 14:17:11 localhost kernel[0]: disabled
Apr 23 14:17:11 localhost kernel[0]: rooting via boot-uuid from /chosen: A46C5BEB-0025-332C-AF80-D55B58D3C245
Apr 23 14:17:11 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Apr 23 14:17:11 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@7/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@1/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/Hitachi HDS722580VLSA80 Media/IOApplePartitionScheme/AppleHFS_Untitled2@3
Apr 23 14:17:11 localhost kernel[0]: BSD root: disk1s3, major 14, minor 4
Apr 23 14:17:11 localhost kernel[0]: hfs mount: enabling extended security on Server HD10.3
Apr 23 14:17:11 localhost DirectoryService[52]: Launched version 2.1 (v353.2)
Apr 23 14:17:11 localhost kernel[0]: Jettisoning kernel linker.
Apr 23 14:17:11 localhost mDNSResponder-107.4 (May 4 2006 16: 34:29)[37]: starting
Apr 23 14:17:11 localhost kernel[0]: Resetting IOCatalogue.
Apr 23 14:17:11 localhost lookupd[51]: lookupd (version 369.5) starting - Mon Apr 23 14:17:11 2007
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 0
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: Matching service count = 11
Apr 23 14:17:11 localhost kernel[0]: AppleRS232Serial: 442b5020 80013020 chip base, virtual, physical
Apr 23 14:17:11 localhost kernel[0]: IOPlatformControl::registerDriver Control Driver AppleSlewClock did not supply target-value, using default
Apr 23 14:17:12 localhost kernel[0]: BCM5701Enet: Ethernet address 00:0d:93:9d:7d:a1
Apr 23 14:17:12 localhost kernel[0]: BCM5701Enet: Ethernet address 00:0d:93:9d:7d:a2
Apr 23 14:17:12 localhost watchdogtimerd: Automatic reboot timer enabled.\n
Apr 23 14:17:12 localhost diskarbitrationd[46]: disk1s3 hfs A46C5BEB-0025-332C-AF80-D55B58D3C245 Server HD10.3 /
Apr 23 14:17:12 localhost lookupd[71]: lookupd (version 369.5) starting - Mon Apr 23 14:17:12 2007
Apr 23 14:17:12 localhost kernel[0]: hfs mount: enabling extended security on Server HD10.4
Apr 23 14:17:12 localhost diskarbitrationd[46]: disk0s3 hfs E5B80404-28D2-3668-86E8-0CF43635983F Server HD10.4 /Volumes/Server HD10.4
Apr 23 14:17:13 localhost kernel[0]: ATY,BlueStar: vram [9c000000:04000000]
Apr 23 14:17:13 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Apr 23 14:17:13 localhost configd[44]: AppleTalk startup
Apr 23 14:17:13 Xserve configd[44]: setting hostname to "Xserve.local"
Apr 23 14:17:13 Xserve loginwindow[79]: Login Window Started Security Agent
Apr 23 14:17:15 Xserve mDNSResponder: Adding browse domain local.
Apr 23 14:17:16 Xserve kernel[0]: AppleBCM5701Ethernet - en0 link active, 1000-Mbit, full duplex, symmetric flow control enabled
Apr 23 14:17:18 Xserve configd[44]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Apr 23 14:17:18 Xserve configd[44]: posting notification com.apple.system.config.network_change
Apr 23 14:17:18 Xserve lookupd[91]: lookupd (version 369.5) starting - Mon Apr 23 14:17:18 2007
Apr 23 14:17:24 Xserve /usr/sbin/serialnumberd[195]: serialnumberd: Firewall rule #1 added to allow port 626.
Apr 23 14:17:28 Xserve /usr/sbin/serveradmin: servermgr_ipfilter:ipfw config:Notice:Disabled firewall
Apr 23 14:17:33 Xserve ntpdate[105]: getnetnum: "time.apple.com" invalid host number, line ignored
Apr 23 14:17:33 Xserve ntpdate[105]: no servers can be used, exiting
Apr 23 14:17:33 Xserve configd[44]: target=enable-network: disabled
Apr 23 14:17:33 Xserve servermgrd: servermgr_dns: no name available via DNS for 192.168.100.102
Apr 23 14:17:33 Xserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
Apr 23 14:17:34 Xserve configd[44]: AppleTalk startup failed, status = 92 (retrying)
Apr 23 14:17:35 Xserve ntpd_initres[245]: couldn't resolve `time.apple.com', giving up on it
Apr 23 14:17:35 Xserve configd[44]: AppleTalk startup
Apr 23 14:17:41 Xserve configd[44]: AppleTalk startup complete
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is down for SCSI Domain = 0.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is down for SCSI Domain = 1.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 5 (External Bus Reset) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: External Bus Reset for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 0.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 8 (Loop State Change) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Loop Initialization Packet for SCSI Domain = 1.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is active for SCSI Domain = 0.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 7 (Link Status Change) for SCSI Domain = 1
Apr 23 14:18:00 Xserve kernel[0]: FusionFC: Link is active for SCSI Domain = 1.
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 0
Apr 23 14:18:00 Xserve kernel[0]: FusionMPT: Notification = 6 (Rescan) for SCSI Domain = 1
Apr 23 14:18:01 Xserve kernel[0]: hfs mount: enabling extended security on RamVol
Apr 23 14:18:01 Xserve diskarbitrationd[46]: disk2s10 hfs FBF4AE84-A5B4-3901-8C4E-8369B12FB0D7 RamVol /Volumes/RamVol
Apr 23 14:18:01 Xserve kernel[0]: hfs mount: enabling extended security on JobVol
Apr 23 14:18:01 Xserve diskarbitrationd[46]: disk3s10 hfs EEABEBCD-B306-36E4-87CA-6A84907FF6FF JobVol /Volumes/JobVol
Here is the Mac OS X Windows Error log:
peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 11:19:32, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 11:26:06, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 11:51:37, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 11:54:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 12:23:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 12:26:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 12:58:52, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 13:27:35, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 13:30:53, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 13:58:42, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 13:58:42, 0] pdbods.c:odssamgetsampwnam(2329)
odssam_getsampwnam: [0]getsam_recordattributes dsRecTypeStandard:Users no account for 'donh'!
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2007/04/23 13:59:36, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:get_peeraddr(1016)
getpeername failed. Error was Socket is not connected
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:write_socketdata(446)
writesocketdata: write failure. Error = Broken pipe
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:writesocket(471)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2007/04/23 14:02:54, 0] /SourceCache/samba/samba-100.4/samba/source/lib/utilsock.c:sendsmb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2007/04/23 14:17:18, 0] /SourceCache/samba/samba-100.4/samba/source/smbd/server.c:main(789)
smbd version 3.0.10 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004

Hi
Add a DNS record using the relevant DNS snap in tool on the AD Server for the mac server as it should improve server and network performance. OSX and especially OSX Server is absolutely dependent on a properly configured and tested DNS Service running somewhere. Apple recommend it as good practice even if you are just running simple file services like AFP.

Multiple simutaneously logged in users accessing AFP home directories?

Hi,
Many of our problems are described in this guy's blog:
http://alblue.blogspot.com/2006/08/rantmac-migrating-from-afp-to-nfs.html
The basic capability we want is to have multiple simultaneously logged in users to have access to their AFP mounted home directory, which is configured in a sane, out-of-the box setup using WGM and Server Admin.
Multiple user access could take the form of FUS (fast user switching), or simply allowing a user to SSH into a machine that another user is already logged into and expect to be able to manipulate the contents of her home directory.
From my extensive searches, I have no reason to believe this is currently possible with 10.4 Server and AFP.
(here's the official word from apple: http://docs.info.apple.com/article.html?artnum=25581)
I've read that using NFS home directories will work, though.
I want to believe that Apple has a solution for this by now (it's been almost a year since we first had difficulty), or at least a sanctioned workaround. If Apple doesn't have one, maybe someone else has come up with something clever. I find it hard to believe that more people haven't wanted this capability! (not being able to easily search the discussion boards doesn't help, though...)
Thanks for your help!
Adam

Parallels Issue. Track at http://forum.parallels.com/showthread.php?p=135585

Attn: ALL APPLE PORTABLE OWNERS -Macbook Pro, MacBook Air Apple portable slowdown / kernel high CPU solution

Attn: ALL APPLE PORTABLE OWNERS -MacBook Pro, MacBook Air, Mac mini slowdown kernel / high CPU use problem and solution.
YOU COULD FRY YOUR COMPUTER IF YOU DO NOT FIX THIS PROBLEM SO PLEASE READ THIS ENTIRE MESSAGE!
YOUR MAC WILL THANK YOU
Hey all.
Like many of you I've got a newer Apple portable which slows down to an unusable level for an unknown reason. In my case a 13" mid 2009 Intel MacBook Pro Core 2 duo laptop. After many failed attempts to figure out what this nutty problem is I have discovered the problem, the solution and I have solved this for my own MacBook Pro. Since this fix it has been working immediately and consistently -without issue
I am sharing this with you in hopes that you to can fix your Apple portable yourself or so you know what to tell the Apple techs so they can quickly fix your Mac from this wacky and unfortunate kernel CPU hogging problem.
User Software Symptoms :
Your Apple portable computer periodically for an unknown reason slows down making everything frustratingly slow. This happens even when running previous apps that were never a problem; things that your Mac should be able to handle easily but for some reason now it can't.
Slowdown most often happens during high CPU use such as gaming, video playback/editing, etc. or when running multiple apps (even non CPU intensive apps) at the same time.
Possible Hardware Symptoms:
Your computer is making more noise than it did previously.
Your computer occasionally makes more noise but then gets quieter.
Your computer is always extremely quiet (too quiet) even during high CPU apps -worst case scenario.
It feels hotter than it normally does. Test: After several minutes of the slowness/high kernel CPU touch the computer to feel if it's hotter than normal.
Looking at Activity Monitor (in the Utilities folder) shows the kernel_task is going bonkers eating up CPU but you have no idea why.
After trying many different things to solve this problem such as :
PR ram reset, SMC reset, fresh OS install of 10.5 and 10.6 on external hard-drives, calling and speaking to various Apple tech people who had no ideas/solutions, etc. I had no luck.
Btw, if you're having the symptoms I've decscribed above I would not run the Apple Hardware check (read below as to why). You could fry your Mac!
After much testing I found the problem :
It is my belief that "recent" Apple portable computers are using low quality internal fans which soon stop working!
Fail time period seems to be about 1.0 years to 2.5 years of use but this fail rate could vary depending on use.
First noticeable symptoms (depending on what you notice) could be computer slowdown or your fan is making more noise than it normally does. This is your fan's lubrication slowly eroding making your fan spin slower and less smooth resulting in the louder noise and slower rpm spin speed. The slower fan spin speed means less cooling is happening for your computer. The effect on your computer is that the CPU and other chips are heating up! Overheating to be more specific. When your computer's chips overheat they get wonky and screw things up. Most often this seems to have the effect of making the kernel hog CPU resulting in a frustratingly slow user experience! Heat kills computer chips and it is extremely bad for them. Extreme overheat or repeated overheating has been said to shorten the life of computer chips or in extreme cases even fry them completely!
The longer this goes on without being fixed your fan loses more lubrication and spins slower and slower cooling lesser and lesser resulting in your CPU heating up more and more possibly shortening the life of your Mac! Eventually your fan will stop completely and you could fry your chips! My fan stopped completely and my MBP was running very quietly, too quietly. Luckily I did not fry my chips because I was avoiding using high CPU apps because I knew something was wrong due to the massive slow down and wonkiness when I'd run them.
Side Note:I'm a bit concerned about all those Mac mini servers which may be using the same defective low quality fans which cannot be easily serviced by their owners as they are co-located in some server facility. One positive thing is those facilities are usually well airconditioned keeping temps low.
I suggest you do not run the Apple hardware test if you suspect your computer is overheating because the hardware test can seriously heat up your Mac! I tried running this test and my Mac got so hot I had to shut it down forcefully and I was concerned I damaged the chips. If you want to run the Apple hardware check make sure your CPU temperature is ok and that your fan works well before you run the test.
IF YOU DON'T FIX THIS PROBLEM YOU COULD FRY YOUR COMPUTER DUE TO HEAT DAMAGE!
DO NOT IGNORE THIS PROBLEM YOUR MACS LIFE MAY DEPEND ON IT!
First you need to properly diagnose this problem and see if your CPU is getting to hot and you need to see if your fans are spinning at high rpms giving proper cooling, or if they are spinning at low rpms when running high intensive apps as your CPU temp increases.
TEST IF YOUR FAN(s) IS WORKING CORRECTLY :
Unfortunately Apple does not include CPU temperature reading software nor fan rpm speed software that I am aware of.
However, There are two free ways that I know of to check your CPU tempurature and your fan speed :
One app shows fan speed, and CPU heat, etc.
One app shows fan speed, CPU heat and allows you to adjust your fan speed settings.
One app is a dashboard widget, the other is a system preference.
I suggest you download both of these to check your computer statistics.
http://www.eidac.de/?p=134
http://www.islayer.com/apps/istatpro/
http://fan-control.en.softonic.com/mac
I am not exactly sure what proper CPU temperatures are for the different Apple computers and this will change given different CPU loads.
My MBP doesn't seem to function properly with anything around 90 degrees or higher (celcius).
It seems when the fan is operating normally the CPU temp should not stay above 78 degrees even under heavy load, at least with the apps I'm running in the room temperature I'm in.
I can post back later with more specific temps under longer load, etc. but I wanted to get this post up for people to read as soon as possible so they don't fry their Macs.
If a bad fan is your problem :
THERE ARE ONLY TWO SOLUTIONS FOR THIS PROBLEM :
Fix or replace your fan so it cools the CPU and other chips properly.
I fixed my fan myself and I didn't need to buy a new one. Total cost was about $8.00 because I had to buy a #00 sized screwdriver and had it shipped to me. Price includes shipping.
On my mid 2009 model MacBook Pro fixing the fan was incredibly easy :
Before I started doing this I wasn't 100% this was the problem so I decided to try to fix my fan instead of ordering a new one and replacing it. As it turns out I didn't need a new fan, I only needed to clean the existing fan and relube it's axl so it could spin easier like when it was new. It also didn't make sense to buy a brand new fan from an Apple authorized parts reseller selling me the same low quality fan for $49.00 which would probably fail in 2 years again. Prices for new comparable fans from different manufactures range from about $15.00 USD + shipping to around $49.00 USD + shipping depending on where you order them from and what brand you get.
How to fix / replace your internal fan on a mid 2009 MacBook Pro :
Please note : I am not a hardware technician, nor expert. If you decide to fix your Mac yourself you do so at your own risk through no fault of my own. Prior to opening up your Mac you should google around and learn how to do it correctly and safely so you won't damage your Mac. For example, it is possible for you to damage your Mac by static electricity from your body. To avoid this I believe proper procedure is that you wear a 'ground strap' (around your wrist) which you clip to your Mac's metal body so your body will not excude a charge into your Mac. I believe the idea here is to keep your body's charge level and your Mac's similar. Since I do not have a ground strap and fixing/replacing the fan doesn't require touching any chips I did not wear a ground strap during my fan fix. What I did was periodically repeatedly touch the metal case of my MBP hoping that would be enough and it was. Avoid unecessary actions that can build up a static charge in you. Once I started the repair I did not walk around the room building up an electrical charge in my body. Walking on carpet can often build up a large charge in us so it is better to be avoided while working on your Mac. Certain clothing can build up static charges. Combing hair, etc. If you need to get up from your repair when you come back make sure you first touch the Mac's metal case and not anything inside.
Now that we're done with the scary paranoia, below you will find some instructions on how I fixed my MBP's internal fan
Before you begin:
Check out someone's video (not mine) on how to remove / replace the fan (but not take it apart and repair it):
http://www.youtube.com/watch?v=AghE9newvbs
Check out someone's web page (not mine) on how to replace the fan in a mid 2009 MacBook Pro:
http://www.ifixit.com/Guide/Installing-MacBook-Pro-13-Inch-Unibody-Mid-2009-Fan/ 1338/1
How to repair your mid 2009 MacBook Pro fan:
Make sure you are in a 'secure' environment. No pets, no kids running around, no drinks near the Mac, etc.
Make sure your computer is unplugged from it's power supply and turned off. NOT slept. Totally off / powered down.
1. Get a size #00 phillips screwdriver (Hobby store, Radioshack, Amazon).
2. Open up your MBP by unscrewing the bottom (yes flip it over so it's resting upsidedown). Note where each screw goes because some are different lengths. I placed each one around my MBP where they go, insuring I know their order (don't jumble them up). Note which direction your MBP is facing when it's upside down so if you spin it around while working on it you still know where the screws go.
2b. Some recommend removing the MBP's battery but I didn't do this step. You probably should, just to be safe. Follow the online instructions from the web page I listed about disconnecting the battery.
3. Unscrew the fan's 3 holding screws.
4. Unplug the fan's electrical connection (lift it straight up off the board). If you need to you can try to pry it up while you lift with a non metal/non electrical conductive object like a spudger if you have one or -perhaps a pen cap. Before you remove it, look closely at how it's attached so when you put it back on you won't wonder if you're doing it correctly. There's only one way it can go because it cannot fit 'the wrong way' but looking at it closely will make you feel more confident popping it back on when the time comes.
5. Remove the fan - it easily lifts out.
6. Take the fan apart by unscrewing it's one screw then unlatching the plastic clips which hold it together.
7. Seperate the fan blades from the housing. Lift the fan blades off of the fan housing by pulling it straight out away from the housing.
8. Clean off the dust that's gathered. A can of compressed air helps here (I didn't have one). I used a little brush from my electric shaver kit which worked well. Once you've removed all the dust from the fan and surrounding areas proceed to the next step.
9. Reapply new lubrication. You need less than 1 drop. Be sure it covers the entire fan blade axl as this is what needs to be well lubricated. Make sure there isn't excess oil that will fly around when the axl/fan spins at high rpms. I used the only oil I had which was olive oil (for cooking!) but I do not suggest this. At the time I was doing this I didn't know my fan was the problem so I wasn't even sure I was going to relube it. You should probably use something more appropriate perhaps like 3 in 1 oil. A good idea would be to call the manufatures of these little fans and ask them. Maybe a hobby store knows of good lubricants for these purposes?
DO NOT use things like WD 40 as it's not a long term lubricant or so I've read.
10. Once your fan is now clean and oiled (make sure there isn't too much oil) reassmble the fan.
Push the fan blades/axl back into the housing shaft. Give it a few spins with your finger.
Screw together the fan housing then reclip the clips.
11. Place the now reassembled fan back into your Mac and screw it in place (3 screws).
12. Reattach the fan's electrical wiring by gently pushing it into place. Make sure you've got the right end facing down before you push it in place.
13. Once your Mac's internals are clean and reassembled, place the rear cover back on your Mac and screw it in place.
14. Double check you didn't forget anything like screws, tools, etc.
15. Boot up your Mac and monitor the temperature and fan speed using those programs.
Compare the previous temps/fan speed to the current temp/fan speed.
Run a high CPU intensive app where your computer has been slowing down.
You should now have a happy Mac
If you have this problem and this solution fixed it for you please post in this thread letting me and everyone else know!
Hope that helps.

Thanks for your lengthy reminder dude, I have a similar Mac with yours. I suspect its a software fault because it happens after I upgraded to Lion, 10.7.2.

Can connect via SMB but not AFP....

Hi Guys,
Firstly, please let me apologise in case im being really stupid (highly likely! )
I have a mixed environment in which i have some iMacs (running Mavericks) and some Mac Pros (Running Mountain Lion 10.8.5). When connencting to the XServe using AFP, some get an error. I will go throught the steps i follow.
- From Finder, Go>Connect to Server..>afp://10.***.**.**>Connect
- I enter the login credentials and select Connect
- It gives me the option to select which volume to mount. I select Volume 1 and select OK
- Error - There was a problem connecting to the server "10.---.--.--". You do not have permission to access this server
When trying to access the server suing SMB instead of AFP (using the same credentials) it connects fine.
The issue with SMB is that for some reason, some of the folders wont show through SMB (no idea why)
The problem is affecting one imac on Mavericks and two Mac Pros on Mountain Lion. If i attempt to login using SMB on any machines which work fine with AFP, they will connect but after that, they wont revertback to AFP. They get the same error as above.
Any idea whats causing this?If any of the above causes confusion, feel free to shout at me and i will try to clear anything up.
Really appreciaste the help guys!
Pami

You'll need to connect your modem to your AEBS WAN port, configure your AEBS with the Airport Admin Utility, setting up the PPOE to properly log into your modem connection.
You should set up your mac to us DHCP (not PPOE).
THis should allow you to use either the ethernet port or wireless from your AEBS.
I hope this helps!

Photoshop/Bridge CS4 problem with AFP shares

Hello,
I have recently purchased Photoshop CS4 and encountered the following problem: when opening images from a NAS share connected via AFP using File/Open command, Photoshop will correctly display the list of files but Open command in the File open dialog remains disabled after a file is selected from the list.However, I can open the same file by dragging and dropping it from the Finder to the Photoshop Dock icon or later using the Open recent menu command.
Similar problem is visible in Bridge: it will not display the image thumbnails from any of the subfolders in the network share.
I am using Leopard with the latest updates, I have a read/write permissions to the network share and Photoshop/Bridge are the only applications that have problems browsing/opening files from the network share. The NAS unit is a Synology DS-107+ with the latest official firmware.
Futhermore, I have noticed that I can work around the problem by opening the same directory in Finder. After the image thumbnails are visible in Finder, both Photoshop and Bridge will correctly open all files in that directory but opening files from other directories still has the problem.
Does anyone have any idea on what might be causing this strange problem?

This is the boilerplate text I use in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):
If you are opening files over a network or saving them to a network server, please cease and desist immediately in the event you are currently experiencing problems with one or more files. Working across a network is not supported.
See:
http://www.adobe.com/support/techdocs/322391.html
Copy the CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work. It should.
Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.
If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.
When problems arise, a lot of valuable work can be lost.

Why does a Login Error occur: "AFP Client wants to use Keychain Login"?

I have three people in my house with separate logins. We are currently using two desktop G4s which are networked via 1000 Base T. When the users login to one of the Macs, they must enter their passwords twice. Once for the AppleShare login and then a second time for the KeyChain Login.
If I attempt to unify the passwords, which are exactly the same, I will get a login error: "AFP Client wants to use Keychain Login". At this point, a dialogue box will appear looking for a password, but not accepting any kind of text at all. All I can do is reset the Mac, go into my admin login and remove the login.keychain file from the local Library folder to get back into the User account.
In my attempts to fix this, I have removed every preference file with the word "login" in it and re-logged in without success. I have also used the Keychain Access software to administer Keychain First Aid without success. Finally, I have deleted the keychain login in Keychain Access without success. I have done all of these separately and together without success.
This is only happening on one Mac. The Mac that has no files on it. All working files are stored on the other Mac and it does not have the same problem at all.
This is not a huge problem, but it is annoying. I would appreciate it if anybody knows anything about this and could shine some light on the situation.

Sorry about the delay from your last reply. I have been busy with work and studying for a licensing exam.
Anyway I tried the AppleJack Utility you suggested. It looked like it tidied up some things. But as for my particular issue, it did absolutely nothing.
Interestingly enough, you know when you aren't looking for something and that something just happens by accident? When I logged in the other day, I typed in the first login. The second dialogue came up immediately and I hit the cancel button instead of the OK button. When I was passed on to the Finder, the second login dialogue came up again. I typed in the password this time and checked the checkbox. When I relogged in, the problem vanished. I only waited this long to let you know to make sure the problem is gone and it is. I wish I would have thought of selecting the cancel button before. Sometimes solutions are simple like this one.
Thanks for your help.

Problem saving a Photoshop file from an AFP server

Hi All,
Just want to know if some of you guys are experiencing this and how you solved it.
Basically we have an AFP server and OD services. All mac clients are bound to OD and are using the OD account for logging in. Most of the user are using photoshop. However when one edits a file and wanted to save/replace it, photoshop generates an error saying its locked forcing phothsop users to do file SaveAs and rename the file. We have been doing the AFP server and editing photoshop directly through the network for almost 1 and 1/2 years but not experienced this issues until later that we added more users/employees in our network and this issue came up
The error is
Could not save "Photoshop File.psd" because the file is locked. Use the 'Get Info' command in the finder to unlock the file.
We are able to create folders/files to where the photoshop is saving and other applications seems to save/replace files fine except for photoshop.
Has anyone encounter this and how did you solve it?

I found the solution here, http://discussions.apple.com/message.jspa?messageID=4644850#4644850 and the steps are as follows,
In Workgroup Manager (OS X Server) select the group you want to apply the setting to, the choose Preferences.
Choose the "Details" tab and add .GlobalPreferences.plist
Clear all the settings, and add a new key called NSUmask, then choose "integer" with a value of 2
Next time your users for that group log in and they save a file it will be rw-rw-r
The default umask for Macs is 022 (rw-r--r--), this changes it to 002. I didn't try manually changing the default umask on the individual workstations, but I assume that would work also.
Kent

File Server/AFP gets slow after a week or so

Hi all,
I manage a file server at our office here, with around 20-30 users, running 10.3.9 server. Users connect via AFP for general office duties, but also remote-desktop into a windows server using Rdesktop via X11. They use SMB to access their files from the windows side.
I find after a week or so that logins to the shares, and general file access gets incredibly slow, and grinds to a halt eventually, but comes good after the server is rebooted.
It is usually quick to authenticate in any case, but takes an age to bring up the list of shares that the users can pick from (probably 10-15 at most depending on their permissions). Even after a fresh reboot it takes about 10 seconds to bring up the list of shares to pick from. Is there any way to fix this?
I find that is someone has their computer set to calculate folder sizes on a server drive/share it can make the server grind to a standstill, but even with everyone set up correctly it still goes slowly all by itself after a few days/weeks of running. Logging in via Remote Desktop becomes slow at this point too.
I've tried some of the tips in this thread below with only limited success.
http://discussions.apple.com/thread.jspa?threadID=343979&tstart=15
Any help is greatly appreciated

As you upgraded the router's firmware,reset the router for 30 seconds and reconfigure the router from scratch.
On the router setup page,Under the Wireless tab,click on the Advanced Wireless Settings...Change the Beacon Interval to 75, Change the Fragmentation Threshold to 2304,Change the RTS Threshold to 2307 and Click on Save Settings...

File sharing/AFP skips "connect as"

I have a Mac-Lion and several accounts, both user and admin. I turned file sharing on and selected AFP. I can connect from another Mac-Yosemite as expected - to any account on Mac-Lion by entering the password when prompted. With one exception.
I have an admin account xyz on Mac-Lion and an admin account xyz on Mac-Yosemite, different passwords. On Mac-Yosemite, in the account xyz when "connect to server", it skips the "connect as" prompt. Connects straight to xyz on MBP-Lion. However, this does happen vice-versa. I also tested other accounts, say abc on Mac-Lion and abc on Mac-Yosemite, admin or standard user. No problem, always goes to the "connect as" window and asks for a password.
I also changed the password of xyz on MBP Lion many times, and delete the keychain, restarted, etc. Also, MBP-Lion is off-cloud. Still thee is this mysterious one-way password-free connection between the two accounts. What could that be and how can I reset it?
Thanks in advance.

It turns out the iCloud causes this behavior. If I sign off iCloud in the account xyz on Mac-Yosemite, then I am prompted with the regular login window when I connect to Mac-Lion. So some setting on Mac-Lion grants password fee access to connections from account xyz on Mac-Yosemite as long as that account is logged in iCloud. (xyz on Mac-Lion used to be signed in the same iCloud account, but I signed out and reset the keychain). Any idea where that could be so that i can reset it?

File transfer: AFP vs FTP

Setup:
Cable modem to Linksys WRT54g broadcasting only in G only mode for PBG4.
AEBSn#1 in bridge mode via Ethernet from Linksys, N only mode, broadcasting wirelessly.
AEBSn#2 is wirelessly extending N-only from AEBSn#1, and is connected to a mini with external hard drive.
Using PBG4, if I mount a volume from the mini and transfer a file, transfer time is very slow: approx. 20 minutes for a 200MB file. If I FTP from PBG4 into the mini, transfer time is 2 minutes.
(I think the same happens if I use a Macbook Pro connected to the N-only network, but it's in for repairs right now, so I can't be sure.)
Any idea why the transfer times are so different b/w AFP and FTP and, more importantly, what I can do to remedy this? Thanks.

Same problem here. I have two AEBS Gigabit in bridge mode. Transfering a file via FTP or with Apple Remote Access (ARD) brings up to 3 MB/sec. Same file and same configuration connected via AFP only brings 60 kB/sec.
I hope somebody has an idea how to fix this.
Thanks in advance

AFP slowdowns

Similar Messages

Maybe you are looking for