Yes, still no luck. I even tried to take a spare good old Linksys WRT54GL with fresh NVRAM erase and settings as default as they could be and connected my Windows computers to that, but OMV was still not showing up. But all other Windows 7 computers on the network are being detected and I have like 4 or 5 of them. So we are back to Samba in my opinion.
Panic or segfault in Samba
-
- OMV 1.0
- Nibb31
-
-
Put the windows client in the same workgroup as samba. Sometimes that helps.
-
Workgroup is the same for all computers and Samba. Maybe let's just wait and see until next releases. Maybe some bug is discovered. As far as I know I am not the only one experiencing this issue. The shares work like a charm it is just that OMV is not being detected anymore by Windows computers in the Network section. As far as I remember it did not happen when I was enabling the WINS server and specifying the OMV address as a WINS server to DHCP clients in my router, but a few weeks after that and some updates to OMV and other updates. Maybe there was even a Samba update in between.
-
There was an update on Samba on Feb 19. CVE-2015-0240: Unauthenticated code execution attack on smbd file
servicesthat's smbd not nmbd
Most of the time this problem either i solve it with workgroup or bringing down the firewall and AV in the windows clients. Nothing to important since i use more access by net drive than discovery.
-
I agree that is more of an inconvenience for clients who rely on discovery rather than a serious bug
-
Just letting you know guys that Samba started to advertise itself again. Then it disappeared again, then it reappeared again. I am not able to reproduce this behavior.
-
Neither am I. But I'm affected too.
Greetings
David -
Anyways, if I will discover that I can reproduce this behavior, then I will let you know
-
is it not a fight about which device has to become MasterBrowser?
try to see with the command smbtree what has been broadcasted.
I can remember that when devices do battle about becoming MasterBrowser that in some situations Windows cannot detect a device automatically.
Long time ago I had a printserver causing devices not being detected correctly when it was turned on. In the end rebooting various devices in different order gave the solution. -
is it not a fight about which device has to become MasterBrowser?
try to see with the command smbtree what has been broadcasted.
I can remember that when devices do battle about becoming MasterBrowser that in some situations Windows cannot detect a device automatically.
Long time ago I had a printserver causing devices not being detected correctly when it was turned on. In the end rebooting various devices in different order gave the solution.Will give it a try. I did notice that everything was working again once my local network had been down for some time. I was reconfiguring my router and as a result many devices where offline for longer time and then I added them back one by one and discovery was working properly again.
-
Will give it a try. I did notice that everything was working again once my local network had been down for some time. I was reconfiguring my router and as a result many devices where offline for longer time and then I added them back one by one and discovery was working properly again.
What you describe seems indeed a battle between devices to become masterbrowser. And in some circumstances it can take up to 15 / 20 minutes before there is again a 'battle / negotiation'. But it will still not give a solution or answer why in some circumstances another masterbrowser is not broadcasting a certain device.
-
Hi,
even the thread is very old, I want to bring it back again.
After a reboot of my server I got informed about a "Panic or segfault in Samba" by omv with the following email:
Code
Alles anzeigen[omv4.local] Panic or segfault in Samba ----------------------------------------------- The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1962 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. However, gdb was not found on your system, so the error could not be debugged. Please install the gdb package so that debugging information is available the next time such a problem occurs.
So, as advised in the email I Installed the package "gdb". Now the error is gone. Did some reboots and the message didn't come up again. My SMART data is free of errors.Any other suggestion?
Let's wait and see what happens.
Regards Hoppel
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!