running SAMBA-SWAT

Port 901 (SWAT) is blocked by default with the Guarddog firewall.
Start>>System>>Security>>Guarddog

Hope this is the easy solution.

q

not that easy, since I'm new to mepis, and not overly familiar with firewalls, I diabled my firewall. In Guarddog, I went to advance and checked off disable firewall. So the firewall should not be an issue. I'm able to run https://localhost:10000 so port 10000 is open and so should?? 901

Sorry, it was worth a shot.

Tried "testparm" command from a shell?
Can you ping all of your boxes?
Tried "smbclient -N -L your_ip_here" from a shell?

In other words, is this an issue with samba or swat (having eliminated the firewall;)?

q

I have no problem pinging my other boxes. With smb4k I can see my shares and all. My problem is samba-swat, tool provided by samba to configure my local samba machine. I simply can't run swat (like the bun) on my machine (samba-swat that is).

I've been down this road before but I'm getting slow in my old age. Debian disables SWAT by default. Check your /etc/inetd.conf.
Uncomment "# swat stream tcp nowait:400 root /usr/sbin/tcpd /usr/sbin/swat". In a shell, restart inetd (kill -1 PID/inetd ("ps aux" to find the PID) and then try your browser again, "http://localhost:901/" (I don't know how to enable the https option but this should get you closer).

q

q, you may be getting older, but your definitely getting better. That's what I needed, thanks, it worked.

I am having a similar problem.

when trying to connect to localhost:901, I get doc contains no data.

added the following:

in /etc/services file > swat 901/tcp
in /etc/inetd.comf?? > added:
swat stream tcp nowait.400 root_/usr/sbin/tcpd_/usr/sbin/swat (underlines = space)
in /etc/hosts deny > changed all: all
in /etc/hosts allow > added swat:_127.0.0.1
did ps aux to find Id of inetd
did kill -1 PID
restarted smbd
restarted inetd (just to be sure)
browsw to http://127.0.0.1 and get "doc contains no data"

OK now what should I do?

PS samba is OK and working and my MS$ boxes can see the shares

Try this way- "http://localhost:901". If you browse to http://127.0.0.1 without the port number, you end up on http port 80.

q

127.0.0.1:901 gets "doc contains no data

127.0.0.1:901 gets "doc contains no data"

My bad, it wasn't clear.

Run, as root, "/usr/sbin/lsof -i |grep LISTEN" in a shell to see if swat is listening.

I learned a better way to shut down inetd-

"killall -HUP inetd"

q

with the " marks returns
no such file or dir

Remove the quotation marks.

without quotes returns this:

portmap    374   daemon    4u  IPv4    510       TCP *:sunrpc (LISTEN)
apache     479     root   16u  IPv4    654       TCP *:www (LISTEN)
cupsd      486     root    0u  IPv4   4013       TCP *:ipp (LISTEN)
apache     499 www-data   16u  IPv4    654       TCP *:www (LISTEN)
apache     500 www-data   16u  IPv4    654       TCP *:www (LISTEN)
apache     501 www-data   16u  IPv4    654       TCP *:www (LISTEN)
apache     502 www-data   16u  IPv4    654       TCP *:www (LISTEN)
apache     506 www-data   16u  IPv4    654       TCP *:www (LISTEN)
inetd      532     root    4u  IPv4    773       TCP *:swat (LISTEN)
inetd      532     root    7u  IPv4    776       TCP *:printer (LISTEN)
inetd      532     root    8u  IPv4    777       TCP *:vboxd (LISTEN)
smbd       597     root   12u  IPv4    981       TCP *:microsoft-ds (LISTEN)
smbd       597     root   13u  IPv4    982       TCP *:netbios-ssn (LISTEN)
sshd       603     root    3u  IPv4    993       TCP *:ssh (LISTEN)
vsftpd     608     root    3u  IPv4   1004       TCP *:ftp (LISTEN)
rpc.statd  623     root    6u  IPv4   1107       TCP *:805 (LISTEN)
apache    1203 www-data   16u  IPv4    654       TCP *:www (LISTEN)

bump

bump again

I wasn't required to make any changes to the hosts.allow/hosts.deny files for accessing my local network. Maybe try returning these files to their original settings.

Are you aware that running SWAT will re-write your smb.conf file?
Since things are being buggy and you already have Samba working, double check that your smb.conf file is still in tact and make a backup copy.

Beyond that, I'm stumped for the moment.

q

Below is a functioning smb.conf file (2 Mepis boxes, 2 Win2K). It is not the most secure configuration, but it works.

# Global parameters
[global]
server string = %h server (Samba %v)
security = SHARE
max log size = 1000
server signing = auto
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=4096 SO_RCVBUF=4096
printcap name = cups
os level = 65
preferred master = Yes
dns proxy = No
panic action = /usr/share/samba/panic-action %d
hosts allow = 192.168.0.0/255.255.255.0, 127.
printing = cups
print command =
lpq command =
lprm command =
printer name = printer

[homes]
comment = Home Directories

[tmp]
comment = temporary files
path = /tmp

[Printer]
path = /tmp
guest ok = Yes
printable = Yes

[test]
comment = this_is_a_test_share
path = /tmp

[user02]
path = /tmp

hi qtech,
I've been setting up a Samba file server myself. You really don't need all of that in your smb.conf. But, since it isn't causing a problem, great. Is on Mepis box your only server? Are you connecting to your Win2K boxes from your Mepis? Or are the other three connecting to the one MEPIS/Samba server? I'm going to put together a howto for folks who want to do this. A person can pick up a decent machine at yard sales or on ebay that would work great for a file server to store music, ISOs, etc.
Thanks,
Jim A.

Hi Jim,

This smb.conf is for a simple workgroup with no PDC. Every node can browse the other. One MepisPro box is a file server, the other MepisPro box handles the printer and Master Browser responsibilities. The router handles DHCP and VOIP port-forwarding.

Previously, I used an identical setup running SimplyMepis with a very basic smb.conf file, but after switching to Pro, Samba kept breaking. Using a packet sniffer, Ethereal (excellent network tool), I discovered that the Master Browser was refusing to synchronize (regardless of which computer won the browser election). Depending on who you ask, this is either a bug in Samba or an issue specific to certain older builds of Win2k/Netbios. Likewise, there are differences of opinion for solving the problem.

There are a million Samba "HowTo" guides available, but it would be really nice to have a "Samba Dance Steps for the Technologically Challenged Windows User". SWAT can be a recipe for disaster. If you write a "howto" Samba based on Mepis, I would be happy to contribute. There is a definite need for such.

q

Let me second qtech's suggestion that someone needs to write a newer/better/more-explicit-to-MEPIS HowTo on SAMBA configuration and "feeding". I too get a large number of SAMBA drops (and reboots or reconfigure) with my four computer local network (mixed MS Windows, SimplyMEPIS, and ProMEPIS). I too would be willing to contribute if I am smart enough.

qtech,
I love ethereal as well. A great network troubleshooting tool and in my last job, enabled me to find out which PCs in the organization were causing trouble for the network. You should see Blaster or the Welchia virus/worm doing it's thing through the eyes of Ethereal! I like Ettercap for sniffing traffic on the network also.

Do you find that Samba makes a better print server than the Cups Serve??? Hmm....I wonder what it was about Pro that caused the Master Browser problem??? Maybe just a coincidence?

Let me get a few things out of the way in the next few days and maybe we can start working with a few more people to put together a howto for such things as file and print servers.

Jim A.
Russell, KY USA