[SOLVED] nmb failed

[L3l00]

I get a call today no one can access the shared folders. I check the status of smb (running) and nmb which said (Failed). I tried useing smbclient and could not get a response! I typed in net usershare --long and got a net user share not working...

---------- Post added at 09:20 AM ---------- Previous post was at 09:06 AM ----------

so fare I have done:

sudo yum update
reboot

when I rebooted and it was about to click to the login welcome screen, I get this message:

Could not create ICE listening socket: Cannot establish any listening sockets
"Log out"

I logged in then tried:

smbclient //QServer/QF -l 127.0.0.1 -U jn


[2012/08/17 09:19:24,  0] ../lib/util/debug.c:571(reopen_logs_internal)
  Unable to open new log file '127.0.0.1/log.smbclient': No such file or directory
Connection to QServer failed (Error NT_STATUS_UNSUCCESSFUL)

service nmb status
Redirecting to /bin/systemctl status  nmb.service
nmb.service - Samba NMB Daemon
	  Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
	  Active: failed (Result: exit-code) since Fri, 17 Aug 2012 09:12:37 -0600; 8min ago
	 Process: 823 ExecStart=/usr/sbin/nmbd $NMBDOPTIONS (code=exited, status=0/SUCCESS)
	Main PID: 846 (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/nmb.service

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

---------- Post added at 09:37 AM ---------- Previous post was at 09:20 AM ----------

?????????????????????

It's working now?

Problem I don't know why our how, plus how do I resolve the smb log file issue so I can actually know more info on the crashes if it crashes again?

Last commands I sent before it started working again:

smbclient //QServer/QF -N
Connection to QServer failed (Error NT_STATUS_UNSUCCESSFUL)

smbclient -L 192.168.0.3 -U jn
Enter jn's password: 
session setup failed: NT_STATUS_LOGON_FAILURE

smbclient -L 192.168.0.3 -U jn
Enter jn's password: 
Domain=[Q] OS=[Unix] Server=[Samba 3.6.6-92.fc17]     ?????????????? Now it's working again!?

[beaker_]

Systemd & NetworkManager suck. Basically your nic's not up in time for smb & nmb. You can reproduce the result with a restart.

su
systemctl enable NetworkManager-wait-online.service
exit

Reboot and see if that cures it.

[L3l00]

Well that did seemed to have solved the nmb failed issue. Just it seems to knock out having the server access to the share files? I tried smbclient got these results:

[2012/08/17 13:06:37,  0] ../lib/util/debug.c:571(reopen_logs_internal)
  Unable to open new log file '192.168.0.1/log.smbclient': Permission denied
session setup failed: NT_STATUS_LOGON_FAILURE

[beaker_]

Originally Posted by L3l00

I get a call today no one can access the shared folders. I check the status of smb (running) and nmb which said (Failed). I tried useing smbclient and could not get a response! I typed in net usershare --long and got a net user share not working...

Ok... I missed that one. Here's what you need to hear: Fedora is too freakn manic and isn't worth risking a friday phone call, get CentOS or SL, you'll be more thankful in the long run.

Just backup and copy your configs over with a memory stick.

system-config-samba can be rebuilt for CentOS painlessly.

[beaker_]

http://www.centos.org/modules/tinyco...ndex.php?id=30

[L3l00]

I strongly agree with your statement and yes I do plan on making this Server CentOS. CentOS 6 to be exact. Just this probably wont be possible until next friday. I need to see if I my boss's would let me come in after hours, they are a bit on the paranoid side but sometimes it just needs to get done. I would say first thing monday but have some android tablet administration work for the city for the next three weeks! Grrrr Not enough time in the day.

Well the important thing is that everyone is able to access the files without any issues... for now...

[beaker_]

They have access, great, then everyone move slowly and noone will get hurt. Especially on Friday.


Late Edit: at 23 you might need to be told this: the sh1t pile will never go away, go home.

[L3l00]

haha ya. I may have some time now actually. Have the live disc of CentOS 6 if I move quick I might get everything running in an hour..... or two it's an old computer. But I would have to get it to work on first try no matter what

---------- Post added at 02:33 PM ---------- Previous post was at 02:02 PM ----------

not sure if this is part of the problem but net user share gives me a disabled.

[beaker_]

I haven't a clue. I thought net user info, add & delete were the only options. Share? And I'm unsure how to duplicate your errors. I've attached system-config-samba and -samba-doc rebuilt for el6 to make your life easier.

You really want to skim through Samba3-by-example. You already have it, it's part of samba-doc, or a quick google search.

[L3l00]

its groovy, switched the Server to CentOS 6. It started because of samba-swat & system-config-samba. I'm sticking to good ol' fashioned terminal smb commands. SOOOOO much simpler. Managed to switch everything and get samba to work within two hours which I'm impressed by because the only fault on CentOS was it wasn't allowing me to mount the backup ntfs drive. Solved it


When it comes to Samba and Fedora I'm just keeping to household use only. It never gives me problems on personal use.

[L3l00]

Figured I should put this, but kept forgetting to mark as SOLVED.

 session setup failed: NT_STATUS_LOGON_FAILURE

Is a permissions problem, normally I would place shared folders in some users desktop on the server. Turns out that by doing this only that user can access it no matter what setting you put them under even if you use a Recursive +X to the folders absolute location.

I have found it much easier to make the shared files in the home folder and of course having proper permissions set in place there. Typically 755. This gets rid of the following error completely, for some reason Shared folders on Desktops turns Linux into a disobedient brat.


Server is now CentOS 6 and have had ZERO problems with anything other then getting redmine to work. Samba now functions like a gem. Moved away from system-config-samba completely and stuck to smb command lines only which I actually prefer anyways.