SLOW Login when Network Unavailable

Hello all, this is my first post on Apple Discussions. I recently upgraded my MBP from OS X 10.4 to 10.5.4 Leopard. When I am at work and plugged into the network, everything runs fine. When I am home, however, OS X takes over 5 minutes to log me in. I am assuming that this is because the system is looking for the network which is unavailable. 10.4 did not do this to me.
Has anyone had this problem? Can anyone offer a solution or at least a work-around? Thanks in advance for your help.

There are two things I did to fix this issue, both from other posts which I didn't bookmark and can't reference.
If you are a part of a windows domain, make sure in the Directory Utility, under Services, Active Directory you have chosen to create mobile account at login. This will cache all of your credentials, login information, etc.
Under Search Policy, make sure /Active Directory/All Domains is listed. It is the last choice for me, /Local/Default and /BSD/Local are first.
What I think is happening is that it's looking for either DNS information or directory information or user credentials. I have also unjoined and rejoined the domain after making sure mobile account was checked and that seemed to make things faster.
Also, double check your service order in your network system preferences and see what order it's looking for an internet/network connection.

Similar Messages

Windows XP slow login when plugged into external network

Hi,
A about 9 months ago XP SP3 was rolled out with an image upgrade, since then there has been rumblings of slow logins when connected to an external network (eg a ADSL modem at home) but no evidence etc.
About the environment
Windows XP SP3
Novell Client 4.91 SP5 IR1
ZENworks 7
Roaming profiles with folder redirection for Desktop, My Documents.
We have just rolled out another upgrade to a number of base apps and this has come up again but with some evidence and some time for me to investigate.
What I have discovered is this:
When a laptop is plugged into an external network (I have used an ADSL network here at work to test this) the login for a user takes about 2 minutes with SP2 and about 3.5 minutes with SP3. This is done checking the workstation only box.
This happens consistently on workstations.
What I have done to narrow this down is as follows:
Removed ZENworks 7 agent. Login times improved dramatically
Installed older versions of ZENworks agent, all results the same, extra slow logins experienced with all versions tried.
Installed ZEN agent and removed Novell Client, still the same slow login.
Created a local user, fast logins experienced even with the ZEN agent installed.
Disabled all ZEN services and logged in with an eDir account, slow logins all the same.
Removed all policies from user and workstations, this made a slight difference but nothing much
Disabled ZEN, no difference either
Disabled NMAS, no difference either
Removed some IDM installer we had rolled at the same time, no difference.
Here are the timed results.
XP with SP2 on corporate network = 30 secs
XP with SP3 on corporate network = 35 secs
XP with SP2 WS only ticked and ADSL modem plugged in = 2min
XP with SP3 WS only ticked and ADSL modem plugged in = 3min 26 secs
XP with SP3 WS only ticked and ADSL modem NOT plugged in = 45 secs
XP with SP3 local user with ADSL modem = 45 secs
So it's down to the ZEN agent really, but the update to SP3 hasn't helped either.
I enabled debug logging and got the following from the log, usernames and servers have been removed:
NWGINA log:
01/31/2011 08:57:02:062 This machine is *NOT* configured to store profiles using NetWare!
01/31/2011 08:57:02:062 Testing for a ZEN cached profile path for this Windows user
01/31/2011 08:57:02:062 GinaRetrieveUsersCachedRoamingProfilePath entered
01/31/2011 08:57:02:062 User's cached profile is: \\SERVER\VOL1\Users\"USERNAME"\Windows NT 5.1 Workstation Profile
01/31/2011 08:57:02:062 GinaRetrieveUsersCachedRoamingProfilePath returning: 1
01/31/2011 08:57:02:062 Testing for NT configured policy file
01/31/2011 08:57:02:062 Didn't find an NT Configured Policy
01/31/2011 08:57:02:062 User logged onto the local machine NT policies are *NOT* configured!
01/31/2011 08:57:02:062
01/31/2011 08:57:02:062 Calling MS API LoadUserProfile
01/31/2011 09:00:16:187 Returned from calling MS API LoadUserProfile
01/31/2011 09:00:16:187 CheckIfSpecialGroupPolicyRunIsRequired entered.
01/31/2011 09:00:16:187 CheckIfSpecialGroupPolicyRunIsRequired returning TRUE
01/31/2011 09:00:16:187 Calling WMGRPPOL in cleanup situation
01/31/2011 09:00:16:187 WMCallUserPolicyHelperDLL Entered.
01/31/2011 09:00:16:187 szHelperName returned: WMPM.DLL
01/31/2011 09:00:16:187 szHelperName returned: WMPOLHLP.DLL
01/31/2011 09:00:16:187 szHelperName returned: WMPRTNT.DLL
01/31/2011 09:00:16:187 szHelperName returned: WMUSPOL.DLL
01/31/2011 09:00:16:187 szHelperName returned: WMGRPPOL.DLL
userenv.log:
USERENV(400.940) 08:56:39:203 GPOThread: Next refresh will happen in 95 minutes
USERENV(400.404) 08:57:02:062 LoadUserProfile: Yes, we can impersonate the user. Running as self
USERENV(400.404) 08:57:02:062 ================================================== =======
USERENV(400.404) 08:57:02:062 LoadUserProfile: Entering, hToken = <0x998>, lpProfileInfo = 0x6ea18
USERENV(400.404) 08:57:02:062 LoadUserProfile: lpProfileInfo->dwFlags = <0x1>
USERENV(400.404) 08:57:02:062 LoadUserProfile: lpProfileInfo->lpUserName = <USERNAME>
USERENV(400.404) 08:57:02:062 LoadUserProfile: lpProfileInfo->lpProfilePath = <\\SERVER\VOL1\Users\USERNAME\Windows NT 5.1 Workstation Profile>
USERENV(400.404) 08:57:02:062 LoadUserProfile: NULL default profile path
USERENV(400.404) 08:57:02:062 LoadUserProfile: NULL server name
USERENV(400.404) 08:57:02:062 LoadUserProfile: In console winlogon process
USERENV(400.404) 08:57:02:062 In LoadUserProfileP
USERENV(400.404) 08:57:02:062 ================================================== =======
USERENV(400.404) 08:57:02:062 LoadUserProfile: Entering, hToken = <0x998>, lpProfileInfo = 0x6ea18
USERENV(400.404) 08:57:02:062 LoadUserProfile: lpProfileInfo->dwFlags = <0x1>
USERENV(400.404) 08:57:02:062 LoadUserProfile: lpProfileInfo->lpUserName = <USERNAME>
USERENV(400.404) 08:57:02:062 LoadUserProfile: lpProfileInfo->lpProfilePath = <\\SERVER\VOL1\Users\USERNAME\Windows NT 5.1 Workstation Profile>
USERENV(400.404) 08:57:02:062 LoadUserProfile: NULL default profile path
USERENV(400.404) 08:57:02:062 LoadUserProfile: NULL server name
USERENV(400.404) 08:57:02:062 LoadUserProfile: User sid: S-1-5-21-77328758-3310200150-3344791982-1022
USERENV(400.404) 08:57:02:062 CSyncManager::EnterLock <S-1-5-21-77328758-3310200150-3344791982-1022>
USERENV(400.404) 08:57:02:062 CSyncManager::EnterLock: No existing entry found
USERENV(400.404) 08:57:02:062 CSyncManager::EnterLock: New entry created
USERENV(400.404) 08:57:02:062 CHashTable::HashAdd: S-1-5-21-77328758-3310200150-3344791982-1022 added in bucket 21
USERENV(400.404) 08:57:02:062 LoadUserProfile: Wait succeeded. In critical section.
USERENV(400.404) 08:57:02:078 LoadUserProfile: Expanded profile path is \\SERVER\VOL1\Users\USERNAME\Windows NT 5.1 Workstation Profile
USERENV(400.404) 08:57:02:078 ParseProfilePath: Entering, lpProfilePath = <\\SERVER\VOL1\Users\USERNAME\Windows NT 5.1 Workstation Profile>
USERENV(400.404) 08:57:02:078 CheckXForestLogon: checking x-forest logon, user handle = 2456
USERENV(400.404) 08:57:02:078 CheckXForestLogon: Stand-alone or NT4 domain, not x-forest logon.
USERENV(400.404) 08:57:14:093 AbleToBypassCSC: Try to bypass CSC
USERENV(400.404) 08:57:14:250 AbleToBypassCSC: tried NPAddConnection3ForCSCAgent. Error 53
USERENV(b78.b7c) 08:57:21:500 LibMain: Process Name: C:\WINNT\system32\wuauclt.exe
USERENV(4ec.ca0) 08:57:42:812 LibMain: Process Name: C:\WINNT\System32\Novell\XTAgent.exe
USERENV(4ec.ca0) 08:57:42:828 GetUserDNSDomainName: Computer is running standalone. No DNS domain name available.
USERENV(400.404) 09:00:16:000 ParseProfilePath: CSC bypassed failed. Ignoring Roaming profile path
USERENV(400.404) 09:00:16:015 ReportError: Impersonating user.

