search for: lharmo02

When attempting to join my Samba box to my AD domain, I get the following: # ./net rpc join -I 192.168.0.20 -U administrator Password: [2004/04/21 16:18:30, 0] rpc_client/cli_netlogon.c:cli_nt_setup_creds(249) cli_nt_setup_creds: request challenge failed [2004/04/21 16:18:30, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(326) Error domain join verification (reused connection):

...d checks the local winbind_idmap database and then returns the correct UID information associated with a file almost instantly. Nsswitch.conf passwd: files winbind shadow: files group: files winbind Any help would be greatly appreciated!!! -----Original Message----- From: Harmon, Leigh [mailto:lharmo02@harris.com] Sent: Friday, January 16, 2004 3:48 PM To: 'samba@lists.samba.org' Subject: [Samba] Problem updating/creating files with winbind and a win2k box Hi, I'm having a strange issue with Samba 3.0.1 running on Solaris 8, and updating/creating files on a Win2k machine. I have...

Hi, I'm having a strange issue with Samba 3.0.1 running on Solaris 8, and updating/creating files on a Win2k machine. I have a test share created on the Solaris machine (path=/export) with initially no files in it. I have no problem accessing the test share from the Win2k machine. I can successfully create/update a file in the test share from the Win2k machine. The problem occurs when I

All, Is there a limit on the number of symbolic links that Samba follows correctly. I'm running Samba 3.0.1 on Solaris 8, and using Samba as a file server. I've tested 3.0.2 and have the same issue. On the Unix side, I have a directory that contains many symbolic links to other directories. Many of these links point to other links (on separate servers by NFS), which then point to a

Hi, I've been researching which type of security to use with Samba 3.0.1 and I still don't understand what the difference is between "security=DOMAIN" versus "security=ADS." I complied Samba to include ADS support, and I initially chose "security=DOMAIN." When I use the "net" command I can add it to my domain. However, if I set

All, I've recently upgraded my Samba server from 2.2.8 to 3.0.1. I also changed the security option to "security=Domain" and added it to the AD domain. The issue that I am having is that some users cannot access a share that is accessible to group members only, even though they are in the group. It appears that certain users on certain machines have a hard time mapping the

Hi, I have a few users that are creating errors like below. These users have mapped a directory via Samba and also have it connected. They can access their home directory or other directory via Samba fine, but it is strange that every hour on the hour there is a failure put into the log (even though they are working). My server is joined to the Domain and it is using