similar to: Swat, winbind, authentication, @DomainAdmins

Hi all... I need to make a few queries to WINS, but am unsure how to do so. 'nmblookup' will allow me to enter an IP address and get information about the machine name, domain, and username. I want to do the opposite...I would like to have a tool that will take a username and return the IP address. I know this information is stored in WINS somehow, and I am capable of writing some Perl

I'm getting really frustrated again...please help. Would someone please answer these questions and maybe I can figure out what is wrong with my installation: 1. I can add printers in CUPS, and they show up in Samba (after a 'service smb restart'). I can see them when I surf to \\waifer <file://\\waifer> (the name of the Samba server), but when I double-click on them there, it

I'm running samba 2.2.2-6 on a redhat 7.2 box running 2.4.9-7 kernel... I'm trying to upload printer drivers from a Windows 2000 client. I've followed the instructions in the samba howto collection. I've created the print$ share, created the printer directory and subdirs, and made sure they are writeable by me. I put myself in the write list and the printer admin list.

On friday I was having a heck of a time using Samba...especially in regard to CUPS and printing. I posted on the list some big questions about my setup and what could be done with it, and was a little disheartened not to get an answer. Later that day, completely out of the blue, I received a long-distance call from John H. Terpstra, one of the Samba lead people. He must have tracked down my

Boy this was a big scary headache! As well, I really wish the samba upgrade didn't wipe my changes to /etc/pam.d/samba and /etc/rc.d/init.d/smb (back them up instead, please). Situation: Upgrading Samba from 2.2.4 to 2.2.5. Samba is using winbindd for authentication. Problem: Under 2.2.4, smb.conf originally contained a password server specified by IP address: password server

Hello all: Here's the problem [on a RH7 running kernel 2.2.17-14 with Samba 2.0.7-21ssl and xinetd-2.1.8.9pre14]: http://localhost:901 does bring up the SWAT login dialog box.. but upon entering root as the user, followed by my root passwd in the next entry... it tells me "Authentication failed. Retry?" I can tell you that I did enter the correct root passwd, because I am root

Hi everyone, In the last few days I've spended hours and hours on the web surching for a solution to my problems. Eventhough it looked like there where several other people having the same problem I couldn't find a way to solve it. Therefore I'm hoping that one of you could help me with the following problem. I've installed Samba 3.0.14a on RedHat 9.0. Samba is working perfectly.

Hello: I have samba-2.2.5-1 running in RedHat 7.3, but I get the page cannot be displayed message when I go to http://sambaserver:901 My /etc/etc/xinetd.d/swat file looks as below. I have removed only_from = localhost and changed disable = yes to no service swat { port = 901 socket_type = stream wait = no user = root server = /usr/sbin/swat

Ok, I should be able to start swat with xinetd, but I can't seem to get anything to start. 1. How do I tell if swat is running (other than trying to browse to aaa.bbb.ccc.ddd:901) 2. Can someone give me an idea of what and where I need commands for xinetd. Server is RH7.2, Samba 2.2.3a, following file "swat" is in /etc/xinetd.d/ ## /etc/xinetd.d/swat service swat { port

Hello All Samba-list Members, I have installed a Samba 2.2.7, the samba-latest.tar.gz, as a PDC on a Redhat8.0 GNU/Linux server. ( Of course, I first uninstalled the original samba that came with the Redhat installation CDs by rpm -e samba*.) The installation was successful. Then I modified /etc/services and /etc/xinetd.d/swat as suggested in the installation document uncompressed from

I'm using Suse 9.1 professional. I've got Samba *almost* up and running. But, I'm a newbie and need Swat to configure a few things. I've gone to /etc/services and made sure that I have the entry "swat 901/tcp" I have checked /etc/xinetd.d/swat and added "port = 901" and changed it to "disable = no" I have gone through the steps in the

Hello, I am not able to access SWAT from any other host besides the one running the SWAT daemon. No firewall blocking access on either side. # netstat -lnt | grep 901 tcp 0 0 0.0.0.0:901 0.0.0.0:* LISTEN works fine connecting from localhost using: lynx localhost:901 Unavailable using public IP on a remote host.. i.e. going into Firefox and

hola, habla usted ingles? bueno, revise bien que 'xinetd' este instalado y corriedo como servicio: ps -ae | grep xinetd si resulta que si, entonces revise el documento de configuracion de swat (/etc/xinetd.d/swat): # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. To use SWAT, \ # connect to port 901

Hello, I have recently updated the Samba 3.6.14 to 3.6.21 on a Gentoo server PACKAGE.USE = net-fs/samba acl aio caps client ldap netapi pam readline server smbclient winbind -addns -ads -avahi -cluster -cups debug -dmapi doc -examples fam -ldb quo 1st issue I cannot get SWAT to connect using my Windows 7 PC to my linux samba server using (http//:ip_address of samba server:901 I have port 901 open

Hi Sean, I had this problem when I upgraded our servers to RedHat 7. In RedHat 7 they changed from running the inetd.d to running xinetd.d. This is the daemon that figures out what programs to start when a port is accessed. Port 901 is for swat, this is configured in your /etc/services file. In the /etc/xinetd.d/ directory you'll find a file called swat. Edit this file so it looks

Hi, I'm a linux newbie so be nice. I have recently installed a Smoothwall Express 2 firewall with fixes7, and am trying to get a Samba server to run on this machine. I compiled the lastest stable release of samba on this machine and it seemed to go fine. I then compiled xinetd and configured the xinetd.conf file for SWAT. Using a putty SSH session I ran the the command xinetd -d to

IT WORKS!!!!!!!!!!! But before I say what I did... yall have to promise not to laugh! (MAH!! I HEAR YOU!!) ... anyone ever heard of.... /etc/rc.d/init.d/xinetd restart I can tell you from experience that 'killall -HUP xinetd' is NOT the same. I can also say that nobody will find that command line entry in "Using Samba". To show my appreciation to the groups involved,

I know there have been previous threads about this, but I don't think they match my problem. I have the xinetd script provided by the Samba.org 2.2.6 binary RPM, and when I enable it and reload xinetd, I see xinetd listening in a `netstat --ip -lnp` command. When I point my browser at http://localhost:901/ I'm given an Alert dialog window stating "Document contained no

Sorry for the direct post.... Eric Hines -------- Original Message -------- Subject: Re: [Samba] can't connect to swat Date: Sun, 16 Apr 2006 08:51:45 -0500 From: EHines <eehines@comcast.net> To: Larry Weldon <lweldon@weldoncomputers.com> References: <02a201c66148$c8925290$0c46a8c0@jshinotebook> <1145194206.20034.72.camel@tiger.home.welcoin.com> Larry Weldon

Hitting a big mystery here. I've configured samba properly but I would like to run swat. The /etc/xinetd.d/swat file contains: service swat { disable = no port = 901 socket_type = stream wait = no only_from = 127.0.0.1 user = root server = /usr/sbin/swat log_on_failure +=