SMBSERVER failed, What Gives?

[ScottE]

In my seemingly neverending battle to use Samba to share files between LIN and WIN, I have been able to see the LIN Box in Network Neighborhood and ping the IP adds, but I still can't share files or ping the hostname from my WIN box.
In my troubleshooting, I have tried many, many suggestions to no avail.
At any rate, one curious thing I ran across was the following:

[root@<hostname> /root]# smbclient -L <hostname>
added interface ip=x.x.x.x bcast=x.x.x.x nmask=x.x.x.x
session request to <hostname> failed (not listening for calling name)
session request to *SMBSERVER failed (not listening for calling name)

[root@<hostname> /root]# smbclient -L localhost
on the other hand gives appropriate output.

How do you make SAMBA listen for calling name of <hostname> ?
:rolleyes:

[bdg1983]

Originally posted by ScottE:
<STRONG>In my seemingly neverending battle to use Samba to share files</STRONG>

Can you post your /etc/smb.conf (change the IPs if you wish)?

Do you have a host name entered? You'll find it (in Mandrake 8.0 menus) under:
Configuration/Other/LinuxConf
Select:
Networking/Hostname and IP network devices/Host name + domain
I have MY500 here for example.

Basically, everything else you need to do is in /etc/smb.conf. Other things I do are:
Create a /public directory, make it writable to all (it is public).
Edit /etc/smb.conf [public] section to apply to this directory.
Use the same username/passwords in all (windows, linux, and samba).

For each windows user accessing my linux box, there exists a linux user with the same name/password. Also used smbadduser for each linux user (just the window users).

Double check your workgroup name and make sure all PCs agree. Also, remember, after you change your linux box, be sure to reboot the win PCs before trying access (it is windows ya know).

[ 09 May 2001: Message edited by: RoofRabbit ]

[ScottE]

Here is my smb.conf file. Names and IP's altered but otherwise what I have in my Linux Box. RH 7.1 Samba 2.0.7.

# Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 2001/05/09 15:57:53

# Global parameters
[global]
workgroup = SIMPSONS
netbios name = HOMER
server string = Simpson's Samba Server
interfaces = 192.168.1.100/255.255.255.0 192.168.1.110/255.255.255.0 127.0.0.1/255.255.255.0
security = SHARE
encrypt passwords = Yes
ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
os level = 65
local master = No
dns proxy = No
guest account =
hosts allow = HOMER MARGE BART LISA MAGGIE
printing = lprng

[homes]
comment = Home Directories
path = /dosc
writeable = Yes
guest ok = Yes

[printers]
comment = Printers
path = /var/spool/lpd/lp
guest ok = Yes
printable = Yes
printing = bsd

[public]
comment = Public
path = /home/public
writeable = Yes
guest ok = Yes

[data]
comment = Data
path = /home/samba/data
writeable = Yes
guest ok = Yes

[SMBPRINTER]
comment = Printers
path = /var/spool/lpd/lp
writeable = Yes
printable = Yes
printing = bsd
printer = SMBPRINTER
oplocks = No
share modes = No

[netlogon]
comment = Netlogon share for Windows PDC
path = /usr/local/samba/netlogon
valid users = root HOMER MARGE BART LISA MAGGIE
force create mode = 0644
force directory mode = 0755


I'm thinking possibly my problem might have to do with xinetd.d as I don't see anything there for the tcp daemon or the fact that inetd.conf does not exist on my machine. Could also be DNS, as I'm new to the Linux OS, and am not absolutely sure I have that set up correctly but I'm determined to get it working.

Help, Anyone, Help?

[bdg1983]

Originally posted by ScottE:
<STRONG>Here is my smb.conf file.</STRONG>

Here is a copy of all used lines in my smb.conf (IPs changed lol). Note in "Host Allow" the simple "192.168.1. 127." is all you need there. There were numberous differences between the 2. Hope something here helps :-)

----------------------------------------------------
[global]
workgroup = SIMPSONS

server string = Simpson's Samba Server

hosts allow = 192.168.1. 127.

printcap name = /etc/printcap
load printers = yes

log file = /var/log/samba/log.%m

max log size = 50

security = user
encrypt passwords = yes
smb passwd file = /etc/smbpasswd

unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*

socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

domain master = yes

preferred master = yes

domain logons = yes

name resolve order = wins lmhosts bcast

dns proxy = no

[homes]
comment = Home Directories
browseable = no
writable = yes

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = no
writable = no
printable = yes

[public]
comment = Public Stuff
path = /home/public
public = yes
writable = yes
printable = no
available = yes
browseable = yes
guest only = no
only user = no

[ScottE]

Thank you very much for the help Roof Rabbit, I will amend my smb.conf and see if that helps get Samba working.

Thought you might like to know, though, I kind of found a work around to Samba and relying on it to share files with my WIN boxes.

Webmin (http://www.webmin.com/webmin/)

So far, I have been able to share files from Lin to Win with Webmin's file manager by logging in to it with my Win Box using the Lin Box host IP add, and the port it utilizes. I haven't tried the other way yet. I haven't had the chance to become incredibly familiar with it yet, but it does seem to offer an abundance of useful tools particularly for someone who is comfortable using the Web and Windows who is trying to reduce their learning curve for Linux.

I do have concerns about security issues with it though.

Thanks,
ScottE
:D

[bdg1983]

Originally posted by ScottE:
<STRONG>Thank you very much for the help Roof Rabbit, I will amend my smb.conf and see if that helps get Samba working.</STRONG>

Please post and let me know what happens :-)

[ScottE]

Turns out my Samba problems were related to my firewall configuration. I had the firewall set for high security. I went in to Lokkit:

Gnome&gt;System&gt;Settings&gt;Lokkit

and reduced some of the security settings and I can now access my files from Network Neighborhood, ping my hostname, and telnet. Somehow I was still able to access Webmin from my Windows boxes even with high security from my from firewall using solely the IP add, like so:
http://xxx.xxx.xxx.xxx:10000

Webmin is really the hot tip for anyone migrating from Bill's OS.

My Linux box is entirely experimental at this stage, so I'm not all that concerned about security right now, but at some point in the near future I hope to be able to host my online sites locally, among others.

I just wish there was a little more and better information for Linux because I believe it will reign in the end due to its affordablity, scalability, and robustness in comparison to the other widely available OSes.

Thanks to Linuxnewbie (http://linuxnewbie.org), we can come and learn from each other, during our wait, for the documentation, to catch up with the technology.

RR, Thanks for hoppin in with all your help. :D

ScottE