OK, I'm out of Ideas.
I was hoping for something much bigger :>
You may want to post in the MS Forums in regards to the Timeout in that
part.
I would not mention ZCM or Client32 as that will just cause pushback.
In short, there appears to be a long timeout for the redirected profile
that extends beyond just client timeout settings.
You may want to post the the Client32 Forum to see if they have anymore
timeout tweaks.
You may be able to use the "Bad Name Cache" to pre-popate that server so
you can gain the 10 seconds w/o needing to disable the workstation service.
Perhaps the "Give Up on Requests to SAs", but I've never messed with
that before. Wait before giving up on DA may help too.
Just guessing now.
On 2/1/2011 4:06 PM, nathan cook wrote:
>
> craig_wilson;2070716 Wrote:
>> As a Test, Could you disable the "Workstation" Service on the Device?
>> There is a Change the MS Client is trying to pull the Profile from
>> there
>> as well.
>>
>> If this "Test" works, we can try and think of a real solution.
>
> Thanks Craig, just tried that and it took 10 secs off the time.
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

Excel slows down when network drive is mapped

Since a couple of months we are experiencing strange behaviour of excel (2011) on Lion 10.7.5
Excel versions from 14.3.1. to 14.3.4 all the same behaviour.
Symptom 1)
When I connect the Time Capsule drive , Excel slows down by factor 100 when entering text. Needs up to 2 seconds to react on a key stroke.
When I disconnect the handle, excel works fast again.
(repeatable, reproducible)
Symptom 2)
on the network drive, always at the same place, a file named ~abcde.xls... occurs (exact name forgotten, but it is a recent file name
preceded with a tilde sign)
deleting of the file does not affect speed
the file reappears occasionally (TC backup is switched off!)
Where is the ghost??? :-D
maybe these symptoms are uncorrelated.
Why the heck does Excel slow down when I open the network drive??
Why does this happen on 10.7.5 and not on 10.6.8?
Anyone any idea?
thanks,
Stefan

