Samba requires authentication to browse unsecured Windows shares
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Samba requires authentication to browse unsecured Windows shares
Hello,
I did a quick search for a question like this one, but came up empty-handed. If this has already been answered, direction to the appropriate thread would be appreciated....
I am a reasonably competent Linux user running Fedora Core 1 on an Athlon with samba-3.0.0-15 installed from RPM as supplied in the original install image. Though I have used Linux continuously for several years, this is my first attempt at getting samba running, so please pardon my ignorance.
In short, I want to be able to access Windows shares, especially certain public shares that are set to not require a user name and password.
I have modified my smb.conf file to list the correct Windows Workgroup designated by my university and have initialized the samba service by running "/etc/init.d/smb start" as root. The remainder of the smb.conf file was left unchanged, including the security level. (This only has to do with the local SMB server, not client, right?)
By running "Network Servers" from the RedHat/Start menu in GNOME, I see various workgroups, including the one that I wish to browse. Inside the workgroup are all the Windows servers that should be present. However, when I try to browse volumes on ANY Windows server, including those that I know for a fact do NOT require a user name password (when accessed from a Windows machine), I am prompted for a name/password. I have been unable to figure out how to get around this, since these servers simply have no user names or passwords associated with them.
If anyone could suggest how to let me browse freely shared volumes on Windows machines, I would greatly appreciate it; I hate having to go to the computer lab to download homework assignments from share servers.
I presume that by guest logins being enabled you are referring to the servers to which I am trying to connect. I do not administer the servers in question. All I know is that these servers I ordinarily do not have to supply credentials for, whereas for other campus servers I do have to supply credentials. I.e. the server volumes in question are public read-only.
My smb.conf file (non-commented sections) is pasted below.
-Conrad
[global]
workgroup = REED
server string = Samba Server
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/%m.log
max log size = 50
security = user
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
[homes]
comment = Home Directories
browseable = yes
writable = no
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = no
writable = no
printable = yes
This may be of little help, but I have never set any permissions when I set up my home network. I was too lazy to remember the samba syntax, so I used Linneighborhood (a GUI network browser). To access a share, I chose to "browse as user" and hit enter - as in no password. I can read/write between both machines that way. From the WindowsXP box, I can browse the shared folder on my Mandrake machine and vice-vera.
So, you may already be able to access the userless/passwordless shares without knowing it. Try to browse as user (use your user from the machine you're on) and don't enter a password. It might work (doesn't teach you anything, really, but if it works...)
shultzc, I misread your first post. I thought you administered the servers in question. Sorry about that.
What is this tool you are using to access the shares? Is it just loading in Nautilus?
You could also check out LinNeighborhood... I use KDE myself and just use Konqueror to browse such shares at home/on my campus.
Your smb.conf shouldn't actually affect you browsing the shares. That file is used for the shares you have on your own machine.
In KDE, there is a network browsing section of the Control Center, thats where I supply the credentials my university wants me to provide. I am not sure if there is an equivalent area in Gnome.
Have you tried just leaving the username and password fields blank when you try to browse the shares?
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
I to have this same issue... Linux requiring user/pass for public shares.
I have tried several options and found no fix... I figured since I was able to config samba to work across 3 networks it would be simple to stop the user/pass browsing requirement... NOPE...
if you know the server name and share name of what you are trying to get to (or just the server, if it's browseable) then just go to konqueror.
in the address bar type smb://ServerName/ShareName or just smb://ServerName. konqueror supports browsing without credentials just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.