nmb service is dead

[glennzo]

Thanks bbfuller. My bad

[beaker_]

OK, both F12 x86_64 and F12 i686 like your smb.conf. Which isn't much comfort since your at F11. I believe you're under AD and your domain or password server is at 192.168.1.1 which is something I can't duplicate here.

Looking at the date from authconfig and the F9 reference from smartmontools, was this server an upgrade or a fresh install? Strange and seldom wonderful things happen post upgrade.

Right now I can't decide whether to tell you to erase and reinstall all the samba packages, grab a live F12 image (mine starts/stops ok here) and give it a whirl or look into /var/log/samba/log.smbd and /var/log/samba/log.nmbd for a hint.


Late Edit: I tried xinetd only on i686. For giggles, remove you samba file from xinetd.d, restart xinetd, and then try and restart smb & nmb.

[ttx336]

Originally Posted by glennzo

May be a dumb question but have you actually installed samba? It doesn't seem to be fully installed after the initial OS installation.

su -c 'yum install samba'

That should bring in samba, samba-client and samba-common. Apologies if I've missed something in the thread.

Hi glennzo,

I installed it via the Add/Remove Software in the GUI but I will certainly give it a shot in the terminal and see what it says.

---------- Post added at 01:21 PM CST ---------- Previous post was at 01:01 PM CST ----------

Originally Posted by beaker_

OK, both F12 x86_64 and F12 i686 like your smb.conf. Which isn't much comfort since your at F11. I believe you're under AD and your domain or password server is at 192.168.1.1 which is something I can't duplicate here.

Looking at the date from authconfig and the F9 reference from smartmontools, was this server an upgrade or a fresh install? Strange and seldom wonderful things happen post upgrade.

Right now I can't decide whether to tell you to erase and reinstall all the samba packages, grab a live F12 image (mine starts/stops ok here) and give it a whirl or look into /var/log/samba/log.smbd and /var/log/samba/log.nmbd for a hint.


Late Edit: I tried xinetd only on i686. For giggles, remove you samba file from xinetd.d, restart xinetd, and then try and restart smb & nmb.

Not sure I know how to remove the samba file from xinetd.d but I will see if I can figure it out. I am still not too good at searching in Fedora... hints?

Yes, this is an upgrade from F9, which I normally don't do just for this reason. I am certainly not opposed to doing a fresh install, if that looks like the easiest option, just say the word. I sometimes, as in this case, will try to avoid that so that I learn a little bit more.

The only thing I need to be SURE of is that I don't choose the wrong option for the grub install and overwrite my windows boot config, I am using EasyBCD and booting from the windows partitions. I get confused on which one is which since I don't do a lot of installs.

Also, this one is not a server, my server is running GREAT!! I am so glad to report. It hums along without a hitch, rsync runs nightly via cron and all is well there! This machine is a laptop, it is kind of my "lab" computer, I have Vista, W7 and F11 on it, I may even drop XP on it too. I use it as my daily driver, though, so I have to be a little careful with it.

One more thing, can I run two versions of Fedora at the same time? I REALLY liked F9 and am pretty bummed that I replaced it with F11, so much so that if I have many more issues with F11 I may drop back to it. Wireless, Bluetooth, Samba, all was running good, I actually thought when I upgraded that I would still be able to run F9 until I updated it a few times, kind of like when we do when we have updates for our current version. I was pretty bummed when I saw that was not the case but I guess too much changes in the files to allow that.

I did get Google Chrome on it all by myself!! Wonders never cease... can't get Flash working on it yet, though, works in Firefox, I think I need to do another step to Chrome to add it as a plugin, seem to remember that from Firefox.

Thanks guys, glad to have the pros helping me!

---------- Post added at 01:53 PM CST ---------- Previous post was at 01:21 PM CST ----------

Originally Posted by beaker_

For giggles, remove you samba file from xinetd.d, restart xinetd, and then try and restart smb & nmb.

I switched to the xinetd.d directory but there is no samba file in there...

chargen-dgram
chargen-stream
daytime-dgram
daytime-stream
dir
discard-dgram
discard-stream
echo-dgram
echo-stream
rsync
swat
tcpmux-server
time-dgram
time-stream

- Gary

[bbfuller]

Hello Gary,

There's nothing referencing samba in mine either, it's working quite happily though.

If that were my installation, I'd be tempted to do a new install, upgrades are notorious for problems.

I can put my hands on six F12 installations where samba is working perfectly. The only caveat is that they are all 32 bit. Though I think if there were a problem with 64 bit samba it would have been all over the forum by now.

Bernard

[ttx336]

Originally Posted by glennzo

May be a dumb question but have you actually installed samba? It doesn't seem to be fully installed after the initial OS installation.

su -c 'yum install samba'

That should bring in samba, samba-client and samba-common. Apologies if I've missed something in the thread.

Ok, I ran the command, here is the result...