Thanks. Away on holiday right now, but will do it as soon as I get back next week.
Out of curiosity, the external drive works fine when connected directly via USB to the laptop. I took that to mean that the problem wasn't to do with the drive, but probably the network. Is it possible there could be a problem with the drive which only shows up when it's used as a network drive?

Workaround for slow Bridge when network drive is inaccessible?

Hello all,
Hoping someone has some information regarding an issue I'm having with my workflow and Bridge. I have CS6 installed and am using the 64bit version of Bridge for file management. I work from 2 locations at the moment and have a portable drive that I take with me from place to place with my work files on it. In one location I can plug the drive directly into my system via USB, but in the other location (for various reasons) I have to plug it in elsewhere and access the drive through a network. This all works fine and I have no issues with getting to my files in general. Where I do get an issue however is when I start trying to add shorcuts to the drive within the "Favorites" menu in bridge.
The short of it is that as long as I have a shortcut to the networked drive in the Favorites menu, Bridge will run EXTREMELY slow when I am at the work location where I am accessing the drive directly. It appears that Bridge is trying to look for the networked drive on all the networked computers at that workplace every time I try to access a file or even use the menu system within Bridge (to right click a file for properties for example). I can alleviate the issue by removing the networked drive from my favorites or disconnecting form the internet (that one is not a practical option however), at which time Bridge stops trying to constantly look for the drive eveywhere and returns to normal speed.
This isn't a horrible issue for me, it just creaates a lot of repeat work of having to navigate to the network every time I open bridge again at the location where I access the drive remotely, or having to constantly re-add the networked drive back into the favorites every time... then having to remove it again before use at the other location and so on. Is there a way to adjust or change Bridge's behavior to basically tell it that if the specific drive isn't available after the first attempt to ignore it from then on unless I specfically click on the favorites link? Or in lieu of that, is there a way to have alternate "profiles" within Bridge that have seperate favorites etc. so that I can switch back and forth depending on the location I am at?
Like I said, not a horrible issue, but I really like having the quick, easy access to the drive that the favorite menu provides and would love to have a work around if one is possible. I realize that this setup is not common and so I might just have to deal, but if there is a super user solution or something I can tweak in a config file somewhere I would love to know! Thanks for the input and advice in advance!

Thanks for taking the time to respond guys! Yeah, I didn't think there would be any easy answer to this one. I actually have never had any issues running Bridge with any network I've been on with the exception of the lag when the network drive isn't present. Or to be more specific, severe lag when the networked drive is stored in favorites and then is absent in a situation where there is another different network of computers present. Don't know if it will help anyone who is trying to connet to a network drive etc. but all I do to get Bridge to "see" the network drive is navigate to the desired network drive or folder in Windows Explorer and then drag the drive or folder icon over from the Windows Explorer browser into my favorites area in Bridge. It drops the network link right into the favorites menu complete with a special network icon for the link. That has proven to be the fastest way for me to get a correct and functional connection to a network drive stored in Bridge. I was doing this with Bridge CS5 as well and it has always worked great for me.
For my network drive situation specifcally, I actually link to the entire drive as It's used solely for my design work. It's uniquely named with a title specific to me and my business so it definitely wouldn't be sharing a common name with any other drives or folders on another system on the network. I save the link to the network drive in my favorites and then I only ever have to click that to get to the root directory of the drive and navigate to whatever I need. Works great and super fast at the location where I need to use the network drive. Maybe I don't have hiccups like some because my computer has a reserved IP for that network tied to the MAC address of my computer so it is always the same IP every time.
The functionality I would like is actually very close in Bridge, with the only issue being that it insists on searching other computers on the network after every process it does if the network drive isn't present. The location I work at that doesn't use the network drive setup has 5 computers linked up to their network and so I guess it's scouring each of those every time I do any single thing in Bridge, looking for the long lost network drive lol! I have to confess this is strange behavior and really seems like a bug (albeit maybe a minor one due to the unusual workflow method) to me and Bridge is the only software I have that does this type of behavior. I can't really think of a good reason why you would need Bridge to look for a drive or folder in a location other than the one you have specified in the favorite path for it. I mean what if you have 2 copies of the same folder in different locations for backup purposes? You wouldn't want Bridge taking the initiative on it's own and accessing your backup folder without telling you, especially if there are legacy versions of a file you wish to retain in the backup location.
If anyone ends up having a solution for this I would love to hear it! Otherwise I'll just have to hope that Adobe eventually buffs up the network functionality of Bridge down the road and in the meantime add and remove the favorites path all the time. I would think smooth network functionality would be increasingly needful and important however. I mean Adobe even offers a cloud service version of their software... That implies to me that they are aware that more and more work will be done "in the cloud" and over networked scenarios. I have my fingers crossed! Thanks again for the info guys!

Whole system slows drastically when network drive is mounted

