Sorry. I wasn't very clear in my previous post. What I want is to monitor this, and action it at once.
I want to fix it before we get loads of calls from people that can't log in after their windows machine has crashed, and they
have to reboot.
I was thinking of a linux probe sitting there on the network monitoring it.. Hopefully kick the samba box till it's lying on
the ground bleeding, but I don't really see that happening. I suppose I have to settle with it sending me a mail or something.
I can get the ip address from the NT server's eventlog but by then it's a bit late.. And finding the actual host isn't the
easiest (some tings are a bit messy here at the moment (cough. Will be fixed soon.. I promise)). We have no updated record of
mac addresses either.. But this is something we have to look into.
Another thing is that this is a live production network, so starting to pull network
cables out of the hub might not be such a good thing.
I have no idea is Swat is running on the box, but I doubt it's gonna help me much as I don't have any username/password.
I admit that there isn't much I can do untill I can make som sort of map with desks=ip's.. But if I can get this monitoring
working I can get working on it before anyone even knows what's happening.
-Tor
On Fri, May 25, 2001 at 02:31:50PM +0200, Peter Kjeldsen wrote:
> Try connecting to samba on the linux box using SWAT and your browser www."IP
> address-linuxbox":901.
>> OR go to the linux box and type samba stop
>> OR disconnect all machines from the network (you can do this at the hub)
> reconnect them one by one while you after each reconnect try to log on to
> the network
> When you cannot log on you know the last machine created the problem
> Keep it disconnected until you have stopped samba at the machine and fixed
> samba.conf
>> In the meantime everyone else can work away...
>> Kind regards
> Peter
>> -----Oprindelig meddelelse-----
> Fra: Tor Bendiksen [mailto:tor at redbrick.dcu.ie]
> Sendt: 25. maj 2001 13:20
> Til: ilug at linux.ie> Emne: [ILUG] Samba/PDC problem
>>> Hi there good people.
>> I have a problem here, and I can't hink of a solution for it.
>> We have a segment with about 50 "powerusers" that each have their own little
> test setup.
> Now the problem is that now and again some gimp decides to try out those
> nice settings in smb.conf.. What happens next is that
> they will manage to make their box take over as domain admin, and our
> PDC/BDC (NT urgh!) will be knocked out. Then no one can
> log in as the samba box isn't at all set up as a domain controller, but
> rather a MP3 server for one user.
>> What I was looking for is some way of monitoring this with Linux (as I don't
> really like NT, and I don't like to sit in the
> server room staring at NT logs waiting for someone to do this.).
>> I want to monitor this segment, and if this happens then do sometihng about
> it (at the very least just mail me the ip address,
> and I can kick the muppet myself.)
>> AFAIK samba can't do this, but if someone has any idea on how to get
> something like this done, please let me know.
> Bear in mind that we have no SNMP, and are running with static ip's.
>> Regards,
> -Tor
>
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!