Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Thanks for the advice to try LinNeighborhood. Indeed, it looks like the sort of program I need. But it doesn't seem to be working. When I run it, it identifies the shared folders on my Windows machine. But when I ask it to mount one of them, I get an error message: "Cannot resolve address."
I don't get it. If it can "see" the folder, why can't it resolve the address? What am I doing wrong? Thanks.
This is nuts. I figured out how to change smbmount to suid root, and now I get this message:
WARNING: The "printer admin" option is deprecated
libsmb based programs must *NOT* be setuid root.
1748: Connection to MAIN failed
SMB connection failed
So I must set it to setuid root, except that I'm not supposed to setuid root. This is crazy. Help!
Yeah, I tried that last night and it worked. So for now I can use this workaround.
But I still can't figure out why the software worked fine under SUSE 9.3 but got all goofy when I upgraded to SUSE 10. Strange.
I suspect it has to do with an upgraded version of KDE. Not sure why that should matter, but perhaps it does. Notice that when I ran chmod on smb4k to get suid root, it said that "libsmb based programs must *NOT* be setuid root." I suspect it's a KDE library issue...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.