Firstly, I hope I'm asking this in the right place. (I've also asked under the MacBook section, but got no replies - sorry for duplicating the question).
I'm using a MacBook with Snow Leopard, a Time Capsule and a 1.5TB USB drive attached to the Time Capsule as a wireless network drive. Whenever the network drive is mounted, my whole computer runs intolerably slowly. Even if no program is actually using files from the network drive and the drive itself is silent and unused, my computer still crawls along agonizingly slowly. Yet if I plug the drive directly into the MacBook there's no problem whatsoever.
Does anyone have any idea what's going on and how I can cure the problem?
In case it counts:
MacBook: running OS 10.6.5, 2.2GHz, Intel Core 2 Duo, 1GB 667MHz DDR2 SDRAM.
Network: 802.11n, WPA2 Personal.
Hard Disk: LaCie, 1.5TB USB 2.0
Thanks in advance for any help you can give me!

Thanks. Away on holiday right now, but will do it as soon as I get back next week.
Out of curiosity, the external drive works fine when connected directly via USB to the laptop. I took that to mean that the problem wasn't to do with the drive, but probably the network. Is it possible there could be a problem with the drive which only shows up when it's used as a network drive?

[Mobile Acc.] VERY slow logout when login on network AND logout off network

Hello,
I'm installing a macmini server (10.6.6) and want to use mobile user account.
I thought everything was fine so I tried to login and logout with my macbook pro (Snow Leopard).
Unfortunately I detected a pb :
- When I login on network and logout on network everything is fine
- When I login off network and logout off network everything is fine
- When I login on network and try to logout off network, the login is fine but the logout needs about 20 minutes!
I found in the console that the macbook is waiting to re-connect the afp share points.
How can I avoid that?
Thanks in advance
Extracts from the console :
20/03/11 17:43:00 kernel AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
20/03/11 17:43:01 configd[14] network configuration changed.
20/03/11 17:43:01 configd[14] setting hostname to "MacBook-Tom.local"
20/03/11 17:43:05 KernelEventAgent[404] tid 00000000 received event(s) VQ_NOTRESP (1)
20/03/11 17:43:05 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Users', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-1.2f00000f', not responding
20/03/11 17:43:05 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Groups', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-2.2f000010', not responding
20/03/11 17:43:05 KernelEventAgent[404] tid 00000000 found 2 filesystem(s) with problem(s)
20/03/11 17:43:05 kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xbca3e58
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect started /Volumes/Users prevTrigger 0 currTrigger 1
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Users
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Users
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: Max reconnect time: 600 secs, Connect timeout: 0 secs for /Volumes/Users
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Users
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Users failed 65.
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect started /Volumes/Groups prevTrigger 0 currTrigger 1
20/03/11 17:43:05 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:06 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Users', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-1.2f00000f', not responding
20/03/11 17:43:06 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Groups', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-2.2f000010', not responding
20/03/11 17:43:06 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Users
20/03/11 17:43:06 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Users failed 65.
20/03/11 17:43:06 kernel AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
20/03/11 17:43:06 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:07 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:08 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Users
20/03/11 17:43:08 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Users failed 65.
20/03/11 17:43:08 kernel AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
20/03/11 17:43:08 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:09 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:10 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:11 KernelEventAgent[404] tid 00000000 received event(s) VQ_NOTRESP (1)
20/03/11 17:43:11 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Users', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-1.2f00000f', not responding
20/03/11 17:43:11 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Groups', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-2.2f000010', not responding
20/03/11 17:43:11 KernelEventAgent[404] tid 00000000 found 2 filesystem(s) with problem(s)
20/03/11 17:43:11 [0x0-0xe20e2].com.skype.skype[2793] WirelessAttach: IOServiceOpen error: e00002c7
20/03/11 17:43:11 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:11 kernel AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Groups
20/03/11 17:43:12 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Users
20/03/11 17:43:12 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Users failed 65.
20/03/11 17:43:12 kernel AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
20/03/11 17:43:12 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:13 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:14 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:15 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:16 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:17 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:18 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:19 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:20 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Users
20/03/11 17:43:20 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Users failed 65.
20/03/11 17:43:20 kernel AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
20/03/11 17:43:20 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
20/03/11 17:43:21 kernel AFP_VFS afpfs_DoReconnect: reconnect already in progress for /Volumes/Groups, going back to wait
*...again and again and again...*
20/03/11 17:53:10 KernelEventAgent[404] tid 00000000 received event(s) VQ_DEAD (32)
20/03/11 17:53:10 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Users', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-1.2f00000f', dead
20/03/11 17:53:10 KernelEventAgent[404] tid 00000000 found 1 filesystem(s) with problem(s)
20/03/11 17:53:10 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Groups', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-2.2f000010', not responding
20/03/11 17:53:10 loginwindow[2705] AFP error -1 mapped to EIO
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Users
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Users failed 65.
20/03/11 17:53:10 kernel ]
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: posting to KEA to unmount /Volumes/Users
20/03/11 17:53:10 kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 1 on so 0xbca3e58
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect started /Volumes/Users prevTrigger 1 currTrigger 2
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: already in unmount /Volumes/Users
20/03/11 17:53:10 kernel AFP_VFS afpfs_unmount: /Volumes/Users, flags 524288, pid 404
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Groups
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: Max reconnect time: 600 secs, Connect timeout: 0 secs for /Volumes/Groups
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 17:53:10 kernel AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
20/03/11 17:53:11 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 17:53:11 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 17:53:11 kernel AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
20/03/11 17:53:13 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 17:53:13 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 17:53:13 kernel AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
20/03/11 17:53:17 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 17:53:17 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 17:53:17 kernel AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
20/03/11 17:53:25 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 17:53:25 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 17:53:25 kernel AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
20/03/11 17:53:35 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 17:53:35 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 17:53:35 kernel AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
*...again and again and again...*
20/03/11 18:03:05 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 18:03:05 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 18:03:05 kernel AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
20/03/11 18:03:15 KernelEventAgent[404] tid 00000000 received event(s) VQ_DEAD (32)
20/03/11 18:03:15 KernelEventAgent[404] tid 00000000 type 'afpfs', mounted on '/Volumes/Groups', from 'afp_4FLpM10E8KV40NIHSB2mlMQZ-2.2f000010', dead
20/03/11 18:03:15 KernelEventAgent[404] tid 00000000 found 1 filesystem(s) with problem(s)
20/03/11 18:03:15 loginwindow[2705] AFP error -1 mapped to EIO
20/03/11 18:03:15 loginwindow[3291] AFP error -1 mapped to EIO
20/03/11 18:03:15 kernel AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Groups
20/03/11 18:03:15 kernel AFP_VFS afpfs_DoReconnect: connect on /Volumes/Groups failed 65.
20/03/11 18:03:15 kernel ]
20/03/11 18:03:15 kernel AFP_VFS afpfs_DoReconnect: posting to KEA to unmount /Volumes/Groups
20/03/11 18:03:15 kernel ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 2 on so 0xbca3e58
20/03/11 18:03:15 kernel AFP_VFS afpfs_DoReconnect started /Volumes/Groups prevTrigger 2 currTrigger 3
20/03/11 18:03:15 kernel AFP_VFS afpfs_DoReconnect: already in unmount /Volumes/Groups
20/03/11 18:03:15 kernel AFP_VFS afpfs_unmount: /Volumes/Groups, flags 524288, pid 404
20/03/11 18:03:17 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[3713] Login Window Application Started
20/03/11 18:03:17 com.apple.ReportCrash.Root[3706] 2011-03-20 18:03:17.458 ReportCrash[3706:2903] Saved crash report for loginwindow[3291] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow2011-03-20-180317localhost.crash

