Problem with Fedora Core 3, Samba, gnome & win 2000/XP
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.
Problem with Fedora Core 3, Samba, gnome & win 2000/XP
I have found similar posts, but nobody has a good answer and it seems as though the treads have been abandoned, so here goes:
I am currently using a Fedora Core 3 pc networked to 2 Win2k pcs and a WinXP pc. All of the windows machines have shares. The problem is that I can't view these shares using any kind of graphical file browser (I'm using gnome, FYI). I can view the workgroup and see the computers, but when I double-click a windows pc to view the shares, I get the following message:
You do not have the permissions necessary to view the contents of "Windows Network: <computername>".
I was never asked for any kind of authentication, and the windows shares are full control for everyone. I can, however, use the command-line smbclient with a specified username and password to successfully access the shares. This, however, is cumbersome for my purposes. Does anyone have any ideas?
I am running smbd, nmbd, and winbindd.
The windows machines obviously don't have this problem accessing each other's shares.
I'm using Nautilus 2.8.1, which came with my Fedora build. I haven't tried accessing via network address, but I don't think that its a name resolution problem because it can find the computer itself, just not the shares. Furthermore, my computers (except the linux box: static) are all obtaining addresses via dhcp from my router. The linux firewall is disabled.
Also, one other unrelated question if anyone has time:
I'm running vsftpd and I was wondering if anyone knows how/if I can limit the users' collective bandwidth, i.e. allocate 40k/s bandwidth for all users to share as opposed to limiting each user separately. I tried looking into QoS, but I neither understand it nor know how to implement it. I'm not even sure if I have it installed!
Here are the contents of my smb.conf file. The only option I know of in the vsftpd.conf file is local_max_rate, which doesn't do what I'm asking. Furthermore, its more important for me to get the samba thing working.
Thanks!
smb.conf contents:
#======================= Global Settings =====================================
[global]
workgroup = WORKGROUP
server string = Samba Server
; hosts allow = 192.168.1. 192.168.2. 127.
printcap name = /etc/printcap
load printers = yes
; printing = cups
cups options = raw
; guest account = pcguest
log file = /var/log/samba/%m.log
max log size = 50
; security = user
; password server = <NT-Server-Name>
; password level = 8
; username level = 8
; encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
; username map = /etc/samba/smbusers
; include = /etc/samba/smb.conf.%m
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
; interfaces = 192.168.12.2/24 192.168.13.2/24
; remote browse sync = 192.168.3.25 192.168.5.255
; remote announce = 192.168.1.255 192.168.2.44
; local master = no
; os level = 33
; domain master = yes
; preferred master = yes
; domain logons = yes
; logon script = %m.bat
; logon script = %U.bat
; logon path = \\%L\Profiles\%U
; name resolve order = wins lmhosts bcast
; wins support = yes
; wins server = w.x.y.z
dns proxy = no
; preserve case = no
; short preserve case = no
; default case = lower
; case sensitive = no
#============================ Share Definitions ==============================
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = no
username map = /etc/samba/smbusers
[homes]
comment = Home Directories
browseable = no
writeable = yes
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
printable = yes
;[public]
write list = @administrators
[serverdrive]
path = /mnt/serverdrive
writeable = yes
valid users = evan
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440
Rep:
you should post your Qos Question seperately.
The fact that one part of the client can find the name doesn't mean you can access it by name. SMB is not the de-facto standard becuaseits good, it's defacto becuase windows uses it. Try to connect by IP, and try to file -> connect to server,even by aname, and you might have better results.
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440
Rep:
when, in gnome youu select file-> connect to server in a nautilus window, it will allow you to connect to a windows share, and you cann provide a username that way. try that.
I Have the exact same problem with my Fedora 3 Core installation and Nautilis.
However, using KDE's file browser Konqueror (if you also have KDE installed) seems to work fine. If KDE is concurrently installed, you should see Konqueror in the \bin foldder. Just make a new program launcher for it and use that instead of Nautilus. (If KDE is not installed, you should be able to install it through the package manager. KDE and Gnome can coexist quite nicely on a system.)
For some reason outside my knowledge, Nautilus doesn't like it when you change the default Samba settings. My system worked correctly when I first installed Fedora 3, but once I tweaked the Samba settings and did all the updates, it hasn't worked since. We also have this problem on another box. We haven't done any updates, but as soon as we tweaked the Samba settings slightly, it broke. Again, using Konqueror works fine.
I've triple and quadruple checked my SMB files and they look fine. With the fact that Konqueror works properly and Nautilus doesn't, I'm thinking the problem is with Nautilus itself.
I probably should have gone with KDE instead of Gnome, but it's a little late now.
Distribution: gentoo, debian, ubuntu live gnome 2.10
Posts: 440
Rep:
gnome doesn't use samba config files to configure itself, it uses the most basic defaults available. Also if you're using gnome < 2.6 your going to have problems from time to time 2.8 is a significant imporvement and 2.10 is a dream, no problems what-so-ever. I'd make sure you. Also simple file-sharing on Xp has caused problems both as a client and a server; I do not advise use.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.