Suse 10 - Samba - Windows/Linux can't browse local network
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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.
Well, to be frank, there has been a lot of fuss around it.
There was an article, whetter it is to be trusted is one thing. ( I looked trough my old mail, it was in the KDE-maillinglist, but I could not find it, oldest mail 21-11-05, but it was before that date....ahh! I remember i reinstalled the twentiesth!)
On the other hand, I think it is impossible for SuSE NOT to continue, as they are the biggest thread for windows.
Novell didn't want to continue, questions rose about bribery by M$, bigshots gone, Novell accused of sailing with all winds...
This is not realy improving for 'a good working athmosphere', that is why, imho, things are a little 'slow', these days.
But it will be allright, I guess...
There also are the Christmas and New-Year....
I can enter a thousand passwords, they get stored, but none of them is able to open the dirs!
All the dirs are visible, you only canot open them.
It is a drag!
I think it is a severe bug....
I'm glad you brought this up. I'm having the same problem. I can see the dirs on my two linux machines. I can even connect fine using SMB on my girfriend's PowerBook, and when I boot to XP on one of the linux boxes I can connect to the other.
Is this definitely a bug, or more of a default configuration error? I've searched the Novell site but it really sux. I can't find anything. If anyone has ideas, please help. Thanks!
I have been updating to the latest samba yesterday, and now I am able to access one directory from all computers in the network, without having to use a password. (In the networkbrowser is in the right-mouse menu an option to share dirs now.)
This directory is on SuSE10.0.
SuSE is not able to get access to the other pc's at this moment, but there is some progress now.
pretty interesting: I don't have any problem either for SuSE to access XP Pro shares, or for XP pro to access SuSE shares (SuSE 10.0 64-bit), if there i a bug, then it does not affect all configurations (mine is LAN with router)
[2005/12/04 19:37:48, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4212
[2005/12/04 19:37:48, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_free_read bad magic 0x42424242 at offset=4324
[2005/12/04 19:37:48, 0] registry/reg_db.c:regdb_store_keys(344)
regdb_store_keys: Failed to store new record for key [HKLM\SYSTEM\CurrentControlSet/Services}
[2005/12/04 19:37:48, 0] registry/reg_db.c:init_registry_db(223)
init_registry: Failed to initiailize data in registry!
[2005/12/04 19:37:48, 0] registry/reg_frontend.c:init_registry(57)
init_registry: failed to initialize the registry tdb!
Does this help at all?
Yes. It looks like you ran into a corrupt TDB file. Please call the following commands:
Then your smbd should start again. And your old registry.tdb was saved as registry.tdb.off.
Please submit a bugreport to bugzilla.Novell.com next time you run in such trouble. And please inform us about the file system used for /var/lib/samba/
Lars
Last edited by Lars Müller; 01-25-2006 at 06:57 AM.
I run two samba servers via SUSE 10 and configured by SWAT. My brother updated his SUSE 10 and is now stuck with samba not running. Novell is not interested helping at all. One SUSE user told me that updating the kernel causes the samba problems but nobody yet has the asnwer...
I'm very disapointed with Novell, but love the SUSE...
Yes this is all very tragic.
There is no working solution, some people seem to have no problem at all.
But I have never been able to get a good working LAN for about 5 months now.
There have been some minor improvements, like SuSE is visible from Windows Boxes, and things can be copied from there, but nothing can be copied to it. And no windows box at all is visible from SuSE10.
Lisa should be the solution, but there is no proper way to get it working at start-up.
We hope that, if enough people complain, something is getting done about it.
After many weeks of trying to figure out what cause me not to be able to browse, I finally found that the process nmbd does not start consistently everytime you reboot or change to smb.conf file. This bug originate from Yast2 within SUSE 10.0.
To solve this problem I added the folllowing line to this file /etc/init.d/boot.local
###Fix smb browsing bug #####################
/etc/init.d/nmb restart
############################################
Then reboot the pc.
Now with the correct smb.conf file I'm able to browse all smb machine in the network.
Note: to test your smb.conf file one can run
testparm
To test if samba is running correctly on the suse box one can type the command as follow:
ok
where will i prepare that problem?
if you can help ,send me by mail with commands to resolve this problem.
my suse is error smb ,so i can't call other computers.
And i want to share them.
help me please!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.