Thanks to try but I'm not in this case.
Note that the pb appears only on logout.

Finder is very slow, particularly when using network drive

I have a mid-2011 Macbook Air, OSX 10.9.4, and Finder is extremely slow, particularly when I am navigating my Time Capsule. First, a little history.
I have tried the fixes listed in these three threads:
(1) https://discussions.apple.com/thread/3358265?searchText=finder%20slow
(2) https://discussions.apple.com/thread/1324280?searchText=Finder%20is%20slow
(3) https://discussions.apple.com/thread/5495797?start=30&tstart=0
Second, my Time Capsule is new. I bought it to replace a WD MyBook that used to work really well, and then something changed. Unfortunately, I assumed that it was some problem on WD's side, so after a year or two of waiting to see if either WD or Apple issued an update to fix it, I assumed it was some kind of file system incompatibility (or other interoperability problem) that wasn't likely to go away, and just sprung for the Time Capsule. However, after getting all the files on the Time Capsule, the problem remains. So here's a rundown of what I experience:
When I navigate the directories on my Time Capsule, if I haven't been in a particular folder, it takes a very long time to load the contents. On average, it will be 30 seconds, but it is not uncommon for it to be over a minute. This can happen even if a folder is empty or has just a few files in it. In addition, adding a subfolder and trying to rename it takes a very long time. After renaming a new folder, it can then take another full minute or more for the folder to actually show the newly assigned name and bounce into line in alphabetical order.
Here are some other observations. First, my connection is very fast, as I'm directly connected to the Time Capsule (albeit via wireless). Second, there is clearly something extra going on in Finder that is contributing to this issue, because I navigated to different directories using Terminal and did an "ls" command, and as you would expect, the list fired out virtually instantaneously. Yet, right after that, if I clicked on that same folder with Finder, it would take a minute or more to display the same file names.
Could it be that the Finder is doing other things at the same time as it is giving me a list of what is in the directory? For example, could the Finder be loading ALL metadata for each of the files into some database or index being built on the fly every time I pop into a new folder, even if I'm not using a view mode where I am asking to see those other bits of metadata? If so, that might make sense as I generally am using the network drive to navigate directories of my photographs, and they have a lot more categories of metadata associated with them than do Word docs and PDFs (e.g., date of picture, time of picture, aperture, shutter speed, exposure, etc.). Or, perhaps is Finder trying to load previews of ALL of the files whenever a directory request is made, so that bouncing through the previews takes less time? I sort of doubt that, because even after a directory listing finally comes up, it seems to churn a bit on each photo before the preview comes up, which I take as an indication that it's creating each preview only after a request is made for that particular file. Either way, I will say that in old WinXP and even in the newer Windows 7, if you want to view files in a Detailed setting where you can see other metadata (called "Attributes"), it definitely prioritizes giving you a directory listing, and then continues filling in the various selected Attributes one-by-one after that. Thus, if you want to sort by the date a photograph was taken (as opposed to its modified or created date, which seem to be default attributes that load as quickly (or nearly as quickly) as the filename), or by the photo's dimensions, it might take a few minutes to load in those attributes for a folder of a couple thousand pictures. But, critically, if you are not planning on using those attributes, but rather, merely want to see how many files you have in that folder, or select them all and load them into a photo viewer, you won't have to wait for the file system to load the file attributes before you get a listing of the folder's contents. It seems to me like the Finder, however, might actually be forcing you to wait until it has loaded all of those attributes.
Does the foregoing sound like a plausible explanation of the problem to those out there with knowledge of how Finder actually works? And if so, does that bring to mind any potential settings that could be turned off or any other work-arounds (since those I've tried have not fixed the issue)?
If anyone has other ideas, I am all ears. I am pretty annoyed that I sunk time into switching over to a Time Capsule on the assumption that Apple couldn't have had a bug this bad, only to find out that I was wrong. The biggest irony is that my old WinXP computer used to rip through the folder structures with ease on the MyBook, but my fully updated Air is practically crippled by the same task.

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

Domained laptop - slow logon when connected to non-domain network

Hi,
I'm looking for ideas on how to solve or workaround this issue, so any help would be appreciated. Please note that this doesn't appear to be the usual type of "slow login" problem - in fact I'm pretty certain the issue is caused by public DNS
servers which return placeholder IP addresses for unknown domains, rather than correctly reporting them as being unknown, which is making XP "hang up" looking for servers which don't really exist. Either way, it's causing a lot of problems for our remote
users.
The scenario is this. When domain-member laptops are not on the domain network, they can take anywhere between 5-30 minutes to login. This issue only occurs when the network they're connected to presents DNS servers which resolve unknown DNS
hosts/domains to "placeholder" sites. Whilst Windows 7 laptops do also seem to suffer from this, login delays on those are at worst a couple of minutes, whereas the Windows XP machines are affected for much longer.
Maybe a bit more info will make it clearer :)
The AD namespace shares the external domain, and there are public DNS records for the external domain, but obviously not for internal hosts (like DCs). So internally, the FQDNs of the domain controllers are "DC1.company.com", "DC2.company.com" etc.
When the laptop is connected to users home network, users can logon quickly (<30 seconds), as long as the DNS server offered by DHCP on that network doesn't return an IP for hosts/domains which don't exist publicly. If they do, login takes 5-30 minutes.
I've confirmed this by doing a lookup of the domain on the affected networks to ascertain which DNS servers return placeholder IPs rather than reporting that name resolution isn't possible. For example, OpenDNS's servers (208.67.222.222, 208.67.220.220)
return placeholders, Google's (8.8.8.8, 8.8.4.4) don't. Using OpenDNS to lookup "dc1.company.com" returns their placeholder IP of 67.215.65.132, using Google's returns "can't find dc1.company.com: Non-existent domain". OpenDNS is being used
as an example, increasingly ISP's seem to be using redirection, we're getting this issue with BT and Virgin Media networks, plus a couple of others.
So, if I manually set DNS on a laptop to use Google's servers, then connect it to one of the affected networks, login is virtually instantaneous. I remove the manually configured DNS servers and allow DHCP to present the ISP's own servers, login is
seriously delayed.
From this I can only assume that the fact that the names are resolving at all is causing the delay. I've removed possibly contributory factors from the equation, such as roaming profiles, redirected folders, mapped drives, group policy etc which the
workstation might be trying to access and causing a delay, as well as checking that fast logon optimization is active.
At the moment we're having to tell users to not connect to the network until after they've logged in, which you'd think wouldn't be that big a deal but you know what users are like :)
I appreciate this issue really seems due to bad practice by ISPs rather than with Windows itself, but we really need a fix we can apply ourselves. Reconfiguring users' home networks really isn't an option, there's too many of them, plus that wouldn't
solve the problem when they're using other networks (hotels etc). I don't think setting "good" DNS servers manually is an option, certainly I can't think of a way that would still work when they're connected to our internal LAN.
I'm thinking there must be some way we can set a timeout or something on the workstations so they don't spend so long trying to communicate with what they think are domain servers, but dispite much searching, I've been unable to find anything that works.
So, any help would be gratefully recieved.
Thanks

