search for: avarachen

...ptions = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no wins server = 10.55.56.4 <http://10.55.56.4> name resolve order = wins lmhosts bcast My krb5.conf file is similar to the one in Samba-Guide (and I knwo this works since I can join the Linux host to AD directory) Thanks, Vijay Avarachen -- "Knowledge is the only wealth that grows as you spend it, and diminishes as you save it." -- ancient Sanskrit saying

...the users home directory will be when he/she logs in. In system.auth there is a way you can set it to create the home directories automatically. Search for mkhomedir parameter. * if you do not get a valid output for getent passwd user.name authentication is not going to work # getent passwd vijay.avarachen vijay.avarachen:*:161167:150000:VijayAvarachen:/home/NA/vijay.avarachen:/bin/bash Once you have everything working, I recommend turning on nscd. Nscd will never cache passwords. Passwords are always verified live against AD. I hope this helps people out there....I know there is more I can writ...

This might be a stupid question, but I ask only because I can't think of a good reason... Why do so many vendors' builds of Samba not include libnss_wins, the WINS/NetBIOS name resolution library? I find that it is very helpful for my Linux/Samba servers to be able to resolve hostnames by WINS. It also seems to improve domain browsing performance dramatically to have the library present

I'm trying to do something fairly simple: login to a Linux box using a Windows AD-based account. I've followed the various recipes available online for configuring Linux (winbind, PAM, etc.) to this send, and I've got it working ... almost. I'm able to authenticate an AD-based user immediately after bringing up the Linux box, but a short time later (roughly 5 minutes, but it

Hi everybody, This may be a stupid question, but I really don't get it. When I restart my Linux box (occasionnaly / rarely), samba is not working from my Windows station. I can't connect to the samba drive. If I do /etc/init.d/smb restart, it doesn't work either. After many unsuccessfull problem determination, I found that there is two ways to correct this: 1- kill smbd -D process

I am looking for some solution, working with Samba preferably, which would allow multiple users to work on one document. This means that if a user makes a change to the document, a previous version of that document is saved somewhere else. For example, user A opens a document (rw - read/write, ro - read-only document): rw \\server\share\document.txt User makes some changes, and saves it to