Roaming Profiles and 10.5.5

[ingenious7]

Hi,

I recently upgraded our servers to 10.5.5, thinking I would see massive improvements still, as with the previous 10.5 updates.

To my dismay, we are having Windows Roaming Profiles issues since the upgrade! When a client attempts to log in, Windows is not copying some files over due to “The specified network name is no longer available”. It is always on certain folders in the profile (namely Adobe Local Settings and Microsoft Local Settings). When these are deleted from the file server the users are able to get their profile, but the same issue occurs the next time they log in.

This really seems like a problem with the profile service on 10.5.5. Is anybody experiencing this, or does anybody have a solution to the The specified network name is no longer available problem?

Regards,

[ingenious7]

In addition, here are the smb logs when the profile is being copied over

KieranB closed file s1997/KieranB/Application Data/Thunderbird/registry.dat:AFP_AFPINFO:$DATA (numopen=48) NT_STATUS_OK
[2008/09/19 14:50:02, 2, pid=1597] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:close_normal_file(399)
KieranB closed file s1997/KieranB/Application Data/Thunderbird/profiles.ini:AFP_AFPINFO:$DATA (numopen=47) NT_STATUS_OK
[2008/09/19 14:50:06, 0, pid=1645] /SourceCache/samba/samba-187.8/samba/source/lib/util_sock.c:set_socket_options(261)
Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2008/09/19 14:50:06, 0, pid=1645] /SourceCache/samba/samba-187.8/samba/source/lib/util_sock.c:set_socket_options(261)
Failed to set socket option TCP_NODELAY (Error Invalid argument)
[2008/09/19 14:50:06, 0, pid=1645] /SourceCache/samba/samba-187.8/samba/source/lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2008/09/19 14:50:06, 2, pid=1645] /SourceCache/samba/samba-187.8/samba/source/smbd/reply.c:reply_special(328)
netbios connect: name1=PRINT name2=W-JS-STU24
[2008/09/19 14:50:06, 2, pid=1645] /SourceCache/samba/samba-187.8/samba/source/smbd/reply.c:reply_special(335)
netbios connect: local=print remote=w-js-stu24, name type = 0
[2008/09/19 14:50:06, 0, pid=1645] /SourceCache/samba/samba-187.8/samba/source/lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 10.133.168.82. Error Broken pipe
[2008/09/19 14:50:06, 0, pid=1645] /SourceCache/samba/samba-187.8/samba/source/lib/util_sock.c:send_smb(761)
Error writing 4 bytes to client. -1. (Broken pipe)
[2008/09/19 14:50:06, 2, pid=1646] /SourceCache/samba/samba-187.8/samba/source/lib/module.c:do_smb_load_module(64)
Module ‘/usr/lib/samba/auth/odsam.dylib’ loaded
[2008/09/19 14:50:09, 2, pid=1655] /SourceCache/samba/samba-187.8/samba/source/smbd/reply.c:reply_special(328)
netbios connect: name1=10.133.168.200 name2=ENDEAVOUR-IMAC5
[2008/09/19 14:50:09, 2, pid=1655] /SourceCache/samba/samba-187.8/samba/source/smbd/reply.c:reply_special(335)
netbios connect: local=10.133.168.200 remote=endeavour-imac5, name type = 0
[2008/09/19 14:50:09, 2, pid=1655] /SourceCache/samba/samba-187.8/samba/source/lib/module.c:do_smb_load_module(64)
Module ‘/usr/lib/samba/auth/odsam.dylib’ loaded
[2008/09/19 14:50:09, 2, pid=1493] /SourceCache/samba/samba-187.8/samba/source/smbd/close.c:close_normal_file(399)
HaydnTS closed file Desktop/Windows Media Player.lnk (numopen=2) NT_STATUS_OK
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

[fleecy]

I’m seeing the exact same thing here.

Roaming profiles are broken in 10.5.5. I tried different authentication methods, no go.