Thanks for the reply Martin, unfortunately it didn't help matters, but after pondering for a while (and eventually kicking myself for missing something so obvious) I did come up with a solution.
Basically, just set up public DNS A records for the internal servers and point them to 127.0.0.1 (setting up a wildcard DNS entry for the domain also pointing to 127.0.0.1 would do the same thing).
Sure enough logon now takes about 5 seconds, even on the Windows 7 machines (which were only taking a minute or so anyway).
Loopback is the best place to point these to, Pointing them to a public server didn't work, and pointing them at a non routeable private IP didn't work either.
To help anyone else confirming this is also the cause of their slow logon issue - when all three conditions are met it's time to mess with your public DNS!
The FQDN of the domain is public (company.co.uk) and not local (company.local).
The DNS servers in use on the network (or the ISP's DNS servers to which DNS requests are forwarded) return placeholder IPs for unknown host addresses, rather than a "non-existent domain or host" error. This can be confirmed by pinging (or doing an
nslookup) on the affected machine, for a host for which no public DNS record exists (ie ping wibble.microsoft.com) - if an IP address is returned then the DNS servers in use are resolving unknown hosts/domains to a placeholder IP.
If you allow the machine to login on the external network, then run a
ipconfig /displaydns you'll see entries for attempts to resolve internal servers themselves, plus lookups relating to the AD domain such as
_msdcs.gc._tcp._ldap.internaldomain.co.uk and such - these shouldn't be there off-domain, and I believe they indicate the machine thinks it's on the domain, even though it isn't.
Hope this helps someone else out.
Ray Von

