similar to: swat questions

I have gotten Samba to work but them came up with a problem. It is working on a mchine with the class C address 198.xxx.xxx.xxx. Any PC's with that on that IP address can see the server just fine. However, we also have another class C 207.xxx.xxx.xxx and folks on that one cannot see the server. We have seen this problem before and NetBeui solved that one. Any ideas? Thanks in advance.

Hello all, I have asked this before but I have not found a solution. I have one Dec Alpha running Tru-64-UNIX, formerly DecUNIX, v4.0d. I am running 2.0.2 and have run 2.0.0 with no problems. SWAT works fine on it also. I have 2 other systems, one running v4.0d and the other running v4.0b. On those systems I can connect to guest volumes just fine but anything that requires a password fails

Hello all, In addition to what I wrote this morning I just ran Test 8 from DIAGNOSIS.txt and it worked but Test 9 didn't. I got invalid password error. I am not running shadow passwords and passwords are not encrypted. Please HELP!!!! I have asked this before but I have not found a solution. I have one Dec Alpha running Tru-64-UNIX, formerly DecUNIX, v4.0d. I am running 2.0.2 and have run

I would like to see those of us who send an inquiry to this list also send a summary of what fixed the problem so that someone in the future could find the answer. I searched archives for an answer and only found questions. Since a lot of folks reply ot individuals then even the replies don't end up in the archives and so it would be nice if summaries were sent to the list. Anyway, enough

I have some new information concerning this issue. I am now able to change both the samba and unix passwords as anyone but root. If I try as root I only am able to change the samba password but not the unix password. I can do this at the unix prompt as well as in swat. So it works but why root can't change both of them makes no sense to me. root can't even change both for root,

I got the answer. I set up swat and found that security was set to user. When I set it to share things work like they did in 1.9.18p10. The manpages say that security = share is the default but I don't think so. Original question: This is the first problem I have had with samba, that I can't find the answer to, since I first started to work with samba. I am running DecUNIX 4.0d and I

I have been kind of fortunate in adjusting my SWAT information, and now can reach the SWAT3 interface through port 902 (thanks!), but now I have an even more interesting snag. Konqueror and Mozilla, when going to localhost:902 (what I set SWAT3 to respond to), will prompt a login box. The site is called "SWAT at localhost". I put in the root username, and the root password. It then

Hi Using 2.2.1a and getting 401 SWAT Bad Authorization error. If I use the -a option everything is OK. The documentation refers to the -a option which leaves everything wide open but I can't find any documentaion regarding any other form of access control for SWAT. What actually controls the access? We installed from source with no selected config options. Hope someone can help, I have

I just compiled and installed 2.0.6 and fired up SWAT. SWAT's security is much different from previous versions, where a user with only read permission could use it, but without the commit changes and delete buttons. With 2.0.6 if you can't write globals or shares, you can't see them and don't even get the share or global navigation buttons. Anyone who can see the global or share

I give up. I had this working and now it isn't and I don't know why. I was able to sync unix password using smbpasswd but now it won't work. When I run smbpasswd it changes the samba password but acts like it doesn't even see the parameters in the smb.conf to change the unix password. Here is a sample changing session: as400:# ./smbpasswd xxxxxx New SMB password: Retype new

Hi all, I've upgraded from 2.0.x to 2.2.2 on a Tru64 5.1 box. I try to start SWAT with root and roots password and get a : 401 Bad Authorization username or password incorrect With a non root account I can access, but not manage the server. What' wrong? Thanks in advance Roman

Hi.. I'm running Samba 2.0.7 on a RH 6.0 box... Now, this box is using NIS for authentication, such that I have no entry in the passwd file, but show up with a `ypcat passwd`. I have made a group called 'swat' and have added myself to it, such that doing a `groups wkim` lists swat as one of my groups. I then `chgrp swat smb.conf` and `chmod 664 smb.conf`. Yet, if I try to access

Hi, I'm having a minor issue with swat on red hat 7.2. It won't let me make any changes to the samba server (adding shares, printers, and global definitions). The buttons to access these simply don't exist. I can view status, but I can't make any changes (not even restart the daemons). This works fine on my Debian system. The only real difference that I can think of is inetd

We are trying out samba 3.2.8. All of our samba servers have multiple network interfaces. With version 3.0.31 we were able to use Socket address = xxx.xxx.xxx.xxx, 127.0.0.1 and nmbd worked fine as did swat. With 3.2.8 that syntax causes nmbd to crash and complain about an invalid address. If we adjust the syntax to use Socket address = xxx.xxx.xxx.xxx Or socket

Hi, I would like to suggest a modification to the SWAT web gui. I have been successfully using Samba for a few years now at my institution and it is a great product. We use it here to handle all of our file serving for around 11,000 users. We have 3 Sun E450's serving up to a 1000 clients each at any one time with no problems. That's the background, here is my request. In the SWAT gui

Hello, I am running a small network, Win., FreeBSD (Unix), & Macs., administering through SWAT. Needing to run an intranet I installed an Apache 1.3 HTTP server running in standalone mode. Now I have lost the ability to access SWAT through the http://xxx.xxx.xxx.xxx:901 port. Guess it requires some special configuration of the server - SWAT runs in inetd mode, will this cause a conflict?

Hi all, My setup is: Ubuntu 10.04.3 LTS Samba/Swat 3.4.7~dfsg-1ubuntu3.8 I apply min password age both on Unix and Samba. I test SWAT and it seems to be working fine, except after few days I notice that changing password from SWAT doesn't modify the "Last password change" on unix password. As the result now the info on my account is: - Unix last password change: Mar 25, 2012 -

I am almost new to samba and the installation and every thing else went smooth through Linux Redhat 6.2, but unfortunately I am unable to login thought Swat while the user exist in this file "/etc/ smbpasswd" This is the message coming from my browser using 401 Bad Authorization username or password incorrect The mapping from windows and printing is excellent. Can some one help

hi all, I just installed samba 2.2.0 on a Digital SMP server and I can tell that administering it via SWAT is the bigest step since man walking on the moon. but... SWAT eroneously reports smbd/nmbd not working while they are working. And even more, the smbd/nmbd [start]/[restart] buttons have dissapeared. Why is that ? Claudiu premises: hardware: Digital server 2xPII 266/128MB/2x4GB SCSI

Did you make sure localhost resolves? Also, depending on your /etc/resolv.conf, you may have to fully qualify the host's name including the DNS domain. I seem to rember having problems with this, and some combination of using localhost or hostname.domain.edu or using the actual IP address of the host cleared up the problem. Karen Wieprecht -----Original Message----- From: Noel Kelly