Tom, does this box know its own name? ..ping boslinux below looks like its name is ..localhost.localdomain ..(redhat and similar often doesen't setup hosts correctly.) Richard Coates.
On Tue, 2003-09-23 at 05:25, Tom Whiteford wrote: > Let's see I've got a network about 10 PCs running XP and 1 running > Linux. I had setup Samba and it was running like a charm. XP pcs > could access linux box through network neighborhood and access 2 > shared dir and edit/change files. > > Really not sure what has gone wrong. I am using Samba 2.2.8a > > I run both smbd and nmbd as daemons. When I run ps -aux they show up. > > root 1553 0.0 0.1 4664 1788 ? S 14:34 0:00 > /usr/local/samba/bin/smbd -D > root 1555 0.0 0.1 3668 1652 ? S 14:34 0:00 > /usr/local/samba/bin/nmbd -D > root 1556 0.0 0.1 3616 1380 ? S 14:34 0:00 > /usr/local/samba/bin/nmbd -D > > When I run netstat -a .... looks like netbios-ssn is set to LISTEN. Also > netbios-ssn is > defined as 139 in /etc/services > > [EMAIL PROTECTED] etc]# 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 *:swat *:* LISTEN > tcp 0 0 localhost.localdo:32773 *:* LISTEN > tcp 0 0 *:netbios-ssn *:* LISTEN > tcp 0 0 *:sunrpc *:* LISTEN > tcp 0 0 *:http *:* LISTEN > tcp 0 0 *:x11 *:* LISTEN > tcp 0 0 *:ssh *:* LISTEN > tcp 0 0 localhost.localdom:smtp *:* LISTEN > tcp 0 0 boslinux:32869 cs52.msg.sc5.yahoo:5050 ESTABLISHED > udp 0 0 *:32768 *:* > udp 0 0 boslinux:netbios-ns *:* > udp 0 0 *:netbios-ns *:* > udp 0 0 boslinux:netbios-dgm *:* > udp 0 0 *:netbios-dgm *:* > udp 0 0 *:sunrpc *:* > Active UNIX domain sockets (servers and established) > > > Everything looks good. But when I run smbclient I get .... > > [EMAIL PROTECTED] etc]# /usr/local/samba/bin/smbclient -L localhost > added interface ip=192.168.1.80 bcast=192.168.1.255 nmask=255.255.255.0 > timeout connecting to 127.0.0.1:139 > Error connecting to 127.0.0.1 (Operation already in progress) > Connection to localhost failed > > > I had this problem and actually uninstalled all Samba RPM packages and then > installed all over again using latest.tar.gz > > hosts.allow file is set to ALL:ALL and nothing in hosts.deny > > no firewall settings > > The ultimate problem is that my XP PCs can see my linux pc (boslinux) but can't > connect to it when I double-click on it in Network Neighborhood ... error is ... > > "\\Boslinux is not accessible. You might not have permission to use > this network resource ... The network path is not found." > > SAMBA is working to some degree ... the pcs can see the > linux box name in network neighborhood. If I edit smb.conf and change > workgroups the pcs eventually see the linux box in the new workgroup > (although we have too many hubs and there is a long latency issue). > > > Misc notes ... > => I've rebooted both Linux and XP machines many times > => SWAT takes forever when clicking on STATUS > => SWAT server status shows nmbd: running > => BUT smbd: not running EVEN THOUGH smbd is running when using ps -aux ???????? > => At DOS prompt $ pind boslinux returns fine > > > Also sometimes this error occurs when the PC tries to simply access > it's own workgroup !!!! However they do eventually recover and can > access other PCs and directories !!!!!!!! > > > Here's my smb.conf file .... > > > # Samba config file created using SWAT > # from localhost.localdomain (127.0.0.1) > # Date: 2003/09/19 15:58:02 > > # Global parameters > [global] > workgroup = BZZAGENT > server string = Linux Server > security = SHARE > encrypt passwords = Yes > log file = /var/log/samba/%m.log > max log size = 0 > dns proxy = No > guest account = guest > printing = lprng > > [homes] > comment = Home Directories > valid users = %S > read only = No > create mask = 0664 > directory mask = 0775 > browseable = No > > [printers] > comment = All Printers > path = /var/spool/samba > printable = Yes > browseable = No > > [tmp] > path = /tmp > username = guest > read only = No > guest ok = Yes > > [internalsite] > path = /usr/local/internalsite > username = guest > read only = No > guest ok = Yes > > > > SAMBA seemed pretty easy when I first set it up. Basically configure > smb.conf then run /usr/sbin/smbd then /usr/sbin/nmbd. But I'm lost > now ... > > Here are log.nmbd .... > > [2003/09/19 15:59:53, 0] nmbd/nmbd.c:sig_term(65) > Got SIGTERM: going down... > [2003/09/19 16:00:30, 0] nmbd/nmbd.c:main(798) > standard input is not a socket, assuming -D option > [2003/09/19 16:13:59, 0] nmbd/nmbd.c:sig_term(65) > Got SIGTERM: going down... > [2003/09/19 16:25:00, 0] > nmbd/nmbd_become_lmb.c:become_local_master_stage2(405) > ***** > > Samba name server BOSLINUX is now a local master browser for > workgroup MSHOME on subnet 192.168.1.80 > > ***** > [2003/09/19 16:28:38, 0] > nmbd/nmbd_incomingdgrams.c:process_local_master_announce(307) > process_local_master_announce: Server ADMIN2 at IP 192.168.1.204 is > announcing itself as a local master browser for > workgroup MSHOME and we think we are master. Forcing election. > [2003/09/19 16:28:38, 0] > nmbd/nmbd_become_lmb.c:unbecome_local_master_success(155) > ***** > > Samba name server BOSLINUX has stopped being a local master browser > for workgroup MSHOME on subnet 192.168.1.80 > > ***** > [2003/09/19 16:28:57, 0] > nmbd/nmbd_become_lmb.c:become_local_master_stage2(405) > ***** > > Samba name server BOSLINUX is now a local master browser for > workgroup MSHOME on subnet 192.168.1.80 > > ***** > [2003/09/19 16:52:49, 0] nmbd/nmbd.c:sig_term(65) > Got SIGTERM: going down... > [2003/09/19 17:11:55, 0] > nmbd/nmbd_become_lmb.c:become_local_master_stage2(405) > ***** > > Samba name server BOSLINUX is now a local master browser for > workgroup BZZAGENT on subnet 192.168.1.80 > > ***** > > and log.smbd ..... > > > [2003/09/19 15:20:11, 1] smbd/server.c:main(679) > smbd version 2.2.1a started. > Copyright Andrew Tridgell 1992-1998 > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
