Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unfortunately, my Debian, or Gnome, was somehow corrupted and crashed. My UserID would not allow logins of any kind, except for the console. I ended up re-formatting my hard drive and doing my Debian Installation from scratch.
I have not followed my normal instincts to tinker with or make any changes to the installation.
However, my new Samba will not share. I went back through the recommendations in my other Samba thread. The Hosts file was updated and the smb.conf file shows the 'workgroup = DAD'.
I have added a user and password to Samba.
I can see and use the network printer.
I can not see the Linux system from the Windows systems and the Linux system does not see the Windows systems. The windows systems do see, and allow access, with each other.
When I use the command 'smbclient -L //DAD' I get the following error:
Quote:
Connection to DAD failed (Error NT_STATUS_BAD_NETWORK_NAME)
When I checked the Samba Status with SWAT, I found that the 'nmbd daemon' is not running. It will not start.
Once again, I am searching for a way to share files between my Windows Systems and the Linux System.
Here is my smb.conf
Quote:
[global]
netbios name = Samba24
server string = Samba file and print server
workgroup = DAD
security = user
hosts allow = 127. 192.168.0.
interfaces = 127.0.0.1/8 192.168.0.0/24
bind interfaces only = yes
remote announce = 192.168.0.255
remote browse sync = 192.168.0.255
printcap name = cups
load printers = yes
cups options = raw
printing = cups
guest account = smbguest
log file = /var/log/samba/samba.log
max log size = 1000
null passwords = no
username level = 6
password level = 6
encrypt passwords = yes
unix password sync = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
local master = no
domain master = no
preferred master = no
domain logons = no
os level = 33
logon drive = m:
logon home = \\%L\homes\%u
logon path = \\%L\profiles\%u
logon script = %G.bat
time server = no
name resolve order = wins lmhosts bcast
wins support = no
wins proxy = no
dns proxy = no
preserve case = yes
short preserve case = yes
client use spnego = no
client signing = no
client schannel = no
server signing = no
server schannel = no
nt pipe support = yes
nt status support = yes
allow trusted domains = no
obey pam restrictions = yes
enable spoolss = yes
client plaintext auth = no
disable netbios = no
follow symlinks = no
update encrypted = yes
pam password change = no
passwd chat timeout = 120
hostname lookups = no
username map = /etc/samba/smbusers
smb passwd file = /etc/samba/smbpasswd
passwd program = /usr/bin/passwd '%u'
passwd chat = *New*password* %n\n *ReType*new*password* %n\n *passwd*changed*\n
add user script = /usr/sbin/useradd -d /dev/null -c 'Samba User Account' -s /dev/null '%u'
add user to group script = /usr/sbin/useradd -d /dev/null -c 'Samba User Account' -s /dev/null -g '%g' '%u'
add group script = /usr/sbin/groupadd '%g'
delete user script = /usr/sbin/userdel '%u'
delete user from group script = /usr/sbin/userdel '%u' '%g'
delete group script = /usr/sbin/groupdel '%g'
add machine script = /usr/sbin/useradd -d /dev/null -g sambamachines -c 'Samba Machine Account' -s /dev/null -M '%u'
machine password timeout = 120
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /dev/null
winbind use default domain = yes
winbind separator = @
winbind cache time = 360
winbind trusted domains only = yes
winbind nested groups = no
winbind nss info = no
winbind refresh tickets = no
winbind offline logon = no
[homes]
comment = Home Directories
path = /home
read only = no
available = yes
browseable = yes
writable = yes
guest ok = no
public = no
printable = no
share modes = no
locking = no
[netlogon]
comment = Network Logon Service
path = /home/netlogon
read only = no
available = yes
browseable = yes
writable = no
guest ok = no
public = no
printable = no
share modes = no
locking = no
[profiles]
comment = User Profiles
path = /var/samba/profiles
read only = no
available = yes
browseable = no
writable = yes
guest ok = no
public = no
printable = no
locking = no
create mode = 0600
directory mask = 0700
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
writable = no
guest ok = no
public = no
printable = yes
share modes = no
locking = no
[pdf-documents]
path = /home/pdf-documents
comment = Converted PDF Documents
available = yes
browseable = yes
writeable = yes
guest ok = yes
[pdf-printer]
path = /tmp
comment = PDF Printer Service
printable = yes
guest ok = yes
use client driver = yes
printing = bsd
print command = /usr/bin/gadmin-samba-pdf %s %u
lpq command =
lprm command =
DAD is the workgroup name not the netbios name.
The computer netbios name is samba24 which is what you want to use when using the smbclient command.
Look at the error logs nmbd error logs to see why its not starting.
DAD is the workgroup name not the netbios name.
The computer netbios name is samba24 which is what you want to use when using the smbclient command.
Look at the error logs nmbd error logs to see why its not starting.
Thanks. After logging in as root I was able to find the error logs. Why can't I just have a user login with administrative rights?
Anyway, In one point of the log it says that nmdb is running and then when I check the Status the nmbd is not running. Most of the error log does not tell me, a novice, where the problem lies. Here is part of the log:
Quote:
*****
[2009/12/28 08:12:57, 0] nmbd/nmbd_incomingdgrams.crocess_local_master_announce(308)
process_local_master_announce: Server JEAN at IP 192.168.11.9 is announcing itself as a local master browser for workgroup DAD and we think we are master. Forcing election.
[2009/12/28 08:12:57, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(148)
*****
Samba name server AHWEBS has stopped being a local master browser for workgroup DAD on subnet 192.168.11.7
Samba name server AHWEBS is now a local master browser for workgroup DAD on subnet 192.168.11.7
*****
[2009/12/28 08:25:00, 0] nmbd/nmbd_incomingdgrams.crocess_local_master_announce(308)
process_local_master_announce: Server JEAN at IP 192.168.11.9 is announcing itself as a local master browser for workgroup DAD and we think we are master. Forcing election.
[2009/12/28 08:25:00, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(148)
*****
Samba name server AHWEBS has stopped being a local master browser for workgroup DAD on subnet 192.168.11.7
Samba name server AHWEBS is now a local master browser for workgroup DAD on subnet 192.168.11.7
*****
[2009/12/28 08:37:02, 0] nmbd/nmbd_incomingdgrams.crocess_local_master_announce(308)
process_local_master_announce: Server JEAN at IP 192.168.11.9 is announcing itself as a local master browser for workgroup DAD and we think we are master. Forcing election.
[2009/12/28 08:37:02, 0] nmbd/nmbd_become_lmb.c:unbecome_local_master_success(148)
*****
Samba name server AHWEBS has stopped being a local master browser for workgroup DAD on subnet 192.168.11.7
Samba name server AHWEBS is now a local master browser for workgroup DAD on subnet 192.168.11.7
*****
[2009/12/28 08:40:14, 0] nmbd/nmbd.crocess(646)
Got SIGHUP dumping debug info.
[2009/12/28 08:40:14, 0] nmbd/nmbd_workgroupdb.c:dump_workgroups(281)
dump_workgroups()
dump workgroup on subnet 192.168.11.7: netmask= 255.255.255.0:
DAD(1) current master browser = AHWEBS
AHWEBS 40849a03 (ahwebs server)
AHTESTBED 40011003 ()
ALIVE 40011607 (Andes Help)
REDONE 40001203 (First)
[2009/12/28 08:43:42, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 08:43:42, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
create_subnets: No local IPv4 non-loopback interfaces !
[2009/12/28 08:43:42, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
create_subnets: Waiting for an interface to appear ...
[2009/12/28 10:15:47, 0] lib/interface.c:load_interfaces(543)
WARNING: no network interfaces found
[2009/12/28 10:16:37, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 10:16:37, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
create_subnets: No local IPv4 non-loopback interfaces !
[2009/12/28 10:16:37, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
create_subnets: Waiting for an interface to appear ...
[2009/12/28 10:23:45, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 10:23:45, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
create_subnets: No local IPv4 non-loopback interfaces !
[2009/12/28 10:23:45, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
create_subnets: Waiting for an interface to appear ...
[2009/12/28 10:30:05, 0] lib/interface.c:load_interfaces(543)
WARNING: no network interfaces found
[2009/12/28 11:58:52, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 11:58:52, 0] lib/pidfile.cidfile_create(120)
ERROR: nmbd is already running. File /var/run/samba/nmbd.pid exists and process id 2608 is running.
[2009/12/28 11:59:10, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 11:59:10, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
create_subnets: No local IPv4 non-loopback interfaces !
[2009/12/28 11:59:10, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
create_subnets: Waiting for an interface to appear ...
[2009/12/28 15:37:40, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 15:37:40, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
create_subnets: No local IPv4 non-loopback interfaces !
[2009/12/28 15:37:40, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
create_subnets: Waiting for an interface to appear ...
[2009/12/28 15:58:57, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/28 15:58:57, 0] nmbd/nmbd_subnetdb.c:create_subnets(206)
create_subnets: No local IPv4 non-loopback interfaces !
[2009/12/28 15:58:57, 0] nmbd/nmbd_subnetdb.c:create_subnets(207)
create_subnets: Waiting for an interface to appear ...
WHY are there 'stick out tongue' smilies embedded into my error log???
Last edited by AndeAnderson; 12-28-2009 at 04:44 PM.
Reason: Had to search for error logs as root.
": p" without the space is the stick out tongue so when you copy past that, it becomes stick out tongue. As far as the user thing goes, you can google to set up root logins. That is a debian thing, so distro's like Ubuntu or mint would act similarly. You can use
PHP Code:
sudo su
to get a persistent root session in the terminal. If you launch a program from that session then you will be running it as root. Such as
PHP Code:
dtest@DELL:~$ sudo su root@DELL:/home/dtest# dolphin
So now you have access to the file browser as root and can of course navigate where ever you feel like.
From the logs it appears your network is 192.168.11.0/24 vs 192.168.0/24 in your smb.conf.
Following the Samba documentation I set those to the default of 'blank' settings which will allow full access. I can now access the windows systems from the Linux system.
However, nmbd still will not run. From what I have read, nmbd has to be running for my Windows systems to access the Linux shares.
So, does anyone have any clues why nmbd will not run?
I have set-up the Linux IP in all of my hosts files, to bypass any name resolution problems. And, I can ping the Linux system from all of the other machines.
You have the interface set to a subnet rather than the IP address of your machine(and I think from above the wrong subnet at that) In my smb.conf I have this line commented out and the preconfigured description states that it is only for multiple interfaces (eth0, eth1, etc) so if you are using a single NIC then I don't think you even need it.
[2009/12/30 10:32:25, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/30 11:04:17, 0] nmbd/nmbd.c:terminate(68)
Got SIGTERM: going down...
[2009/12/30 11:04:17, 0] libsmb/nmblib.c:send_udp(839)
Packet send failed to 192.168.11.255(138) ERRNO=Invalid argument
[2009/12/30 11:05:02, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/30 11:05:02, 0] nmbd/nmbd.cpen_sockets(683)
[2009/12/30 15:55:04, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
[2009/12/30 15:55:17, 0] nmbd/nmbd.c:terminate(68)
Got SIGTERM: going down...
[2009/12/30 15:55:17, 0] nmbd/nmbd.c:main(849)
nmbd version 3.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2008
If I read this right, the last entry says nmbd started. Yet, it is not running.
You have the interface set to a subnet rather than the IP address of your machine(and I think from above the wrong subnet at that) In my smb.conf I have this line commented out and the preconfigured description states that it is only for multiple interfaces (eth0, eth1, etc) so if you are using a single NIC then I don't think you even need it.
Those settings were accomplished by Debian when I was installing from the Net-Install. I thought Debian would have set them correctly.
As advised in the smb.conf documentation, those have already been reset to:
hosts allow =
interfaces =
That was how I was able to gain one-way access from the Linux to the Windows. But, I still can not access the Linux Shares from the Windows systems.
Last edited by AndeAnderson; 12-31-2009 at 07:52 AM.
Reason: Mistakes in typing
This indicates that nmbd is running. The same thing can be used to see if smbd is running also. Try the following command:
smbclient -L Samba24 (Just press enter when the password prompt is displayed)
You should see some output that shows the browseable shares. If that works then you should be able to see it on your windows PCs network places. BTW what did you put in the hosts file and did you add any samba users? Also, if you are running a firewall make sure the SMB ports are open.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.