Apple really should test its stuff better before letting it out there. SMB needs so much attention on Leopard Server, it’s unbelievable.

I’m actually starting to wonder if I should split this SMB stuff from my Leopard server and move it to a virtualized Win2K3 solution, or something else.

[ingenious7]

I’m “glad” to hear that I am not the only one with this problem. Everything was working really well with 10.5.4 and I really don’t know how it could have gotten broken so much.

I don’t know what you have concluded, but we seem to think that there is an issue with smb dropping connections, possibly due to an issue with WINS. we have changed some of the WINS settings and it seems a little better, but still a few issues. I did see in the list of improvements for 10.5.5 that Apple “fixed” PDCs and BDCs so they would work properly together.

[Sappomanno]

Hullo,

I found this link, and the method explained by dherberd resolved the issue

[url]http://macosx.com/forums/mac-os-x-server/298314-samba-shares-hfs-extended-attributes.html#post1432514[/url]

C.

[bomek]

I’m also getting a lot of issues using MacOSX 10.5. This version seem to be totally broken when used in a windows environnement. If you select the box “Password must be changed at next login”, the user is asked to change his password over and over if he logged on a replica!!!!

And the fileserver stop responding from time to time. Support for streams is whacked, etc, etc…

[David Wallace]

I have a 10.5.4 server running as a ODM and a PDC. When the windows folks log into their computer (connected to the domain created by the PDC) the server it will authenticate them. Problem is that after a while some users start to get a “can’t find profile” error. It creates them a temp one on the local machine. Usually what we do is create them a new user on the ODM and they start the process again and it works for a while but eventually they get the error again.

Ideas?

David Wallace
Director of Technology Services, Webb City Public Schools
Webb City, Missouri
[email protected]

“Sharing my tools so that others may sharpen them”

[ingenious7]

[QUOTE][u]Quote by: bomek[/u][p]I’m also getting a lot of issues using MacOSX 10.5. This version seem to be totally broken when used in a windows environnement. If you select the box “Password must be changed at next login”, the user is asked to change his password over and over if he logged on a replica!!!!

And the fileserver stop responding from time to time. Support for streams is whacked, etc, etc…[/p][/QUOTE]

Hi bomek,

I am still seeing this issue! Mac OS X clients are able to change password fine when it is forced – Windows gets stuck in an infinite loop of forcing password changes. Funny thing is that users can actually change their password once logged in. We have possibly linked this to a corrupt index in the LDAP tree and plan to do a rebuild of the index to see if this makes any difference.

As for profiles: All servers are now running Mac OS X 10.5.6. We have three BDC and one PDC. Two of the BDC have no issues for users downloading their roaming profiles. Never get error messages and it works super fast.

The other BDC occasionally has issues, though not as often as it used to. The error we get is that “The specified network name is no longer available”. It is like the server is being overloaded and dropping connections. We adjusted some group policies for computers using the System Policy Editor to try and increase the timeout before the workstation uses a local profile as we thought that maybe this particular BDC was under heavier load than the others. If anyone is having different error messages when trying to download profiles we made changes using the System Policy Editor to redirect Windows Desktop to H:\Desktop and also set a policy to not create “thumbs.db” which for some reason causes profiles not to download correctly.

I really find this quite a cryptic problem – as two BDCs work fine – always have under 10.5.4 and 10.5.6. The only difference is that I didn’t put them on 10.5.5 after the problem with the BDC we did put on 10.5.5.

[lunatica]

We get the “This process has forked..” error on our PDC and BDC. I’m currently in the spring break at school and the couple of last breaks I always was working to get the roaming profiles going. In fact the non-working SMB-implementation kept me from using Leopard Server for some time. It’s a shame for Apple.

