Ubuntu Networking :: 10.04 Can't See Shares On 9.10 Samba Server?
May 10, 2010
I have an Ubuntu 9.10 Samba file server. I have set up Ubuntu 10.04 netbook remix in a home network which also has Windows XP home and Vista computers already present in the network. The XP and Vista machines have no problem accessing the file shares.
The server is running mhddfs with FlexRaid. The security is set to share level access. I have a hosts allow line in the smb.conf file to permit access to certain IP addresses and have added the 10.04 netbook remix IP address to this hosts allow line.
I cannot access shares from the 10.04netbook remix machine if the hosts allow line is active, but have no problem from the windows machines. If i comment out the hosts allow line, all machines can access the share, including the netbook remix machine. I am fairly new to Linux and would appreciate any help in solving this problem.
I have a problem with 'Samba' shares on Ubuntu 8.04. Bringing shared folders over from Windows (on another computer) is not a problem...until I try same process with a Windows backup folder holding .tib data from an 'Acronis' backup.The files appear in Ubuntu Network, everything looks o.k., Ubuntu just won't copy the data to another folder. Other shares work without a problem, its only with these ':.tib' data.
This one has proven to be a real for me. On one of my Samba shares on my server I have a folder of mp3 files of my CDs. The one I am having an issue with is "Clarence Carter/Dr. C.C." (yes, the one with the ULTIMATE party song). The "Dr. C.C." folder name is normal locally, but across Samba it comes out "DMOU3A~H". I can still access the folder this way, but it would be nice to not have Samba mangle the folder name this way. I am using Samba 3.4.2 on an Athlon64 X2 system running Slackware64.
PDC SAMBA + OPEN LDAP (ubuntu 9.04) Linux (File Servers) + Windows machines all working well
I'm trying to set up a share drive on my new server using ubuntu 9.10 with samba (v 3.4) and ldapclient and the shares are not working when I defined Valid Users for share folders, that keep me ask me about my user and password, on the logs I have:
[global] workgroup = FLOWCONNECT server string = OSLO SAMBA FILE SERVER [code].....
I have the same set up on my File Server (Ubuntu 9.04) which use samba 3.3 is working fine.Someone know if has some different setting between samba 3.3 (ubuntu 9.04) and samba 3.4 (ubuntu 9.10) that could cause this problem ?
I have a fileserver that I want to share out samba shares. However, i configured samba to have another netbios (SAN) and my windows box still sees whoopn-SAN which is the name I gave to my server when i installed it. Now I am using 9.10 and I know that i can create a share from the gnome gui in nautilus and that appears to be a windows like share. How can I turn OFF the windows like shares that ubuntu does out of the box and use ONLY samba? I ask because there appears to be a conflict of permissions b/w samba and this stuff.
It's been awhile since I posted anything which is a good sign my install has been working well and I have been able to handle most everything. However, I'm not able to handle this issue. I recently installed F11 and everything went well. But, when trying to see my other computers on the local network, I cannot. I receive this error message: Unable to mount location Failed to receive shared list from server. I understand the message as it is obvious, but do not know how to fix it.
I've been running a Samba server under RedHat 8 for five years without a hiccup. I want to cut over to a F10 box but cannot get shares accessible. smbclient attempts fail over NT password error. SELinux is disabled. Server is visible on the network. Users require no password access to shared data.
# Samba config file created using SWAT # from UNKNOWN (>) # Date: 2009/06/12 14:15:15
I want to setup a Linux File Server for a small windows network (around 50 users). I do know that I am gona need Smb service/pkg for that. I haven't used Samba for a while now and as per the best of my knowledge, entire communication (including usernames and passwords) between a samba server & windows client machines will be plain text. Is there any way to secure all this communication??
Secondly, if i remember correctly, MS windows wont let me mount more than one samba shares as network disk when all my shares can be accessed by different smb users with different passwords?? is there a solution to this problem? OR may be if there is any other package available for this purpose so that i wont have to use samba?
So I setup the newest Ubuntu on my old desktop on a 30g HD and have 2 200G HDs with a ntfs file system on those two. I got SSH and FTP configured, then went on to setup Samba.I have it (seemingly) set up well. /dev/sb1 gets mounted on /data1 /dev/sc1 gets mounted on /data2.I want anyone connected to my router to be able to see this machine and be able to read and write to both shares.
I configured WINS on my laptop to point to the linux box. and i've seen the pc in question (TECH-PC) in "My Network Places" on both of our laptops.Long story short, I try to connect to my network share and it says i don't have permission and i need to contact my network admin. This computer is the only one with Linux installed, the rest are windows-OS.Let me know if you need more info, pretty stumped here, have searched, read, scrapped my install and started from scratch, maybe i need to sleep on it
I am working as a Linux administrator in a very small data centre with 5 servers with following routine tasks.
1. Managing SAMBA shares and giving user specific access for the shares. 2. Scheduling backup of some mount points with rsycn to store data in remote hard disk 3. User and group administration, with sudo access. 4. Creating and Managing Xen Virtual machines and giving access to other project teams. 5. Automating some tasks with Shell Scripting. 6. Managing FTP server for user uploads.
I have practiced a lot in my home laptop without RHEL training, Cleared RHCE and LPIC1. I want to do some advanced system admin tasks, but do not have option in my current data centre. With Above skills is it possible to get a job ?
First off a little history of me lol. I'm not completely a Linux noobie, but I'm not the most advanced user either. With that said I have a few interesting problems with Samba.First off I can see the NetBios name under Windows Networking (Windows 7), however everytime I try to connect to it I get an Access Denied and/or "Incorrect Password/Username" error. I have gone into secpol.msc and changed the values that other posts have suggested. Both the server and the workstation are located under the same group, and I have used the smbpasswd -a <username>. The server is not configured to be a Primary Domain Controller so.. I'm lost. Infact my brain hurts from 3 days of this. I have posted my SMB.CONF file to see if that helps. Hum.. Maybe I'm just trying to access a file share that isn't there..
Still new to Linux and especially samba. I have setup samba for 2 shares, will list below shares. 1 which requires a login and 1 temp folder which I would like guest access to. Currently I have security = user which works great for the data folder which requires a login. If I try to access temp I get asked for a user name and password as well. I tried to set security = share which then allowed access to temp with out a login but also allowed access to the data folder. From the data folder I emoved public = yes. I then get asked for a user name and password like I should but the system will not accept it. This is a Centos 5.5 server with a mail server on it.
[data] comment = Data Folder path = /home/data/ public = yes writable = yes browseable = yes printable = no avaliable = yes write list = glenn, force create mode = 0660 force directory mode = 0770
[temp] comment = temp folder path = /home/temp/ public = yes writeable = yes browseable = yes guest ok = yes guest only = yes guest account = nobody available = yes force user = nobody force group = nobody
As the subjects states, I cannot see my windows 7 shares from any of my *nix computers. I tend to over complicate things and I may do so here, but I want to try and be as thorough as possible in explaining the situation. I'll state w/ the basic layout of my lan code...
I have a samba server set up on my computer, and I can only access the shares over the network by loging in as my main user. This works for all shares, on any drive. When I log in using my fileshare guest account, I get the list of shares, but after selecting one to connect to, it gives an error that the server isn't available. Any share off the boot drive won't work. I don't know if it has to do with permissions, or it's a config problem.
[Administration] comment = Administration path = /home/adm valid users = adm public = no writeable = yes browseable = no
We have two samba users: samba and adm. The first is used to connect to Storage and Backup shares, and adm is used to connect to Administration share. There are two problems:
1) If Storage and Backup shares are connected to a Win7 box, the Administration share cannot be connected. All we get is an error saying that that share is already connected with different username. 2) We have managed to work around this by connecting the Administration share with the IP-address of the server instead of it's name(?!). The problem then becomes that sometimes connecting Administration share this way makes Storage share read-only. Not always though.
Wrong "security" type in smb.conf (was "user", needs to be "share"). For some reason the Storage share still occasionally gets connected read-only. Win7 also tends to forget the passwords/usernames for some shares upon reboot (not all of them, though).
I have setup Samba shares on my Ubuntu 10.10 and assigned different different username and password combination for each share.
The sharing works perfectly fine on all the Windows machines but it does not work on OSX. When I try to connect using OSX, it ends up showing waiting icon (screenshot attached) after entering username and password. (It asks for the login details after selecting the share from the list)
Following is my smb file content:
Code: # # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the
find that i cant access from my ubuntu box (desktop), now running 11.04 (i was able to access yesterday, when i tested the config). I CAN access from my XP and Win7 virtualboxes.and also from another win7 on the house.. So server is working good aparently.This is all i modified from the default config file:
Code: ####### Authentication ####### # "security = user" is always a good idea. This will require a Unix account
I recently switched from centos to fedora as my server choice. Probably not the best decision but I like trying new things. Now before I switched I had my samba server setup just they way I wanted it. Now I'm having a hard time getting it back to that way. Here is my smb.conf
Code: [global] workgroup = workgroup netbios name = netbios name server string = Linux Server security = user wins support = yes encrypt passwords = Yes domain logons = yes [homes] comment = Home Directories browseable = yes writable = yes valid users = %S
[me] path = /home/me read only = no public = yes create mask = 0777 directory mask = 0777 browseable = yes writable = yes
Now I did throw away my old smb.conf because it wasn't that complicated and I figured I could reproduce it.. aside from that everything is working except for the fact that I can access any share I want to listed without it requesting a password. I have a username and password setup with smbpasswd and I think everything else is setup correctly involving samba shares but I have no idea why it won't request a password.
My environment in a nutshell is like this: - I'm a member of a Windows AD domain environment that spans many different subnets. - My client workstation (Windows XP) is part of this domain and resides on one subnet. - The server I'm trying to get Samba working on (SLES 10) is part of the same domain but resides on a different subnet. - I want to access shares on the SLES 10 box from my workstation.
Here is what does work: 1. I can ping the workstation from the SLES box, both by hostname and ip. 2. I can ping the SLES box from my workstation, both by hostname and ip. 3. netstat -an shows that the SLES box is listening on ports 139 and 445. 4. I can telnet from my workstation to the SLES box on ports 139 and 445. 5. Output from smbclient -L coolserver (hostname obfuscated):
Code: Enter cooluser's password: Domain=[COOLDOMAIN] OS=[Unix] Server=[Samba 3.5.8-30.4-2516-SUSE-CODE10-x86_64] smb: > So, cross-subnet communication seems to be working in a general sense and I have verified that my share is present and accessible by my chosen user id.
Here's what doesn't work (from the workstation): 1. Output from net view \coolserver: Code: System error 64 has occurred. The specified network name is no longer available.
2. Output from net view \coolservercoolshare: Code: System error 5 has occurred. Access is denied.
3. Same output as above if I try to connect via IP. However, when I run any of the above commands from my workstation, I see the following in log.smbd on the SLES box:
Code: coolworkstation (10.49.140.36) connect to service coolshare initially as user cooluser (uid=12171, gid=500) (pid 29039) [2011/07/08 00:39:29.098422, 1] smbd/service.c:1251(close_cnum) coolworkstation (10.49.140.36) closed connection to service coolshare
I'm not really sure how to interpret this because those are the exact same entries that get logged when I connect to the share locally, via the smbclient utility on the SLES box, which works fine... but from the Windows box I get the "Access is Denied" or "The specified network name is no longer available" errors. I also occasionally see this in log.smbd:
Code: [2011/07/08 01:01:19.858308, 1] smbd/server.c:240(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2011/07/08 01:01:33.828692, 0] printing/print_cups.c:108(cups_connect) Unable to connect to CUPS server localhost:631 - Connection refused [2011/07/08 01:01:33.832127, 1] smbd/server.c:282(remove_child_pid) Could not find child 29781 -- ignoring
I don't know if that is relevant. I created the Samba user via the smbpasswd utility and my smbusers file maps the system user directly to the Samba user, both of which have the same password. Here is my smb.conf:
Code: [global] workgroup = COOLDOMAIN netbios name = coolserver domain master = no preferred master = yes local master = yes wins support = no .....
My workstation and the SLES box are both pointing to the same WINS server, which services the entire domain (which is also one of the DC's and one of the DNS servers). I'm really not sure what's going on. I'm guessing it probably has something to do with the subnet boundaries or the WINS configuration or something along those lines. I just don't understand because the smb daemon seems to be logging "successful" sessions from my workstation... but then the session just insta-closes.
this is really a brainstorming thread seeking advise on how to setup some samba shares within a small office network. For the quick judgers:
-no I'm not an IT expect and I'm not even the IT at the office, I just fill in this gap too. -I have looked into several samba 'by example' tutorials - none seems to fit my needs or answer some of my Qs.
So I seek advise from your experience: What do I know:
-the functionality of the setgid to have subfolders inherit the group owner of the parent folder -the fact that I don't want samba in 'share' level in order to register the owners of files -the functionality of acls that enables inheritance of rwx permissions to subfoldrs of a parent folder. - the groupmod -o option but that doesn't help apparently.
So this is a 25ppl civil engineer consulting office. The physical groups of ppl working here are: engineers, drafters (those who generate the drawings , i'm not sure if thats the correct term), and secretaries. The job usually is done in the following way, once a project commences a project folder gets generated and everything is done in there. incoming mail arrives there (secretaries put it there), engineers do they calculations on speadsheets, write reports and do draft drawings and, finally, drafters take the draft drawings and finalize them. So pretty much everyone of these 3 groups needs write access to the main project folder.
How do I accomplish that? as which group should I create the project folders? It came to mind the notion of group of groups. Now that the actual owner of the file is not so important anymore (several engineers will need to have write access to the folder) and group becomes important, it would be nice to have the ability to add... groups (instead of users) to groups! so that the permissions to a group are inherited by its children groups... Does such functionality exist of can it be implemented somehow?
How do I go about giving access to everyone and at the same time, NOT giving up on the 'user' secutiry level of samba (and NOT just giving rwx permission to 'others'? Is it possible? or Should I instead forget about individuals and match the 'physical groups' to 'linux users' and 'groups of groups' to 'linux groups'? ( This means I should give on ownership of files by individuals )? Since its a small office some work is mixed - engineers might pickup incoming email, a secretary might do abit of drafting work etcetc.
Dolphin will only open Samba shares if I open them by typing in smb://SERVER-IP. It also does not show up in the Network section of Explorer under Windows 7. How do I fix this? The only Samba share icon that shows up in Dolphin under Network --> Samba Shares is Workgroup. If I click it it changes smb://workgroup, but then it does nothing and shows no files. Here is my Samba server's smb.conf file.
I'm trying to share some folders over the network, but the shared folders are not visible on another computer. This is through double clicking my computer from the Network list in Nautilus. However, I can access the share by typing the full address(<computer name>/<share name>) in "File > Connect to Server...".Since I can't type the address manually from my blu-ray drive, I need to get the shares to show on the network. What is wrong with my settings?
I setup shares on a fresh install of Ubuntu 9.10 via the shared folders application from here: [URL]. The shares are visible on my vista laptop but when I go to open them I get an error "you might not have permission to use this network resource". I set the smbpswd to nothing via the method in the above article as well and my /etc/samba/smd.conf has the follow lines:
 path = /media/Secondary Storage available = yes browsable = yes public = yes writable = no
 path = /media/New Volume available = yes browsable = yes public = yes writable = no
i have a file server running kubuntu and samba, when i plugged it into a different router, the router assigned it a different IP address (as I expected - its using DHCP) - but the old router was supplying 192.168.1.x type IP's and now the new router is suppliing 10.0.0.x type addresses.I now cannt see the samba shares on the file server.the computers can ping each other and they have working connections to the internet
Been trying to deal with this one for some time, and still not sure it's more or an issue on the Samba or Win 7 side.
Running Ubuntu 10.04 with Samba 3.4.7, using Windows clients from 2000 on up to access shares.
2000 and XP have no trouble both connecting initially to shares, but upon reboot the shares are disconnected and do not automatically reconnect unless one of them is double-clicked on. Passwords and mappings are saved such that Windows tries to reconnect upon restart. When manually reconnected in this way, shares remain open as they should. This isn't a big issue, but it would be preferable to have these shares reconnect so that links and shortcuts across the LAN work right from bootup.
The bigger issue is with Vista/Windows 7 - When shares are set up with appropriate passwords and such on the clients, they work as expected, until the client is rebooted. After signing into windows 2 things are observable:
- Black screen for 2-5 minutes before desktop appears
- error message appears when you try to double-click on a mapped share (even with a saved password) that the connection cannot be restored.
If you go into credentials manager and delete the saved password for the share(s) on the samba server, you are prompted for the password when you try to open any of the shares - reenter it and you're then fine until the next reboot.
There must be some issue with the persistence of the saved password, but not sure if this a Windows-side issue or not. Read some other info on this, and had to make the following changes earlier to even get Win 7 clients to connect to samba at all:
It appears that when Win 7 starts up, it simply can't connect using the saved password, and the desktop doesn't come up until the reconnecting action(s) time out (if you disconnect your win 7 machine from the network the delay is not present).
It's not a game-breaker, but really annoying when rebooting having the delay and reentering the network share password(s).
Just set up Ubuntu 10.4 AMD64 on an old machine. We have an existing Ubuntu machine acting as a SAMBA file sharer. The other machines, windows and ubuntu have no problem in accessing files on the server. This machine reports that it can see the server on the network but instead of the expected data we see what is on the local machine. I admit I am out of my depth with SAMBA.
I have a NAS running Samba. My Samba shares are accessed from a Windows computer, it works very well.
With the kubuntu 10.04 computer, things are different : I can see the Samba shares in Dolphin, and copy files to the local drive, but lots of applications don't allow me to open a file on a Samba share.
Some applications such as OpenOffice let me browse to the share but refuse to open the remote file
Some other applications don't let me browse to shares at all.
What's up with that ? Surely I'm not the only one wanting to access files on a NAS ? How do other people do it ?
PS I chose kubuntu 10.04 because the 10.10 install hangs, the "ui" workaround I saw here and there did not work, the only solution offered was to go back to 10.04