Fedora Networking :: Samba NMB - Dead After A Reboot
Feb 8, 2009
I've got a problem with samba and the nmb service. My system boots in Gnome
Ive set up Samba and it works ok, untill I reboot, then I have to go into services and restart Nmb service. the services bit says its dead after a reboot, its running on run levels 2345 I had a few hicups setting it up took me a couple of days to figure out the fire wall and SElinus were blocking things, so I ticked all the samba things - and it works a whole lot better.
I have to admit its a whole lot more polished than last time I tried linux - Red Hat 5. I like the Yum installer it takes a lot of guess work out for us novices, one thing I would like is to be able to edit and open things as root in Gnome or just log into it as root so that you can set things up, but I'll save that question for another day.
I have been running Fedora 12 on my HP Proliant DL140 Server for about 6 months now without any issues, yesterday I ran yum update and rebooted afterwards but the server now wont boot
running Ubuntu 10.10, generally with no probs. After the upgrade to 10.10, and several updates, I still have a problem. Namely when ever I re-boot, which now more often than I'd like, due to a machine failure. It starts, but accross the network can't "see" tux, pop to root term, and
running a server semi-headless (desktop installed, but usually I connect via ssh/freenx) on my network.after rebooting the box, the samba service will not respond to clients, until I login over nx, and restart samba with 'sudo service smbd restart'. I have it rigged via startup applications, so the command runs on first login, but I would really prefer it come online on boot even if I'm not there to logon. I wrote a quick script to enumerate the status of the network services. here is the output right after a reboot. I ran the script from ssh, before starting a desktop session with nx.
Code: Checking status of network services Named Status:
I have FC 12 install on a Compaq nx9600 that comes with a Broadcom BMC4306 wireless card. I'm not sure what my kernel is, but I have all of the updates for FC 12.Whenever my laptop resumes from Hibernation/Suspend my Enable Wireless check box in the Network Manager is greyed out and it will not come back till I reboot the computer. Is there any one out there that can help with this problem, as I do not want to disable my Hibernation/Suspend as I tend to forget to turn the laptop off for a few days on end, and this beast sucks a lot of power so it is a drain on my power bill.
I am using samba to share some folders from a Ubuntu server (10.04) onto Windows XP. This works fine, but once in a while (once/twice a day), samba crashes and leaves a dead.letter in the folder I was accessing. Here are mode details: lsb_release -a
Code: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 10.04.1 LTS
I want to use samba for file sharing like on a Windows home network. Actually they are all Linux machines but nfs is too complicated. On my host machine I installed samba and system-config-samba. I created a new share for /home, check marked writable and visible and put access to everybody. For preferences-->server settings--> security the "authentication mode" is set to user, encrypt passwords is no, and guest account is no guest account. Under preferences-->samba users I added myself as a user with the same windows user name as my Linux user name and the same password.
My client is a virtualbox fedora (used for testing purposes but actual clients will be real computers on my home network). I entered the address smb://192.168.1.184. When asked for the user name and password I put my regular user name and password since that was what I set in samba users. However, the password dialog keeps coming up and won't let met into my own computer. If I quit it says something like access is denied. How can I get my home network back? I liked this feature when my home computers ran XP but I switched them to Fedora 12.
I am trying to have accessible computer by its network name (same as hostname) by ping and Samba client from other computers and one directory shared on my laptop. I simple, trivial wish I hope. Nothing extravagant. Something what every Windows user has out-of-the box, just to select a shared directory. However I struggle hard to do the same with linux. Sharing directory with samba is relatively easy, the issues I have is with my laptop network name. It is not recognized/propagated to the local network.
I cannot rely on static data in /etc/hosts. This is a laptop not a server, I move it between different networks. To achieve propagation of my network name (hostname) dynamically, so everyone in the local network can at least ping me, I was advised to use winbind (winbindd), that is to rely on MS NetBios technology There is no native linux technology to achieve this? shame! what about plain/dynamic DNS? why it is not my network name not propagated to my local DNS server/wifi/rooter?
To do that I was advised to do: - run winbind service (winbindd daemon) - run samba service (umm, not sure if this is necessary for network name propagation, but I also want to share data so lets keep it as an essential). - add "wins" to /etc/nsswitch.conf to "hosts" section
Well, it seems to work on my other two computers with Ubuntu and Mandriva well. But not on Suse. Well, not completely, not permanently. It magically start working when I call "Yast -> Samba Configuration". No change here (everything is already set: Domain Name, Not a DC, Netbios Hostname, Wins server support=yes, use Wins for Hostname Resolution) just hit OK. It runs SOMETHING in the background (some scripts) for a few seconds. And then abrakadabra, everything is fine, my network name is recognized, everyone can use my samba exposed directory, smb4k sees me in the Network Neighborhood.
BUT when I restart, I am "back in square one". Pinging my name does not work, smb4k does not see me, or cannot find me even by IP! Samba sharing works by using direct IP. Not all clients support connecting by IP notably not smb4k. To use Samba properly you have to sort out network name visibility fist. I would like to make "Yast -> Samba Configuration" achievements somewhat more PERMANENT.
What exactly runs when I hit OK? No new server/daemon was started. I checked PS, nothing with newer PID appeared. And samba and winbind are started on boot, they were running indeed. No change in configuration was made. I checked all changes made in /etc - but none found! Where is winbind configuration? smb.conf? Do I need to run wins server/client, another daemon?
It took me a while..But I finally got samba to be a pdc. I was able to join a test xp machine to the new domain samba made. That part worked well. In my Swat I added a samba new user and password. restarted samba etc.. Then tried to log in from the xp with the new user name as the password. As I hit enter im waiting for it to log in..the XP machine reboots. It seems to do that ever time I try. Im sure theres something not qit right in samba.conf or is it something else.
I have entered my primary and secondary DNS addresses through Network Configuration tool (system-config-network). But whenever I reboot the system it loses the DNS addresses. Following another thread, I tried changing the PEERDNS=no in ifcfg-wlan0; but it didn't work. I also put both DNS addresses in the ifcfg file, but that didn't work either.Does anyone know a solution to this?$ uname -aLinux fedoralinux 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686 i686 i386 GNU/Linux
I have installed fedora core 9 and configures the ifcfg-eth0 script as below. my problem is the network is not coming up after reboot. after the reboot if i restart the network service(service network restart) network is coming up.
I just installed Fedora 10. I entered my static network info in Network Configuration. When rebooting, the eth0 says Inactive. I've read many articles about this problem on earlier versions and tried many of the suggestion, but have not found a definite way of solving this. Is there a better way or a workaround to get this machine on the network?
I ran yum broadcom-wl and installed the driver for my card no problem. I connected to the internet just fine using my wifi thereafter.
When I shut my laptop down and booted sometime later, the wireless connection was gone and I didn't even see a wireless adapter in the networking applet.
I tried to run insmod wl and insmod wl.ko and that failed.
So... after using yum to install the broadcom drivers, how can I make that install 'permanent'; so I don't lose my wireless adapter each time I reboot?
I am having slight issue with setting up file sharing. I have a windows 7 pc and hp proliant microserver running. I have a raid array which I am using as a share for storing music, pictures etc. When I reboot the debian server I can't connect to the server from the windows 7 PC (I have mapped a network drive) until I go on to the server and restart samba with /etc/init.d/samba restart - then everything works fine. I can ping the server with both ip and hostname but the network drive does not connect - this is straight after a reboot. Is the /etc/init.d/samba restart doing something differently to when the server boots? I have read several posts relating to printer sharing issues which point to samba not starting before cups so I am wondering if samba is starting before some of the relevant networking services.
running fc10 in a vmware setup Added /etc/sysconfig/network-scripts/ifcfg-eth0:0 to create another interface and all works fine (IPADDR=10.99.56.98). Would you expect this to be available after a reboot, last reboot I had to run ifup eth0:0
I am applying a virtual interface (eth0:0) which is failing after the system reboots. It actually cause the default interface (eth0) to fail as well, I must manually go in and remove the configuration for the eth:0:0 and restart the network to get it running again. How do I successfully add a Virtual interface to Fedora 11 that will stick when rebooted.
I have installed Fedora 12 on my laptop.Installing my Broadcom BCM 4312 wireless drivers works just fine, but after a reboot I have to reinstall them. modprobe wl, modprobe wlan0 etc doesn't work either. I need to reinstall them every time I reboot.
After a recent update and reboot, I can no longer access the internet. Typing google.com in firefox or elinks results in firefox/links complaining about the server not found. However, I can find the server by using dig on the command line. I have checked the DNS configuration in resolve.conf and it is exactly the same as on a RHEL 5 system connects fine. The strange thing is, I can connect to other local machines in my domain just fine but can not connect to any other machine on the internet on this one Fedora 12 host even though I can on all other machines!
I have installed Fedora 14 about 4 days ago. I have set all the networking parameters like dns path, hostname etc. I have also ensured that I select the check-box for "Enable automatically when system starts" for eth0 interface. But weirdly, whenever I boot my system(or restart), I see that the interface eth0 is disabled. I have to manually enter as root and enable it, each time I boot/reboot my system. Why is this happening? Could you please suggest a way so that I have eth0 interface enabled always when I boot up?Also, my domainname also is not boot-persistent. What steps should I take to ensure that the domainname set once persists across reboots?
Struggled a little to get Broadcom driver working with my Dell laptop. But I am at a point where if I manually type 'modprobe b43' the wireless works. If I reboot, it doesn't work automatically and I have to 'modprobe b43' again. Any ideas what I am missing here?I can't seem to figure out how to get this to work automatically. I did check to activate device when computer starts in network manager
I am in need of some help trying to get my wireless working. I have a compaq presario f557us and my wireless card just seems to be dead. I got this laptop a few years ago and I tried installing ubuntu 7.04. The wireless part did not work out of the box (it took a lot of tinkering but finally got it working by using ndiswrapper). Later I did an OS reinstall but tried ubuntu 8.10 this time and the card was recognized with no problems, I just needed to use the proprietary drivers that ubuntu recommended. Finally I decided to give 10.04 a try. I don't know if doing an "apt-get upgrade" would've been fine but it's too late for that now; I did a fresh install and the wireless part seems dead.
I already tried installing ndiswrapper as I did before: $ ndiswrapper -l bcmwl5 : driver installed later I tried the fwcutter way: $ bcm43xx-fwcutter -i bcmwl5.sys Sorry, the input file is either wrong or not supported by fwcutter. I can't find the MD5sum b89bcf0a25aeb3b47030ac83287f894a
It looks like my laptop's wireless chipset (Broadcom) has/is dying. It won't work anymore on my Lucid install whereas it was working perfectly. The warrenty is long expired.
lspci brings up nothing about it anymore, it once did.
I booted my laptop into Win7 and it no longer finds it either. The manual slider switch on my HP Pavillion dv6000 is in the on position but the light is yellow.
It will very rarely work on Win7 now.
I can't afford a new laptop just now so it looks like I need an external wireless adaptor. I have (open busses) USB, cardbus/54, and a small firewire port. It does not pcmcia or other busses.
I need to know how to configure automate sending sms if server reboot and shutdown? Now i just set sms notification once my server it's UP by create scripts in /etc/rc.d/rc.local while booting then from server sending sms notification. SMS - using gnokii attached mobibe phone. Server - Fedora 10
Im new to fedora 11 and iptables, and i need to set the following set of instruction so VirtuaBox can accept request from lan, to the mailServer in the guest os, but after restart fedora i have to input it all again.How can it become permanent entry in iptables.
I just installed (dual-boot with Vista) Ubuntu 9.10 in my Toshiba Satellite M300. The problem is that (when using Ubuntu 9.10), its network is dead, both wireless and wired. The LEDs of the LAN port don't even blink. My wifi is not also detected. Both of my wifi device and LAN port are functional when using Vista.
I was connected to my intranet website using webmin. I was getting a message that the hostname cannot be resolved. I went into the /etc/hosts file and change the following:
127.0.0.1 localhost intranet.lab.net 192.168.50.100 intranet.lab.net # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix
I hate kernel upgrades, at least on my laptop. Every time I upgrade, I have to recompile the driver for my Linksys WUSB600N adapter or it doesn't work. Usually, this is no problem, as I have the driver saved in a .tar file and all I have to do is 'make' and 'make install' and it works. BUT... This time, I tried that, and I get this:
