search for: mbarnes

Samba 2.2.8a, RH7.3 I have successfully connected machines running XP to the samba controlled domain. There are 3 XP machines, each with only one user designated as a power user (ie domain\username power user). Each can log into any of the three machines without a problem. Now I am trying to log a different person into any of these machines and I get the message "System Could Not Log

I loaded the NT4 Domain Manager tools and tried to use UserMgr to add some users. The add users sections of the menu are grayed out and I cannot do the deed. I've tried a variety of things. The machine was a member of the domain, I was logged in a administrator, which seemed to map as root in Samba, but still all I could do is look, not touch. Any ideas what I did wrong this time?

I installed CentOS 4 on a new box to use as a DNS server. It is a basic server install. I configured named and it is all up and running fine. It just isn't listening on Port 53. It also (obviously) does not respond to DNS requests. Requests from the machine itself are processed just fine, so the service is working. It just can't be used by other machines. Not good for a public DNS

I have two Samba servers on a local network. One is to eventually become the new system file server. The original server is on the domain/workgroup MCALLEN, the new server is on the domain/workgroup WRNHQ. Everything was moving along smoothly. I could see both workgroups on various Windows machines (both 98 and 2K), I could see the shares, permissions seemed good, etc. I was working on

John, It's great to see you on this list. I'm a Samba newbie and recently found your book, "Samba-3 by Example". I must say this is the best written "how-to" type of book on any subject I have ever seen. The various examples fit a number of categories and answered so many questions for me. I just wish similar books were available on other applications. I just

I'm not exactly sure if this is a Samba or other problem. I'm moving files from a Netware server to a Samba server. The Samba server is running CentOS4 and Samba 3. CentOS does not support ncpfs, so I mount the Netware volume on a Fedora box. Then, I use rsync to copy the files from the Fedora box to the Samba box. My problem is all the files seem to have the DOS 'hidden'

Can anyone tell me exactly how the various add machine/user/group/etc/ scripts work in Samba? I know how to set them up in smb.conf. That's not problem. But how are they invoked? Some use Samba specific variables like %u and %m. How do you run a script manually to use these variables? If you have an add user script and a non-user tries to log in, does it create an account for him?

Actually two issues on this subject. Migrating to a new system. First, I want to set all accounts so when the user logs in the first time, he is asked to set a new password. Second, I need to have passwords expire and require a change every 3 months. As I understand it, First, I need to set "Password must change: " to '0'. For the second one, I need to set the maximum

I cannot get this to work. Either the user's password is valid or it is not. I cannot get anything to tell or offer the user to change password. I can get the expiration date to work now, but when expiration time comes and the user tries to login, it simply says login denied, password expired. Ideas? Michael

I see lots about how the administrator uses various tools to administer users. However, if the user just wants to change his own password, how does he do it? Or can he? I'm using tdbsam for the password backend. Samba 3.0.10. Users are Win98 and Win2k. Thanks, Michael

I think I found some of my cutover problems. I found a couple Win98 machines which had the same name for user and machine names. While it never seemed to be an issue in the Netware realm, under Samba, it appears to have undesirable results. Although the machines have been renamed, there still seem to be strange problems. Any ideas on where to fix/change/clean whatever to remove the machine

I've got a moderate network with several subnets, a number of domains and workgroups. I have a central WINS server, each domain has its own PDC. My problem is transient users. We have occasional users who plug a laptop into the network. Once they leave, they hang around in Network Neighborhood forever. Then I have users who curiously click on their icon in NN and their machine just

I'm running into a permissions problem on a share. If I set the g+x on a file, it sets it as a system file in Windows. If I set o+x on a file, Windows sees it as a hidden file. This is a department share with a number of users accessing it. When I don't have the group bit for executable set, some files will not work, like Access .mdb files and some .ntf files used for a CD

This one is driving me nuts. There has got to be some way to do it. I have a Windows application that is very limited on the folders it will use. It is installed in a base folder like C:\Program Files\Application\app.exe. It uses multiple folders under that, like C:\Program Files\Application\myfile, C:\Program Files\Application\yourfile, C:\Program Files\Application\bobsfile, etc. Here's

How do I establish both a user's primary NTgroup and Unixgroup when creating a new user? Depending on the tool, I can set his NTgroup or his Unix group, but I don't seem to be able to establish both with one tool. I'm having a little difficulty with creating users with the proper groups. My login scripts are based on the user's primary group. When I create a new user with

I'm having problems adding users with usrmgr. I can run the scripts from my smb.conf fine from command line and do what I need to. But, when adding users with usrmgr, the login script and path statements are not identified and I have to go in and edit them manually. Does adding a user with usrmgr not use the add user script from Samba? Or must the user environment variables be added