similar to: Samba 3.0 question, DOMAIN vs. SERVER method? Help!

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (OK, my first message got mangled because of the attachments, so I'm reposting) I've got a samba 3 box that's part of an AD domain. It works correctly for most users; but there was a problem where certain users couldn't connect. We'd get a log message that looks like this: Username SAMPLE.COM\pcuser is invalid on this system

Hi all, I'm trying to make samba authenticate to my Active Directory Domain. I already configured and tested Kerberos5 and joined my machine to my domain with no problems, getent passwd and group give me the correct output also wbinfo give a good output too, and I can logon using my domain user to SSH and to my server console, so I assume my Kerberos config is correct. Also I

hi! is it possible to use a samba server for a backup-to-disk space on a veritas backup system??? my system: debian sarge samba 3.0.14a-3 windows 2003 server with veritas 10.0 sp3 i try to configur veritas to use my share on the debian maschin but i always get the following error message: es konnte kein neuer sicherungsordner erstellt werden. zugriff verweigert translation: backup

Environment: redhat, Linux 2.4.7 Samba Version 3.0.0 MIT Kerberos 5 Win2k SP2, running Active Directory. Steps done: 1. net ads join -U admin%admin works fine. Able to see the linux PC test2 on Win2k ActiveDirectory Computers' console. ----- PROBLEM: --------- Not able to test authentication of a valid AD user against Samba. (tried through smbclient and also through Win2k PCs logged on to

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

Hello, I had a perfectly good setup with samba being a domain member, and domain users accessing their shares, since beta1. A month and several updates from M$ later, clients were no longer able to log on to the samba machine. I know this must be related to the updates, since there have been absolutely no configuration / application modifications on the linux box, and clients who forgot to

Hi i have a small problems: I have a Linux Samba File server, on this, i have one directory where a authentification are requested. That's work on all workstation, but only one can't connect. I have only this into the log: [2006/03/16 13:51:43, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(619) NativeOS=[Windows 2002 Service Pack 2 2600] NativeLanMan=[Windows 2002

Hello, I have two domains: - a domain FRANCE on a SAMBA PDC called "SARGE" - a domain DOMAINTEST on a Active Directory called "SRV2003-2" I followed the samba howto chapter on setting a domain trust relationship between this two domains. For now, I just want DOMAINTEST users to log on shares of the FRANCE domain. On Windows 2003 side, with the MMC I can check/revalidate

Hello Rowloand, ok, I just keep "default" for the mounting. I changed the path of my share : [homes] comment = User Home Folder path = /home/%U read only = no follow symlinks = yes wide links = yes browseable = no hide files = /desktop.ini/$RECYCLE.BIN/ I need Wide Links because in the share there are symbolics links to outside the share. Anyway, I still get the same error with all

Hi All, I installed samba 3.0.22 and join it to Win2003 AD domain. Users from my domain can access the samba shares successfully. My problem is that users from trusted domains can not access to my samba shares Wbinfo -m - show all the trusted domains Wbinfo -u - show all the users include the trusted domains users. Any Idea? My smb.conf global parameters: # Global parameters

Hi all I have a samba 3.0.21c with ldap backend , i have about 100 users connecting to my domain. i have a linux system which acts as a file server (prjsrv01) where i have declared 2 shares. projects and datalib. The users get drives mapped with the help of logon script. so i map projects share as P: drive net use p: //prjsrv01/projects. but whent the logon script runs the command. it says

================== platform ===================== Linux version: RHEL-3 resp. Scientific Linux 305 Samba vesrion: 3.0.9-1.3E.3 Samba operating mode: security = SERVER ================== problem ===================== 'net use n: \\smbs1\public' on Windows XP, always asks for a password. 'smbmount //smbs1/public /mnt/public -o password=' does not. This all used to work fine

On 07/01/2020 16:32, Ni Co wrote: > > Le 05/01/2020 ? 14:27, Rowland penny via samba a ?crit?: >> On 05/01/2020 11:36, Ni Co wrote: >>> Hello Rowloand, >>> >>> ok, I just keep "default" for the mounting. >>> >>> I changed the path of my share : >>> >>> [homes] >>> comment = User Home Folder >>>

Hi all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server

I know this may be a very simple question but I cant seem to find the answer in the O'Reilly Samba book or from Google. When using Samba 2 (actual version 2.2.12) we had W2K domain users authentication via the ADS to access Samba shares. The W2K users did not actually have Unix accounts on the Samba server, we used the users.map file to map the W2K account name to a guest Unix account.

Dear Samba-Team, I already wrote to Jeremy Allison an he told me to post my problem to you: I have the following problem: The smbd and winbindd start fine, everthing seems to be okay, all users can be authenticated. But a few minutes later the winbindd is suddenly unable to authenticate some users against the Domain. You can see it in the snapshot. Messages like "Unable to initgroups"

Hey Gang, I'm having some trouble getting my domain authentication to work. My config looks like this: [global] workgroup = MYWORKGROUP realm = MYDOMAIN server string = SERVER22 security = DOMAIN password server = SERVER5 obey pam restrictions = Yes smb passwd file = /etc/samba/smbpasswd pam password change = Yes passwd

Le 05/01/2020 ? 14:27, Rowland penny via samba a ?crit?: > On 05/01/2020 11:36, Ni Co wrote: >> Hello Rowloand, >> >> ok, I just keep "default" for the mounting. >> >> I changed the path of my share : >> >> [homes] >> comment = User Home Folder >> path = /home/%U >> read only = no >> follow symlinks = yes >> wide

Hello, I've got a somehow weird problem with the primary GID of samba users. passdb backend is tdbsam. when I connect to the samba server my gid is set to 2147483404 instead of 1002 (domainusers). The GID 1002 ist configured as my primary group in /etc/passwd. This also happens with other usernames. After deleting group_mapping.tdb this worked for some hours but the error came back.

I have been having a problem that has had me scratching my head for the last week and a half. I have searched with google, read the 13th hour troubleshooting guide (stopped when it got to the sniffer diagnostics), and have even upgraded samba to 3.0.0. I will post a description followed by a level 4 debug log file. When a user opens the "Public" share they can browse the share without