What I’ve changed the last 2 weeks:
Our setup so far was that all roaming profiles where not stored on the PDC @ /Users/Profiles but on the BDC on another share totally not @ /Users/Profiles. This break I’ve changed this and moved all profiles carefully to the PDC to it’s default location @ /Users/Profiles. This has fixed high cpu load and so far (I’m virtually alone in school) the few user accounts I know the password of, work fine!

In Tiger Server, we’ve had our win-user group for Windows Profiles. We always had to have staff as well on the profiles permissions, otherwise no Windows machine could login. In Leopard Server, staff has become the group “Open Directory Users” for what reason ever and also important: “Domain Users”. This has to be added, also don’t forget to give the network users this new group as well, otherwise they won’t be able to login.

Things working for us:

– PDC & BDC running with Latin 1 (850) Characterset if you edit the smb.conf, no gui fix yet in 10.5.6: another shame
– Reduced server load in 10.5.6 when certain Windows profiles log in, still have to see this when school restarts during high usage
– netlogon scripts work and network drives are mapped if the computer is in the domain

What’s not working:

– On certain Windows XP computers, a few users are not able to get their network drives mapped, also their access is blocked as if the whole computer is not in the domain or the user not fully authorized. But, if a nother user logins on the same machine, everything is fine..very strange.

– And yes, we get constantly broken pipe errors and then the “This process has forked..”- nightmare.

-> I’ve already checked the CIF SID and it’s correct and played around with secpol.msc and the variations that are possible there, no improvement.

It’s so ludicrous, Mac OS X 10.5 Server is soon phased out in favour of Snow Leopard but never had a working SMB implementation so far. Tiger Server worked perfectly in comparison. Why why why why? Let’s hope our SMB will hold after the spring break with the changes I’ve made.

[playersons]

[QUOTE][u]Quote by: lunatica[/u][p]It’s so ludicrous, Mac OS X 10.5 Server is soon phased out in favour of Snow Leopard but never had a working SMB implementation so far. Tiger Server worked perfectly in comparison. Why why why why? Let’s hope our SMB will hold after the spring break with the changes I’ve made. [/p][/QUOTE]

So, did it hold after spring break? How are your roaming profiles doing so far?

playersons

[lunatica]

Hi playersons,

I’ve got positive results. We’re running 10.5.6 Server for SMB homes. What solved for us many problems with netlogon scripting, stability and reliable functioning roaming profiles was to:

– move all roaming profiles to the server that handles the authentication (beforehand we’ve had authentication and authorization split to 2 servers, that was the pdc handling the authentication and a 2nd file server hosting the roaming profiles, acting as a bdc.

– Outcomment the usage of darwin streams in the smb.conf

– minor adjustments of the syntax of our netlogon.bat.

Apple said that the ‘this process has forked’-messages in the log are non-critical, although I’ve seen them only in connection with the problems we’ve had. But, to my surprise, applying the changes I’ve outlined above solved all issues but the ‘this process has forked’ messages in the logs are still there, which confirms that those messages are non-critical.

What I don’t understand is why Apple is so tight-lipped about their smb-implementation and treats SMB as a stepchild in Leopard Server. That’s a mistery for me still, because during all the months of my attempts to find out why SMB was so terribly wrong in the beginning, I’ve had to rely on the experience of others confrming problems I’ve had so my impression was and still is that it could have been better if Apple puts their focus back on SMB. It’s a marketing argument if you can sell OS X Server along with an Xserve to replace all Windows servers because of a state of the art SMB implementation.

If you have further questions, feel free to ask.

[lkalis]

May I ask what adjustments you made to the your netlogon.bat file?

[lunatica]

We had issues with incorrectly mounting shared folders so we have now this that works. I can’t remember what wrong with that to be honest.

Excerpt:
NET USE J: \\File-1\%username% /persistent:no
NET USE K: \\File-1\Groups /persistent:no

The first line let’s the mac user profile mount under J and the 2nd line mounts our shared groups folder under k.

Other than that we check what printers are installed and delete unused printers, but this worked fine directly.

[Author]

Posts