search for: workstats

Dear Friends, I use LDAP as the samba backend passwd in RHEL. After adding some index to LDAP, some workstation lost the trust relationship with the domain controller. The solution is to re-join the workstation to the domain, but I do not know why workstation lost the trust relationship. When I re-join the workstation to domain, I find that the workstation LDAP entry change/add the

I have setup samba with msdfs, and configured it. The problem is that it works with some windows 2000 workstations, but not with others, even if they are at the same service pak levels. I.e, I have workstation a and workstation b, both running 2000. On workstation a, I can map the dfs share to a drive, and be able to access everything in that share (which is different shares on different

I believe this has already been discussed[1], but I''d like to add a bit more to that original discussion and see if anyone has any suggestions. Here''s what I''m trying to do: we have a set of very thorough "wipe" scripts that run every night on our workstations. I''d like to stash these into a class so that I can include them as a group: class wiped

The sshgroup exists on the client/workstation: > root at lws4:~# cat /etc/groups > ..................... > sshgroup:x:998:adminlinux > ..................... > But, on my member server that acts as a fileserver for domain users (redirected) files there is no "sshgroup" at this time. The AD has server-ssh group: > root at dc1:~# samba-tool group listmembers

I hope somebody can help me with this. I posed this question a week ago and got several well-meaning answers that were not very helpful. I have 10 Windows XP workstations and 100 users. Each of the 100 users has an account on my Samba server (running Samba 3.03 on Mandrake Linux 10). Each user has several shares on the Samba server which are unique to that user. In other words, only THAT

Okay, now so I don't get confused. Yes, /home/WKDOM/tuser16 does exist on the client/workstation. root at lws4:~# getent group > root:x:0: > *..snipped for brevity..* > winbindd_priv:x:129: > sshgroup:x:998:adminlinux > postfix:x:130: > ..snipped for brevity.. > There is no servers-ssh group on the C/W. (I have a server-ssh group somewhere per Louis' instructions,

Package: logcheck-database Version: 1.3.13 Severity: normal The rule for SSH ignoring "Bad protocol version identification" assumes there are no single quotes inside the version string ('[^']'). I am however getting mails including those lines: Mar 25 22:57:04 Debian-60-squeeze-64-minimal sshd[12144]: Bad protocol version identification

Package: logcheck-database Version: 1.3.13 Severity: normal Tags: patch After upgrading to debian squeeze I get several messages a day in the form of: Jul 2 15:05:15 hostname spamd[21286]: spamd: handled cleanup of child pid [28609] due to SIGCHLD: exit 0 This is due to an update in spamd, that makes the message more detailed (includes exit code)[1]. Therefore messages including exit code 0

Package: logcheck-database Version: 1.3.8 Severity: wishlist HI, can you please create a rule/some rules for amavis(d-new). I get for every mail this mesage: May 25 19:55:40 data amavis[9603]: (09603-15) Passed CLEAN, [::1] [213.165.64.22] <xxx at yyy.zz> -> \ <aaa at localhost>, Message-ID: <20100525175015.29677page1 at mx002.bbb.ccc>, mail_id: MM7upJv6se1Z, \ Hits:

Hi, After a migration from samba 3 nt domain to samba 4 AD we have detected that Workstation Logon Restrictions (Log On To) is not working correctly, with samba 3 was working perfect, but after migration we have detected that some resources are not available, for example roaming profiles, home folders... we have tried to add as log on to workstations samba machine (dc), machine that has roaming

I am writing this email from Wildlife Institute of India, an autonomous institution of Ministry of Environment & Forests, Government of India. Our institute is involved in the research, management and training for the conservation of wildlife in India. We have a GIS and Remote Sensing laboratory having four Sun workstations on Solaris 7 and two Pentium 4 workstations on Windows NT 4.0 are

Running into a serious problem here with 3.0.24 + patches. The shop has a mix of domain member computers and privately owned non-domain member computers. I'm trying to use "net sam set workstations" to limit the workstations domain users can log onto. This limitation works as expected. And domain member workstations all work properly. But once the workstation limit is put in

The "short" version on why multiple groups here. For all my member servers apply the following. This line : > > AllowGroups servers-ssh sshgroup There are 2, linux only Admin accounts, ( local accounts ) And, only if these are member of the "local group" sshgroup then your allowed to login. Only users that are allowed to login with ssh on these servers

Hi all, I have samba4.2 (Version 4.2.0pre1-GIT-6d2f56d) as AD domain controller. Some users can only logon to specific window workstation. Now, we want to configure the samba AD as the user authentication of squid. I use the following configuration in squid. The users without workstation limitation can successfully authenticate to squid, but the user with workstation limitation cannot.

On Oct 8 2015 09:32 Rowlan Penny wrote: > It might help if you were to explain just what you require from single-sign-on ? Well, perhaps I'm mistaken, but is this not the #1 reason to install Samba4? >From reading this list over the past couple of months it does not seem that Authenticating users on Windows workstations is the main thing people do. But, is not the ability to

Sometime ago had migrated from a PDC (samba3) to an AD (samba4) environment. In the PDC environment setting the allowed workstations for each user was done with the "net sam set workstations" command and could also easily be unset (using "" as the last argument). I now wish to move to a GPO for login control but removing the limitations put in place are no longer working - I

After sending my first email, I tried to modify auth/auth_sam.c to allow groups of workstations to the workstations list. And, for my surprise (?!) it was quite easy. And worked fine. I use LDAP as sam backed, and for unix accounts and groups database. I create a test group "stations" and putted there into two of my workstations. Then I defined the "sambaUserWorkstations"

Hi all, I made a copy of a folder from a WINXP SP2 to a Linux workstation shared folder. After the copy and from the WINXP SP2 workstation, i look the properties of the remote folder (the copied folder on the Linux workstation) and of the local folder (the original folder on the WINXP workstation) For the remote folder, I have : - 29764 files - 2427 folders - Size : 6868067,965

You can see by the subject I've got an ugly problem. Even though I don't have a Samba server anywhere near the network in question, nobody understands browsing as well as the folks on the Samba team. :-) Here's the situation: I've got two workgroups, FLINTSTONE and RUBBLE which are on physically separate networks. FLINTSTONE has a Windows 2003 Active Directory domain

Dear Samba Users, I have a Samba 3.2.5 Server running on Debian. I use tdbsam as a password database and wonder how I can change the "Workstations" value in order to control the allowed workstations for a particular user. Last year I had a configuration with ldap using the smbldap tools where it was possible to set this value. But how can I set it without LDAP just using pdbedit?