similar to: Using UNIX passwords

The Samba FAQ mentions a program called timesync to update the system clock on clients from the server. The download address in the FAQ is out of date - where can I get a copy ? Geoff -- ---------------------------------------------------------------------------- Ever sit and watch ants? They're always busy with Geoff Short something, never stop for a moment. I just

Bloody H3ll... I replied only to the person who sent it. Hey, maybe this list could stick a Reply-To field to the incoming messages before broadcasting them? Juan Carlos Castro y Castro wrote: > Andrew J Miles wrote: > > > Hello all, > > > > We've just started using MS Visual C++, and have a problem that I believe > > might be related to the samba server. >

Helooooww ow ow... -- ROTINJAILPINOCHET*APODRE?ANACADEIAPINO * Valeu, LORDES! C T That's it LORDS! H E Enhorabuena LORDES! E OGY IS POLICY @ THE END HCONIPLECRACALNESARDUPETEUQ*LIAJNITORT L ***************** O * FIGHT * UST NO ONE @ DE E @ BELIEVE THE LIE @ AP * THE *

Thanks, Juan Carlos. I needed some more specifics such as which document had the info, but I eventually found it once I'd been assured it was really there. I'll give it a try tonight. -- Gregor Mosheh An NT server can be run by an idiot, and usually is. "If you can't make it good, make it LOOK good." - Bill Gates

Funny thing happening with an NT Client: it sees all the files in a public Samba share, but when I make any change (like renaming a file or dropping files into it) the change doesn't show up in the window until I press F5 (Refresh). Is it some config in Samba whichs defaults to "lazy" behavior which I'm failing to see? Thanx 4All, Juan --

Please excuse me if this has been covered, but I just noticed something odd with samba 2 beta 1. If I use smbclient to connect to a passworded resource on a win machine (I've tried it with 98/95) and I just hit enter for the password, it lets me in. No questions asked. So, I pretty much have unlimited read access to stuff I should not be able to get to. Best Regards. If this is the wrong

I want to install a linux samba server to serve 30 win9x machines. I want to prevent users from writing on the local drives, they should have write access only to their home dirs on the samba box. These users have a nasty habit of deleting crucial system files. Is it at all possible with win9x and samba? Of course NT workstations could resolve the problem, but that's not an option with these

I have samba installed on a web server (behind a firewall). It's working fine with all the WINS networking here (eg, password authentication from the NT servers, etc). I (we) want this web server - a linux redhat 5.x box currently running samba-1.9.18p8 - to have as few actual unix login accounts as possible. What I want/need to do is to allow LOTS of people in the faculty here