[root@hplaptop xinetd.d]# su -c 'yum install samba'
Loaded plugins: refresh-packagekit
adobe-linux-i386                                         |  951 B     00:00     
google-chrome                                            |  951 B     00:00     
livna                                                    | 2.4 kB     00:00     
updates/metalink                                         |  12 kB     00:00     
updates                                                  | 4.4 kB     00:00     
updates/primary_db                                       | 6.3 MB     00:09     
Setting up Install Process
Package samba-3.4.2-0.42.fc11.x86_64 already installed and latest version
Nothing to do
[root@hplaptop xinetd.d]#

... so it was already there.

btw, when I boot, I see winbind fail but nmb reports that is starts ok, smb fails immediately after that.

%G/etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (en_US.UTF-8): No such file or directory
/etc/profile.d/lang.sh: line 20: warning: setlocale: LC_COLLATE: cannot change locale (en_US.UTF-8): No such file or directory
/etc/profile.d/lang.sh: line 23: warning: setlocale: LC_MESSAGES: cannot change locale (en_US.UTF-8): No such file or directory
/etc/profile.d/lang.sh: line 26: warning: setlocale: LC_NUMERIC: cannot change locale (en_US.UTF-8): No such file or directory
/etc/profile.d/lang.sh: line 29: warning: setlocale: LC_TIME: cannot change locale (en_US.UTF-8): No such file or directory
		Welcome to Fedora 
		Press 'I' to enter interactive startup.
Starting udev: %G[  OK  ]

Setting hostname hplaptop.BRITTON:  [  OK  ]

Setting up Logical Volume Management: [  OK  ]

Checking filesystems
/: clean, 7216/67824 files, 83472/271089 blocks
/backup: clean, 11/72000 files, 38938/263056 blocks
/usr: clean, 130035/589824 files, 872733/2351506 blocks
/tmp: clean, 99/169344 files, 28089/676730 blocks
/opt: clean, 241/67824 files, 25599/271089 blocks
/var: clean, 1718/270912 files, 407990/1082371 blocks
/home: clean, 2038/130560 files, 86841/524112 blocks
/usr/local: clean, 46/270912 files, 51974/1082371 blocks
/boot: clean, 37/67824 files, 14987/271089 blocks
[  OK  ]

Remounting root filesystem in read-write mode:  [  OK  ]

Mounting local filesystems:  [  OK  ]

Enabling local filesystem quotas:  [  OK  ]

Enabling /etc/fstab swaps:  [  OK  ]

Entering non-interactive startup
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Enabling ondemand cpu frequency scaling: [  OK  ]

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Bringing up loopback interface:  [  OK  ]

Bringing up interface Auto_colorado:  Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.

Determining IP information for ... done.
cat: /sys/class/net//ifindex: No such file or directory
/etc/sysconfig/network-scripts/ifup-eth: line 300: 1000 + : syntax error: operand expected (error token is "+ ")
Missing config file ifcfg-ifcfg-Auto_colorado.
[  OK  ]

Starting auditd: [  OK  ]

Starting portreserve: [  OK  ]

Starting restorecond: [  OK  ]

Starting system logger: [  OK  ]

Starting irqbalance: [  OK  ]

Starting rpcbind: [  OK  ]

Starting NFS statd: [  OK  ]

Starting RPC idmapd: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
[  OK  ]

Starting system message bus: [  OK  ]

Starting cups: [  OK  ]

Mounting other filesystems:  [  OK  ]

Starting acpi daemon: [  OK  ]

Starting HAL daemon: [  OK  ]

Starting PC/SC smart card daemon (pcscd): [  OK  ]

Setting network parameters... [  OK  ]

Starting NetworkManager daemon: [  OK  ]

Starting Winbind services: [FAILED]

Starting Bluetooth services:[  OK  ]

Starting sshd: [  OK  ]

Starting xinetd: [  OK  ]

WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Starting NFS services:  [  OK  ]

Starting NFS quotas: [  OK  ]

Starting NFS daemon: [  OK  ]

Starting NFS mountd: [  OK  ]

Starting sendmail: [  OK  ]

Starting sm-client: [  OK  ]

Starting crond: [  OK  ]
[  OK  ]

Starting NMB services: [  OK  ]

Starting SMB services: [FAILED]

Starting atd: [  OK  ]
[  OK  ]

Starting Avahi daemon... [  OK  ]

-Gary

---------- Post added at 02:16 PM CST ---------- Previous post was at 02:11 PM CST ----------

Originally Posted by bbfuller

Hello Gary,

There's nothing referencing samba in mine either, it's working quite happily though.

If that were my installation, I'd be tempted to do a new install, upgrades are notorious for problems.

I can put my hands on six F12 installations where samba is working perfectly. The only caveat is that they are all 32 bit. Though I think if there were a problem with 64 bit samba it would have been all over the forum by now.

Bernard

Hi Bernard,

I think I'll just do that... a fresh install sounds positively refreshing!

Any advice on getting the grub install correct? I remember that there are a few options... one is leave as is, one is replace... I can't remember them right now. I want to end with being able to boot up with the existing windows boot.bcd but of course there has to be a grub.conf file built too.

Gary

[bbfuller]

Hello Gary,

Well, I have access to several machines dual boot or triple boot. This laptop has Windows 7, Vista and Fedora 12 on it.

