[NTLUG:Discuss] Samba frustration

Wayne Dahl w.dahl4 at verizon.net
Wed Feb 26 00:19:33 CST 2003


Ok, I'm officially frustrated!  I'm attempting to get Samba set up for
my local network at home and it ain't happening.  Let me tell you what I
have here.

I have 3 computers currently on this network (with more I could put on
it).  2 are currently Windows 98 machines, the other is this one, with
Win 98/RH 8.0 as a dual boot.  I have a peer-to-peer network set up with
the Win 98 machines that works just fine on a LinkSys 4-port ADSL
router.  I can and have mapped network drived between machines and have
2 printers on 1 each of the computers and was able to map those printers
to each computer as well.  The workgroup I have them set up on is
OURGROUP (I should have something more original in there, but it works).

Ok, now I come to the Linux box.  I have SMB set up to start on bootup,
I have set up OURGROUP as the workgroup in smb.conf.  Below is what I
currently have as global parameters in it...

# Samba config file created using SWAT
# from localhost.localdomain (127.0.0.1)
# Date: 2003/02/25 23:39:18

# Global parameters
[global]
	workgroup = OURGROUP
	netbios name = LINUXHOST
	server string = Samba Server
	encrypt passwords = Yes
	obey pam restrictions = Yes
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *New*password* %n\n *Retype*new*password* %n\n
*passwd:*all*authentication*tokens*updated*successfully*
	unix password sync = Yes
	log file = /var/log/samba/%m.log
	max log size = 0
	socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
	dns proxy = No
	printing = lprng

Here are a few shares I've set up...

[homes]
	comment = Home Directories
	valid users = %S
	read only = No
	create mask = 0664
	directory mask = 0775
	browseable = No

[Wayne]
	comment = Wayne's Share
	path = /home/Wayne
	read only = No
	hide dot files = No

[Amanda]
	comment = Amanda's Share
	path = /home/Amanda
	read only = No

Based on what I've been able to find on the net and in the internal
documents located on this machine, it should work at this point.  I
should at least be able to see the Linux box from the M$ machines in
Network Neighborhood, but all I see are the Win boxes (most of the
time...sometimes all I see in Network Neighborhood is Entire Network
with no machines in it, but the network drives still work and I can
still map to them, even though Network Neighborhood doesn't display
them).

Now, per the file DIAGNOSIS.txt in the Samba /docs/textdocs/ directory,
I ran testparm smb.conf and get no errors.  I attempt the second test,
pinging WAYNESCOMPUTER and DESKPRO (the NetBIOS names of the 2 Win 98
boxes) from the Linux box and get...

[Wayne at localhost Wayne]$ ping DESKPRO
ping: unknown host DESKPRO
[Wayne at localhost Wayne]$ ping WAYNESCOMPUTER
ping: unknown host WAYNESCOMPUTER

I attempt to ping LINUXHOST from the 2 M$ boxes and get the same error. 
Now, I have Sygate Personal Firewalls on each of the M$ boxes, but I've
tried pinging them with the firewalls disabled and still get the same
error.  I CAN, however, ping the 2 Win 98 boxes from each other.

I attempted Test 3 per DIAGNOSIS.txt running "smbclient -L LINUXHOST"
and get this...

[Wayne at localhost Wayne]$ smbclient -L LINUXHOST
added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0
Connection to LINUXHOST failed

I've tried that as root also, get the same thing.  I tried running
"netstat -a" and get this at the beginning...I've shorted the response
because the rest of it is so long and doesn't appear to apply...

