[pixelgrunt]

Give a little, take (well, ask) a little…

[quote]To enable debug logging at startup, run the following:

[code]$ sudo touch /Library/Preferences/DirectoryService/.DSLogDebugAtStart[/code]
[url]http://www.jaharmi.com/2008/07/21/start_directory_service_debug_logging_automatically_after_the_next_restart_on_mac_os_x[/url]

I’m left hanging. I’m also seeing the following in my DirectoryService.debug log:

[code] ADPlugin: Something wrong, unable to determine domain information from Config container……[/code]
My client macs are OS X 10.4.11 attempting to bind to a 2003 AD environment. Can anyone shed some light on this particular error?

I’m also seeing “Computer Container specified does not exist,” when attempting to bind. This shows whether I create the machine
account in AD or not. I even tried a CN beside Computers to see if that helped. It didn’t.

Anyone?

[pixelgrunt]

Thanks for the quick response. This is a very well-run site.

We have a sufficiently non-standard AD environment here that just makes life as a Mac technician, let’s say, ‘interesting.’

Here is a snippet of the log.smbd around the time of my reboot this morning:

<snip>
[2006/04/24 07:33:42, 0] /SourceCache/samba/samba-92.19/samba/source/smbd/server.c:main(789)
smbd version 3.0.10 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2006/04/24 07:33:43, 0] /SourceCache/samba/samba-92.19/samba/source/libads/kerberos.c:ads_kinit_password(146)
kerberos_kinit_password host/[email protected] failed: Client not found in Kerberos database
[2006/04/24 07:33:43, 0] /SourceCache/samba/samba-92.19/samba/source/printing/nt_printing.c:nt_printing_init(386)
nt_printing_init: error checking published printers: WERR_ACCESS_DENIED
[2006/04/24 07:33:56, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:get_peer_addr(1016)
getpeername failed. Error was Socket is not connected
[2006/04/24 07:33:56, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:write_socket_data(446)
write_socket_data: write failure. Error = Broken pipe
[2006/04/24 07:33:56, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:write_socket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
[2006/04/24 07:33:56, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:send_smb(663)
Error writing 4 bytes to client. -1. (Broken pipe)
[2006/04/24 07:33:58, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:get_peer_addr(1016)
getpeername failed. Error was Socket is not connected
[2006/04/24 07:33:58, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:get_peer_addr(1016)
getpeername failed. Error was Socket is not connected
[2006/04/24 07:33:58, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:write_socket_data(446)
write_socket_data: write failure. Error = Broken pipe
[2006/04/24 07:33:58, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:write_socket(471)
write_socket: Error writing 4 bytes to socket 23: ERRNO = Broken pipe
<snip>

Does this give any insight into the cause of our problems? We have had to downgrade other Tiger (G4) XServes here because of this very problem, but that’s not an option here because 10.3 Server doesn’t install on this G5 XServe.

Here is some more of the same log, just before the reboot when the problem was noticed:

[2006/04/14 14:42:42, 0] /SourceCache/samba/samba-92.19/samba/source/smbd/service.c:set_current_service(51)
chdir (/Volumes/VideoXServeRAID1/Video Lab Share) failed
[2006/04/14 14:42:42, 0] /SourceCache/samba/samba-92.19/samba/source/smbd/service.c:set_current_service(51)
chdir (/Volumes/VideoXServeRAID1/Video Lab Share) failed
[2006/04/21 15:28:30, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:read_socket_data(400)
read_socket_data: recv failure for 4. Error = Connection reset by peer
[2006/04/21 21:53:48, 0] /SourceCache/samba/samba-92.19/samba/source/lib/util_sock.c:read_socket_data(400)
read_socket_data: recv failure for 4. Error = Operation timed out
[2006/04/22 13:42:01, 0] pdb_ods.c:odssam_getsampwnam(2329)
odssam_getsampwnam: [0]get_sam_record_attributes dsRecTypeStandard:Users no account for ‘video lab user’!
[2006/04/22 13:50:41, 0] pdb_ods.c:odssam_getsampwnam(2329)
odssam_getsampwnam: [0]get_sam_record_attributes dsRecTypeStandard:Users no account for ‘video lab user’!
[2006/04/22 13:51:15, 0] pdb_ods.c:odssam_getsampwnam(2329)
odssam_getsampwnam: [0]get_sam_record_attributes dsRecTypeStandard:Users no account for ‘fcp’!
[2006/04/24 07:33:42, 0] /SourceCache/samba/samba-92.19/samba/source/smbd/server.c:main(789)
smbd version 3.0.10 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004

I’m still interested in getting launchd to function as a watchdog replacement.

[pixelgrunt]

…and thanks for the quick reply.

This site rocks.

[pixelgrunt]

[QUOTE] Youch. You’re working too hard there.[/QUOTE]

I couldn’t agree with you more.

I know the server is functioning as a stable service otherwise, but tying this into our AD is a nightmare. Most of this due to the fact that the server group doesn’t feel compelled to let us know when changes are to be made in AD. There’s no need for that rant here…

I’m not sure that I can provide too many more details about the AD side. If you have some specific questions, I can try to contact our server group to get the answers. I understand that some change was made within the last three weeks to our AD environment that seems to have precipitated this.

To clarify the symptoms- afp and smb connections from an OS X Mac (10.3.9 client) are successful. An attempt to map the drive from XP erroneously returns an incorrect password error. The Windows File Service Log on the server says the following:

[2005/10/14 10:53:51, 2] /SourceCache/samba/samba-92.9/samba/source/auth/auth.c:check_ntlm_password(312)
check_ntlm_password: Authentication for user [USER1] -> [USER1] FAILED with error NT_STATUS_WRONG_PASSWORD

I can repeat this on a development 10.4.2 server.

The server is a file server only, sharing via afp and smb. I have the administrative power to bind and unbind to AD, but that’s about the extent of my AD powers here.

[pixelgrunt]

Pardon my anonymity, I’m on a different computer at work and forgot my afp548 login…

Is anyone aware of what the following error means when attempting the dsconfigad -enablesso command?:

Unable to configure service http error = 2

I having a heckuva time keeping a Tiger server Kerberized in our AD environment. We managed to get this working a few days ago, but Kerberos broke after a server restart and I can’t get it running again. We had to do some magic dance involving trashing kerberos and directory preferences, setting up an open directory standalone server, and then joining the kerberos domain, with a few restarts in between all of that. Could anyone point me toward any information regarding any of this?

XServe OS X Server 10.4.2 bound to native 2003 AD

I’d be happy to provide more details if requested.

[Author]

Posts