IPHONE 5: can't receive calls & random error messages, such as "could not activate cellular data network" and "no connection - network unavailable, please connect to wifi or cellular network." This occurs even when signal strength or wifi is operational.

IPHONE 5: can't receive calls and random error messages, such as "could not activate cellular data network" and "no connection - network unavailable, please connect to wifi or cellular network." This occurs even when signal strength or wifi is operational, and it does not matter whether wifi is on or off. ATT went through the standard protocol - resetting network, resetting sim card, etc. No changes. Other phones working fine in same region with same carrier. Apple's solution is to restore software, but haven't gone there yet. Anyone successfully addressed this/these issues?

I should point out that it worked when the iPhone was set back to factory settings, but when restored with the backup, data/internet no longer works again, and I get the "Could not activate cellular data network" error message yet again.

Very slow login/logout with Portable Home Directories

I've set up Portable Home Directories for our department so that people can work from different computers if need be (also, I think our network is too slow to use network home directories). However, the login times are excruciating - some users report average 45 minute login times. None of these users are moving huge files or anything, and even if I just log someone out (completing the sync) and then log back in, the login will be very slow.
If I disconnect the computers from the network, obviously it logs in quickly because it can't connect to the server, but I don't want to do that (or disable login/logout sync altogether). I tried removing things from the login/logout sync rules, but often the sync takes time just on 'Finishing' or 'Stopping', so I don't think that it's any particular files that take a lot of time.
On a possibly related note, for some reason our computers all take perhaps 30 seconds to get an IP address when starting up, waking up from sleep, etc. Is there any reason why the computer would need to be doing this repeatedly? Especially on logout, this wouldn't seem relevant, but I've seen that mentioned in other threads.
Thanks in advance for any advice,
Greg

Apple Discussions has a special forum just for Portable Home Directories, you might want to search and/or post your question there:
http://discussions.apple.com/forum.jspa?forumID=1249

Slow login and grey wallpaper?

All,
I have a 4 day old Macbook Pro Retina base config. I haven't had the need to reboot my machine since i first turned it on and maybe updating to the latest update. Last night I decided to shut down rather than put it to sleep.
Today (fourth day) I turned it on, booted up fine, and when I logged in, I noticed it took like 5-7 seconds before it went to my desktop, at one point I thought it froze.
Later on, i was messing with time machine, my external hd, itunes, caffeine, and the menu bar turned black, so I though to reboot the machine.
After the reboot, I logged in, and notice the slow login again, and this time, the wallpaper i set up was gone and was replaced with a grey wallpaper.
I searched a bit and notice a few people have had issues like this with Lion.
Was wondering if there is a solution to this?
Thanks!

Delays and related can be caused by DNS errors, and by network errors.
OS X Server is dependent on correctly-configured DNS services.
To verify DNS, launch Terminal.app from the Applications > Utilities folder on the server, and issue the following diagnostic command:
sudo changeip -checkhostname
That command won't make any changes, but will report whether your host name and your DNS are correct on your server. You'll get some output and a message that no changes are required, or some output and a message indicating something about whatever error was detected.

Safari Falsely states network unavailable randomly - often

Safari Falsely states network unavailable randomly - often .
This has been the case since installing OSX 10.6.2 & Safari 4.0.4 .
I say falsely to rule out network issues as I get a Gateway Error page if my modem has a connection issue .
Also I have been able to still do a software update while Safari states it can't find the network .
These happen daily ... intermittently .

Ok...
From the Safari Menu Bar, click Safari / Empty Cache. When you are done with that...
From the Safari Menu Bar, click Safari / Reset Safari. Select the top 5 buttons and click Reset.
Go here for trouble shooting 3rd party plugins or input managers which might be causing the problem.
http://support.apple.com/kb/TS1594
Make sure Safari is running in 32-bit mode. Right or control click the Safari icon in the Applications folder, then click: Get Info In the Get Info window click the black disclosure triangle next to General so it faces down. Select 32 bit mode. *Also, (in that same window) make sure Safari is NOT running in Rosetta.*
Try Open DNS - Free / Basic
If Safari still gives you problems, go to the Safari Menu Bar, click Safari/Preferences. Make note of all the preferences under each tab. Quit Safari. Now go to ~/Library/Preferences and move this file com.apple.safari.plist to the Desktop. Relaunch Safari. If it's a successful launch, then that .plist file needs to be moved to the Trash.
Also, login using a different user account on your Mac. See if the problem persists. If it does, then the issue is system wide. Back up all important data and use your Mac install disc or SL disc to reinstall the Mac OS X. You can do either the Archive & Install which preserves Users and Network Settings or completely erase the disk and start fresh.

Cannot login to network account (leopard client and server)

