Suse 10 - Samba - Windows/Linux can't browse local network
 

I'm having an extermely tough time working with Samba on my new Suse machine.

When I try to access the network using smb:/, I usually get an error.
I've tried turning the firewall off, and now I don't get the error, but none of my other computers come up.

One my windows computer, when the linux machine is on, I can't browse other Workgroup computers... When the linux computer is off, I can browse no problem.

The error reads "Workgroup is not accessible. You might not have permission to use this network resource. COotact the administrator of this server to find out if you have access permissions. The network path was not found"... note, that's accessing the list of other Workgroup computers, not trying to access my linux machine directly...

On Windows, if I try \\linux-machine-ip-address\ I get the error "Windows cannot find [...]"

I realize this isn't a Windows support forum, but it's obviously a configuration error on my Suse machine... hopefully someone can help me track it down...


Thanks!

Make sure that you have lisad and lwresd running.

Also: if you can browse between Windows boxes when the Linux box is down, but cannot when the Linux box is up, check for conflicts in the following:

* Nbios/Netbios name
* Hostname
* IP Address (if IP is conflicting NO IP networking would work from the conflicting machines. Many IP stacks refuse to load in the event of such a collision to prevent breaking the network)

I can verify that the Netbios name, hostname, and IP address are unique.

I tried running /etc/rc.d/smb stop and then start to restart samba...

Here's the output of tail /var/samba/log.smbd

Does this help at all?

I'm running into an issue with network browsing myself now (just reinstalled Linux over the weekend). I configured everything as usual, went into KDE control center and configured lisa, and while my PC will browse the network there is a long delay. :(

It worked SO much better in SuSE 9.1 and SuSE 9.3

I still haven't got mine to work.
What's 'lisa'?

http://docs.kde.org/stable/en/kdenetwork/lisa/

It's a network browser daemon.

Is there anything else I can provide to help with my Samba client issues?

I'm pretty sure this worked once, and now for some reason doesn't work anymore.
I've checked the firewall and even turned it off...

Similarly, and more importantly, my Samba server doesn't work either.

I've tracked the answer do to a thread in a different forum.
I hope linking it here isn't against forum policy as it directly relates to this issue where the samba pid exists"

It seems that the latest patch from YaST has spoiled Samba on 64-bit installations.

I don't know how to rollback patches, can anybody help me out with that?
Or more ideally, direct me to how to solve the problem at hand...

Thanks!

I have horrendous problems since upgrading from SuSe 9.3 to 10, it would appear, (from other sites and forums) that a lot of people are having similar problems, Samba does not work, swat does not work, sound and sound players are iffy, there are graffics problems, video does not work. Novel are conspicuous by their silence on these issues, but if you call their help desk (at exorbitant telephone call rates they will solve all your problems (bit like Bill Gates strategy). It would appear they shipped SuSe 10 with "known broken bits". Redhat and ubuntu both work fine.

add sax2 to the list, suthron

What I have learned about SuSE: skip the even-number revisions. 9.0 sucked, 9.1 was awesome. 9.2 sucked, 9.3 was awesome. SuSE 10.0 sucks, but 10.1 looks like it's shaping up pretty well.

Lan is HORROR on SuSE10, I am trying to get it working almost for 2 month's now, I tried smb4k, which looked very promising, but , it seems to be the firewall that is weird.
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....

This is what I get in my log file...
 

I am running SuSE 10 on an AMD Athlon64 as well and get this when I have manually deleted the pid lock file and /etc/init.d/smb start

-------------------------------------------------

[2005/12/30 12:37:13, 0] smbd/server.c:main(806)
smbd version 3.0.20b-3.1-SUSE started.
Copyright Andrew Tridgell and the Samba Team 1992-2005
[2005/12/30 12:37:13, 1] param/loadparm.c:lp_do_parameter(3405)
WARNING: The "printer admin" option is deprecated
[2005/12/30 12:37:13, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4152
[2005/12/30 12:37:13, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4152
[2005/12/30 12:37:13, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4152
[2005/12/30 12:37:13, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_free_read bad magic 0x42424242 at offset=4264
[2005/12/30 12:37:13, 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/30 12:37:13, 0] registry/reg_db.c:init_registry_db(223)
init_registry: Failed to initiailize data in registry!
[2005/12/30 12:37:13, 0] registry/reg_frontend.c:init_registry(57)
init_registry: failed to initialize the registry tdb!
[2005/12/30 12:37:28, 0] smbd/server.c:main(806)
smbd version 3.0.20b-3.1-SUSE started.
Copyright Andrew Tridgell and the Samba Team 1992-2005
[2005/12/30 12:37:28, 1] param/loadparm.c:lp_do_parameter(3405)
WARNING: The "printer admin" option is deprecated
[2005/12/30 12:37:28, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4152
[2005/12/30 12:37:28, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4152
[2005/12/30 12:37:28, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_read bad magic 0x42424242 at offset=4152
[2005/12/30 12:37:28, 0] tdb/tdbutil.c:tdb_log(767)
tdb(/var/lib/samba/registry.tdb): rec_free_read bad magic 0x42424242 at offset=4264
[2005/12/30 12:37:28, 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/30 12:37:28, 0] registry/reg_db.c:init_registry_db(223)
init_registry: Failed to initiailize data in registry!
[2005/12/30 12:37:28, 0] registry/reg_frontend.c:init_registry(57)
init_registry: failed to initialize the registry tdb!

I agree. Novell should never have shipped SuSE 10 as is, and they do not seem particularly interested in fixing the fooking bug.

SaX2 is every bit as broken too, BTW.

Novell will not any more...They left SuSE....to be on her own...

Where are you getting that idea from?
www.suse.com redirects to http://www.novell.com/linux/suse/
they're still selling:

http://www.novell.com/products/linuxenterpriseserver/
http://www.novell.com/products/suselinux/
http://www.novell.com/products/linuxpointofservice/

OpenSuSE is not an abandoning of SuSE Linux. They've alienated some of the SuSE founders (unfortunately who is/was arguably their greatest asset, the kernel maintainer) who left but that does not mean that SuSE is being discontinued. There may be some parallels between SuSE and Fedora but those similarities are superficial at most. Was there a press release stating that they are abandoning the retail versions of SuSE Linux? If so, I'll be switching to kubuntu and Mandriva.