[Wayne at localhost Wayne]$ netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address        
State
tcp        0      0 *:32768                 *:*                    
LISTEN
tcp        0      0 localhost.localdo:32769 *:*                    
LISTEN
tcp        0      0 *:printer               *:*                    
LISTEN
tcp        0      0 *:swat                  *:*                    
LISTEN
tcp        0      0 *:mysql                 *:*                    
LISTEN
tcp        0      0 *:netbios-ssn           *:*                    
LISTEN
tcp        0      0 localhost.localdoma:783 *:*                    
LISTEN
tcp        0      0 *:sunrpc                *:*                    
LISTEN
tcp        0      0 *:x11                   *:*                    
LISTEN
tcp        0      0 *:auth                  *:*                    
LISTEN
tcp        0      0 localhost.localdom:8118 *:*                    
LISTEN
tcp        0      0 *:ssh                   *:*                    
LISTEN
tcp        0      0 localhost.localdom:smtp *:*                    
LISTEN
tcp        0      0 192.168.1.100:32832     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32864     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32797     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32972     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:33003     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32896     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32940     www.memsconference:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32833     quotationspage.com:http
CLOSE_WAIT
tcp        1      0 192.168.1.100:32865     quotationspage.com:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32798     quotationspage.com:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32973     quotationspage.com:http
CLOSE_WAIT
tcp        1      0 192.168.1.100:33004     quotationspage.com:http
CLOSE_WAIT
tcp        0      0 192.168.1.100:32897     quotationspage.com:http
CLOSE_WAIT
tcp        1      0 192.168.1.100:32941     quotationspage.com:http
CLOSE_WAIT
udp        0      0 *:32768                 *:*
udp        0      0 192.168.1.10:netbios-ns *:*
udp        0      0 *:netbios-ns            *:*
udp        0      0 192.168.1.1:netbios-dgm *:*
udp        0      0 *:netbios-dgm           *:*
udp        0      0 *:bootpc                *:*
udp        0      0 *:sunrpc                *:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ACC ]     STREAM     LISTENING     4113  
/tmp/orbit-Wayne/linc-584-0-222fece914fb5
unix  2      [ ACC ]     STREAM     LISTENING     4359  
/tmp/orbit-Wayne/linc-590-0-49f2728ecffcd
unix  2      [ ACC ]     STREAM     LISTENING     4099  
/tmp/.sawfish-Wayne/localhost.localdomain:0.0


The thing I see that looks like it could be a problem is the entry for 

udp        0      0 192.168.1.10:netbios-ns *:*

It doesn't appear to be listening.  This is for the NetBIOS nameservice,
is it not?  If this is the problem, I have found nothing so far that
would tell me how to correct it.

I have run Test 4...running "nmblookup -B BIGSERVER __SAMBA__" and get
this....

[Wayne at localhost Wayne]$ nmblookup -B LINUXHOST _SAMBA_
querying _SAMBA_ on 0.0.0.0
name_query failed to find name _SAMBA_
[Wayne at localhost Wayne]$ nmblookup -B LINUXHOST SAMBA
querying SAMBA on 0.0.0.0
name_query failed to find name SAMBA
[Wayne at localhost Wayne]$ nmblookup -B LINUXHOST Wayne
querying Wayne on 0.0.0.0
name_query failed to find name Wayne

I ran the other two because I didn't know what I was actually supposed
to put in after LINUXHOST in that command.

SOOOO.....as you can see, I've not had any success beyond "testparm
smb.conf".  There is no joy here and I'm about ready to pull my hair
out.  It just shouldn't be this hard.

What am I missing here?  Any help would be appreciated.  I hope I've
supplied you with enough info.  I have searched high and low, both in
the internal documentation and on the web and EVERYONE says "just do
this and this and this and it will work".  Well...IT DOESN"T WORK!  

One other thing that bothers me.  On the Windbloze boxes, Network
Neighborhood doesn't seem to work all the time either and I'm wondering
if that doesn't have something to do with it.  I might check NN and it
will show all the computers one time, check it again later and just get
the Entire network icon.  Double clicking that icon returns an error box
after it sits for awhile saying the network couldn't be browsed at this
time.

Sorry to take up so much bandwidth...hope this wasn't TMI.

Thanks,

Wayne




More information about the Discuss mailing list