Samba 2.2.8a on Suse 8 (part of SLOX system - no I can't upgrade until Suse upgrade the system) Windows XP Pro clients Are failed client logins on the XP clients logged anywhere ? How about non-domain member clients accessing shares ? I've been asked to provide a log of failed login attempts with a view to spotting break-in attempts (apparently auditors like that sort of thing). There doesn't seem to be anything useful in syslog, log.smbd, or log.nmbd. Simon -- Simon Hobson MA MIEE, Technology Specialist Colony Gift Corporation Limited Lindal in Furness, Ulverston, Cumbria, LA12 0LD Tel 01229 461100, Fax 01229 461101 Registered in England No. 1499611 Regd. Office : 100 New Bridge Street, London, EC4V 6JA.
> Are failed client logins on the XP clients logged anywhere ? > How about non-domain member clients accessing shares ?It completely depends on your logging settings. Perhaps show your smb.conf global section so we can tell. In my setup, and from the looks of things around here, a lot of other peoples, is that there is a main log.smbd file and then also a log for each machine. Check in those if you are so configured. I'm sure we'll have better info for you once we see your globals. -- -- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Systems Architect Fax: 701-281-1322 URL: www.ae-solutions.com mailto: pgienger@ae-solutions.com
Maybe Matching Threads
- Combining NFS and Samaba - file locking
- Can't print properly through server, only direct client->printer
- Can't print properly through server, only direct client->printer
- SCO OpenServer 5.0.6a and missing libncurses.so.4
- Suse Linux OpenExchange Server (Samba 2.2.5) and XP