It was installed in the order of Vista, then Windows 7, then Fedora 12. Windows 7 and Vista share the Windows boot loader. When I installed F12 I just told it to put Grub in the Master Boot Record.

That way, I get the usual Fedora Menu offering me the range of installed kernels and Windows. If I select Windows then I go to the windows boot menu and that gives me a choice of 7 or Vista.

Bernard

[beaker_]

+1 for a clean install and I think your other problems all share a common denominator, upgrade gone south. F12 wouldn't be a bad way to go, besides if you're gonna ride a roller coaster may as well be in the front seat

For xinitd.d; either you would have created the file yourself, or it'd be in 'swat.' Basically it's the one with a reference to 'server = /usr/sbin/smbd.' But, honestly, I think there'll be less hair pulling going with a fresh install.

[ttx336]

Originally Posted by beaker_

+1 for a clean install and I think your other problems all share a common denominator, upgrade gone south. F12 wouldn't be a bad way to go, besides if you're gonna ride a roller coaster may as well be in the front seat

For xinitd.d; either you would have created the file yourself, or it'd be in 'swat.' Basically it's the one with a reference to 'server = /usr/sbin/smbd.' But, honestly, I think there'll be less hair pulling going with a fresh install.

I did a fresh install and *sigh* chose the wrong grub install option so I have spent the last few hours fixing that.

xinetd, nmb, smb and winbind are all running but I still can't see my other computers on the network... I shouldn't really need samba for that I don't think but perhaps I do. I did notice that Samba does not appear in the "Administration" list, that seems wrong to me but I see smb service running. I edited the smb.conf in terminal to have the right WORKGROUP but it didn't fix it.

Any ideas?

[bbfuller]

Hello ttx336

If you have installed F12 then there may well be differences in the setup tp F9.

For starters, Samba needs to be allowed through the firewall where it is blocked by default.

SELinux also prevents samba shares on the local machine until allowed.

Assuming you have an identical Linux and Samba user on your machine that is identical with the owner of a share on your server, what does:

smbclient -L <server ip address>

return.

I presume that you installed from DVD and elected to add all the samba parts then? Or have you added them since?

[ttx336]

Originally Posted by bbfuller

Hello ttx336

If you have installed F12 then there may well be differences in the setup tp F9.

For starters, Samba needs to be allowed through the firewall where it is blocked by default.

SELinux also prevents samba shares on the local machine until allowed.

Assuming you have an identical Linux and Samba user on your machine that is identical with the owner of a share on your server, what does:

smbclient -L <server ip address>

return.

I presume that you installed from DVD and elected to add all the samba parts then? Or have you added them since?

Good morning Bernard... actually good afternoon for you...



I woke up this morning to it all working fine, I had set the firewall last night, don't remember if I rebooted before I went to bed to check it or not but when i booted into Fedora this morning, it is working fine.

I did install from DVD and allowed everything to install and I am still using F11 for now. The only thing I still need to test and possibly resolve is the Sleep Mode. It was going to sleep but not waking up properly in the last install.

Gary

[beaker_]

Just adding. It sounds like you have samaba running, your shares are visible, and everything tikety-boo. But you simply can't browse the network from F12. Sound about correct?

Yum in your friend. Yumex (gui) is good but don't let it handicap you. For example; samba appears on you menu when 'system-config-samba' is installed.

At the terminal:
su
yum install system-config-samba

If I could remember only part of the name then I could:

yum list system-config-*

Or
yum list *samba*

Caveat. system-config-samba would fail when launched from the menu but will work when lauched from the terminal as root (su). I think it was fixed with updates so besure to update the system.

su
yum update

Selinux does tighten the screws and if your network is trustworthy, then toss it into permissive mode while you troubleshoot. A quick google for redhat and selinux will kickup good instructions.

Ex.,
Toss into permissive & enforcing mode:
su
setenforce 0. (Permissive)

setenforce 1. (Enforcing)

There is a gui (system-config-selinux) but I forget which package provides it. I can find out by jumping to the terminal and:

su
yum provides */system-config-selinux

Selinux troubleshooter should already be installed and will help identify issues. Just don't follow its advise blindly.

system-config-firewall is a decent tool. It's not like slinging iptables commands but you can quickly open services.

Late edit: I see your edit. You're miles ahead then. Not sure about sleeping though, maybe a bios bug and easiest to just to disable it. But, again, I'm no authority.

[ttx336]

Originally Posted by beaker_

Late edit: I see your edit. You're miles ahead then. Not sure about sleeping though, maybe a bios bug and easiest to just to disable it. But, again, I'm no authority.

I know that the sleep mode in windows is handled by the nVidia video driver so I am going to give this a shot http://forums.fedoraforum.org/showthread.php?t=204752 and see if I can pull off installing and testing the video driver. I really need to do that anyway as I cannot currently control the brightness of screen. If anyone has any tips on this I'd appreciate it, I have only installed the wireless driver following the instructions posted by bbfuller to a user called majdi (something like that).

Thanks, Gary

[bbfuller]

Hello Gary,

This is the howto I follow for nVidia drivers:

http://forums.fedoraforum.org/showth...ghlight=nvidia

Bernard