Ubuntu Networking :: Samba Shares Used In Windows DFS Not Accessible To Remote Users
Feb 7, 2010
We have an existing Windows 2000 network that I am trying to add an Ubuntu 8.04 server to. I have put links into the windows domain DFS to the linux machine's samba shares.
The shares work fine for local users that are physically on the same network (192.168.0.X). Remote users from other offices or dialing in with a vpn client can not access the these particular folders off the DFS. However, they can map them directly from the ubuntu server.
I am running Ubuntu 10.10 and have 5 shares that I have setup for Samba (assume names of share1, ..., share5). I find that shares(2,3,4) are accessible from my MS Windows system, but the share1 and share5 are listed but Windows gives an error accessing them that I may not have permissions.I have reviewed the sharesve the same owner, group, and permissions.Is this a known Samba bug or configuration issue? I have gone through the smb.conf file multiple times as well as examining the directories and do not see what the issue might be.
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
I'm having some troubles with my samba shares on a fresh install of Fedora 10 x86_64 on my laptop. The laptop has only the KDE Desktop environment. I'm trying to share between this computer and my homebrew server via a wrt54g linksys router running DD-WRT firmware. The server is running Fedora 9 i386.
The shares on the server can be read by the laptop, and I have been consistently able to mount the server shares on the laptop using mount.cifs, but only when the firewall on the server is down. Shares are only visible between the machines when the firewall is down on the machine containing the share. I set up the shares using the system-config-samba tool, and the firewalls are both set to allow samba server and samba client. I can typically see the laptop from the server, but not the shares, and only when the laptop firewall is disabled. I can access the Laptop shares from the laptop. When trying to mount the laptop shares on the server, a warning message stating that the mount failed appears. Shares show up as correct in both the system-config-samba tool, and the KDE sharing tools. The share shows a "shared" icon in the dolphin browser.
From all that I know, the shares should work perfectly. I've searched the web, perused the man pages and how-to's, and combed through the forums, and everything I've found tells me that the shares should be working. Since they are not working, it leads me to believe that I must have made a mistake someone and not noticed it.
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.
I have Linux installed on one machine with samba running and a second machine running XP. They are going through my router and I am using the same username/passwords for both machines and I have even gone to the point of allowing access to everyone for the share I created and the worgroup in samba is MSHOME just like my XP machine. When I view (or search) my workgroup computers my Linux machine shows up and so do the shares I created but when I try to open them I just get a message that permission is denied and I may not have permission to use this resource. I even tried setting access to the shared folder to 777 but still I can't open this share. Has anyone got any idea of why this is?
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
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).
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.
My network comprises three PC's .... Windows XP, Windows 98SE and Ubuntu 9.04 running SAMBA. All PC's are configured WORKGROUP=WORKGROUP. The network connection To/From XP/UBUNTU via SAMBA Shares works perfectly OK. However, despite scouring all forum information regarding changes to Win98 ENCRYPTION, (Registry change re: DWORD "EnablePlainTextPasswords"), the Win98 PC refuses to connect to UBUNTU. The UBUNTU PC can conect to all the Win98 shared folders OK. I have disabled my Linux Firewall (Firestarter), I have run SMBCLIENT to check the user password for Win98 and it is validated OK. The Win98 error message is ....
"\Inspiron 510m is not accessible. The computer or sharename could not be found. Make Sure you typed it correctly and try again."
My samba.conf file is as follows ..... Any help or assistance PLEASE !
#======================= Global Settings =======================
## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = workgroup # server string is the equivalent of the NT Description field code....
I have an Ubuntu Server 9.10 box running Samba 3.4.0. It has 4 shares, one of which is a CIFS connection to an XP machine, another of which is a password protected share. All the shares work fine and well. However, lately the client has called to say that "everything's hanging and freezing" when they browse the shares via Windows Explorer (approximately 30+ PCs on network, variety of XP, Vista and 7 OSes).
Not all users always experience the problem, and I remote in to test when I hear this via an XP machine, and today for the fist time I also experienced this problem - browsing literally sticks and hangs. No entries in PC's eventviewer. They are running on Netgear switches, all the same age, a couple of months old. A simple reboot and and everything's fine again for an indeterminable time, then I get another phonecall and an unhappy client on the end!
I have a machine acting as a gateway for a private network. While it can ping hosts on that private network, I can't use samba (smbclient or smbmount) to access shares on hosts on the private network from that machine. Other machines on the private network can access shares on other machines - just not the gateway server.
Here's how the gateway is configured:
When I try to connect to ports 139 or 445 (via smbclient or smbmount) the mount() system call times out. As I mentioned above, I can ping those hosts, so UDP packets work but TCP packets seem to get blocked or lost.
Currently I am trying to get some fedora shares to simply connect to each other to access a read-only shared folder on a host machine (no security/encryption even required for these files!). I've tried to get a smb network share going but that didn't work (can't connect with nautilus), I've tried a quick fix with daap and rhythmbox so that they can at least access the music, but rhythmbox fails very miserably trying to connect/create that (and mt-daapd didn't help much) - Basically I get errors saying the host is unreachable.
I haven't even set up a firewall yet for this network and already I'm running into these fundamental problems. Currently I'm using Fedora 15. On a whim I tried the "public" folder and had sharing of the public folder over the network enabled - yep, didn't work (and I certainly didn't expect it to). I would be trying some more advanced CLI stuff, setting up an ssh server or something, but the computer-challenged people who have to access these files just want to be able to click something and have it work.For the operational requirements of this setup, a file synchronisation system would work (although highly inefficient since it would mean gigabytes sent over the network).
Trying to setup a Kerberos + OpenLDAP server to manage users for our Samba shares (was going to use just OpenLDAP, but apparently it is less secure than using Kerberos with it). (Distro: CentOS 5.5) Haven't even gotten to the point of connecting either to Samba yet. I have set up a Kerberos server, and configured it as necessary. I am happy that it is working as intended, as I can login and manage principals from both the local terminal and remotely on other clients.
I have setup a server (sv1.myhost.net), and configured it to talk to Kerberos (auth.myhost.net). I have created both a [URL] principal, and a testuser principal. I have set the password on the testuser but not on the host/sv1.myhost.net. I have added the keys for both users to the keytab file on the sv1.myhost.net. I am at a Windows 7 machine (on the same internal network), and have installed the Network Identity Manager. It is able to request a ticket successfully for the testuser account.
When I use putty w/GSSAPI (0.58) to remote login to the system, it says using 'testuser' and then just hangs there. Eventually putty connection times out. The fact that both machines can connect to the auth server to communicate with kerberos correctly suggests firewalls are correct. The relevant entries in sshd_config have been uncommented to tell srv1 to use Kerberos authentication.
I have setup a Centos5.5 VMWare guest with Samba and Winbind for Active Directory integration, using GUI tools. Authentication works flawlessly, with automatic home directory creation. What I want to achieve now is using local UNIX groups to controll access to shared folders, to avoid bothering AD administrators with groups management. This is my smb.conf global section:
'finance' is a local UNIX group where I added user 'COGITANSalberto' (I also tried with 'alberto') as a secondary group (primary group is 'domain users' and it cannot be changed). I am sure the user is added, because it is listed in 'getent group'. If I specify user COGITANSalberto in valid users it works, i.e. only that use can access the share, the others get a NT_STATUS_ACCESS_DENIED error. But if I use +finance, access is denied to everybody, and this is the log:
[2010/09/11 14:12:37, 10] smbd/share_access.c:user_ok_token(211) User COGITANSalberto not in 'valid users' [2010/09/11 14:12:37, 2] smbd/service.c:make_connection_snum(617) user 'COGITANSalberto' (from session setup) not permitted to access this share (finance)
It seems like winbind cannot recognize finance as a local group. For the same reason, I guess, 'force group = finance' does not work either (files are created with 'domain users' group ownership). My /etc/nsswitch.conf:
I have an ubuntu 11,04 samba domain server, I want to also configure this machine to work as a dhcp server, however this have give me some issues with te windows 7 workstations, my guest is that it have something to do with the iptables because those station do join the samba domain went both server and workstation are conected to a router.
This is the script I use at boot
#FOR SHARED INTERNET /sbin/iptables -P FORWARD ACCEPT /sbin/iptables --table nat -A POSTROUTING -o eth2 -j MASQUERADE
I haven't test it with windows xp station but I have use the same code in the past with no problems, and since this is my first time joining windows 7 station i belive there must be some other port that need fowarding.
If I want to add Windows & Mac users as Samba users, must I first add them all as Ubuntu users? If so, since none of the other users will actually be working on the Ubuntu Server, how do I disable the other non-admin users on the Ubuntu Server login screen. I am using Webmin to administer some server settings, and command line for others.
I am trying to have a serial device connect to my ubuntu machine via the com port, and forward that comport over the network to a windows box so that I can configure/access the device. I have looked into socat/ sredird but still haven't found an option that I can get to work.
Fairly new to Karmic - wanting to setup some Windows Shares on an external Hard drive. I understand that I need to install Samba to do this but when I try to install it I get the following message:-
pat@CCBC-13112:~$ sudo apt-get install samba Reading package lists... Done Building dependency tree Reading state information... Done Package samba is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: samba-common-bin smbclient samba-common E: Package samba has no installation candidate
I am using Ubuntu 9.1 and want to connect to my other computer (win 7) on my home network. I installed Samba...and it sees the 'windows network'...then it sees the pc I want to connect to, but when I try to dbl click on its name, I get 'unable to mount location, failed to retrieve share list from server'. There are at least 8 publicly shared folders on that PC that other Windows pc's can connect to without problem.
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'm trying to connect to a Samba share on a VirtualBox'ed Windows 7 that is connected to an openSUSE host in bridged mode. For reasons beyond my comprehension I cannot use the shared folders feature, so I'm using Samba instead. I configured a share through openSUSE's Samba server configuration tool:
[iTunes] inherit acls = Yes path = /home/myusername/iTunes read only = No valid users = myusername
I also set a password for this user using smbpasswd -a myusername. I can go to smb://192.168.1.6 on the host machine and log in to the share successfully, but on Windows 7 I see this: What am I doing wrong? I can connect to the shares list without any problems. It's just the login that doesn't work.
Update: I noticed that my Samba server is part of the WORKGROUP domain.
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.7-1.17.1-2505-SUSE-SL11.4-x86_64] Sharename Type
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...
[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).
The company I work for, as usual, is Microsoft-centric. I'm attempting to integrate my Ubuntu server into the domain to allow domain users to authenticate to the server and access file shares using Samba. Here's my current configuration:
I am in the process of migrating my small workplace to a basic spin i've created of f14. Everything is suave but some file browser windows eg: file upload in gmail, hotmail etc, does not show my samba shortcuts i've created nor even the option to browse the network in the "places" section. It shows other locally created shortcuts but no samba ones. Just to test it, even creating an ftp:// shoftcut yeilds no dice. I had a quick search through the forums and I couldn't find anything. I have a feeling this has an easy solution that my inferior brain cannot comprehend! Loving F14 on my macbook pro and so are my employees in my office! Feels much less bloated than Ubuntu IMHO.
I can't for the life of me figure out why I cannot browse my own shares from my linux boxes. both run OpenSuSE 11.3 I follow swerdna's tutorials and reboot several times but don't have a clue as to whats going on to prevent me from viewing localhost shares or 2nd linux box shares. I get 'unable to mount location, Failed to retrieve share list from server' error when I click on my workgroup icon in nautilus.