Up until now, I have used local accounts on my leopard server. I want to start experimenting with OD prior to implementing. I created a new user account in the /LDAPv3/127.0.0.1 domain, and have bound my leopard client to the server using directory utility. On the login screen, "Network Accounts Available" has a green button to the left of it. When I try and login to the server account, the login window just shakes. At first, I could enter the password and then it would prompt me for a new password. Trying to enter a new password would not allow me to login. I went back to server admin and disabled the "require new password" setting, (as well as the other good security policies)...
I have also reset the password in WGM, and made sure to disable all the security stuff there too...
Lastly, I have deleted the server in directory utility, rebooted, then added it back in, and rebooted again...
I still cannot login to the server account, the login screen just shakes
Does anyone have an idea of what settings and or logs I can check to try and narrow down what is going on?
Thanks in advance....

to close out the thread, I have working dns on my network, but I did not have dns enabled on my server. I enabled the dns service and entered just the info for my server, then assigned my server and client to use the server's ip addy as the primary dns server. Next, I created the home directory.
Once both steps were done, I was able to log in from my client to my server based account...
FYI-I found a document on afp548.com called "leopard server: advanced setup, rsync backup and automated reporting" that walks you right thru the process...Here is the link, it's a very useful doc....
http://www.afp548.com/filemgmt_data/files/Leopard%20Server%20Quickstart%20Guide. pdf
thanks again boomboom_uk and woVi, your suggestions were spot on....

Can't Login With Network Account After Upgrade To Yosemite Server 4

I've been putting off this troubleshooting for a while now, and after trying everything I could find, decided to post.
- After upgrading my server to Yosemite with Server 4, and my MacBook to Yosemite, I can no longer login with any network accounts.
- I was on clean installs of Mavericks before the upgrade.
- I'm using SSL for the OD, with a GoDaddy cert, the same one that was working on Mavericks.
- I've tried removing the laptop's binding using the Users and Groups preferences dialog, which does not remove the laptop's entry from Open Directory, so I manually deleted the record on the server.
- I then choose to Join again, and it looks as though everything goes through, but I still cannot login with a network account. Also, when rejoining, it does not create a binding on the server.
- If I use the Directory Utility->Services->LDAPv3, and add it that way, entering the FQDN and checking Encrypt..., Use for auth and Use for contacts, it asks me for the directory admin username and password, and does in fact create the binding on the server, but I still cannot login. What's strange about that method, is that it forces the use of the IP address of the server, rather than the FQDN, like I entered it, which would of course have problems, because the certificate's common name is the server's FQDN. It does not allow me to change from using the IP address, graying out that field.
- I've also tried destroying the OD and restoring from archive to no avail.
It looks like many users have hit dead ends with this, with some having success by completely formatting and setting up a new iteration of the server, but I will not be doing that. However, I'll be happy to try any other suggestions.
Thanks for your time,
   -- Mike

     Okay, I've finally resolved the issue, thanks to the Apple Enterprise tech support team. I'm thinking they wouldn't mind if I share this information, but I can't guarantee that this will work on your system or, worse yet, degrade your system further. However, that's fairly unlikely, just make sure you have plenty of backups before you begin any troubleshooting session.
     So I was told to perform the following instructions, which I did, line for line. The part about closing Server.app seems a given, but I'm not sure why they want you to open Server.app at the the end (maybe taken out of context from some other instructions?). I did it anyway, but you should be able to begin testing, on a client workstation, right after rekerberizing is complete. I did, however, need to reboot my client, login as local admin, and then binding would proceed, and network users are able to login again. The engineer also let me know to expect an error, something like the following: "2015-03-11 21:58:38 +0000 Error synchronizing removal of attribute draft-krbPrincipalACL from record 72519e4c-7ac7-15e4-bd42-10adb1944cbc: 77013 result: 16 No such attribute" - this is apparently normal, and did in fact happen in my experience.
So here's the fix:
- Quit Server.app (don’t just close the window)
- On the Open Directory Server, execute these Terminal commands:
- sudo mkdir /var/db/openldap/migration/
- sudo touch /var/db/openldap/migration/.rekerberize
- sudo slapconfig -firstboot
- Open Server.app
And that's it. I did nothing else on my OD server, just logged out. Immediately tried binding on my MacBook client, it failed, I rebooted, tried again, it worked quickly, and I'm able to login with network user accounts again.

HP Laserjet M1132 MFP is too slow over the network!

Hi,
My HP Laserjet M1132 MFP is too slow over the network!
I have connect the printer to a windows XP 32bit SP3 using UBS port. The printer works fine on the local computer but when sharing it over the network it works too slow, for example with print test page it takes about 45 seconds to print and for other documents it takes much longer time.
I have installed the latest driver form HP website and upgrade the firmware it the latest version.
It happens on other Windows XP machines as well.
I connected the printer to my laptop (Windows 7 64bit) and it works fine (No delays over the network) and it seems that this problem have some relations with the windows XP Driver.
I have used local port trick on remote machines (instead of regular method) like this:
''add a local printer;
'new port'
'localport'
\\XPcomputer\HPPrinterName as port name
but still nothing!
There is nothing wrong with the network, we use to use a Samsung printer on the same machines over the network with no problem.
I Really appreciate your HELP!
This question was solved.
View Solution.

BEHZAD_T, how is the printer connected to the network (wireless or Ethernet)? If it is slow wirelessly, I would suggest trying to connect the printer to your router with the Ethernet cord and install it to the networked computer that way.
Another question is, relatively speaking, how close to your router are the Samsung printer and the HP printer? Depending on the distance (and what stands between the devices) there can be a lag between sending a print job and it being received by the printer.
Let me know!

SLOW Login when Network Unavailable

Similar Messages

Maybe you are looking for