Networking :: Samba Requesting Password When Accessing Shares ?
Apr 2, 2010
I'm trying to do the normal setup of sharing some dir's on my linux machine using samba, to allow a windows laptop to access them.
I've managed to get the printer shared and this is allowing to send print jobs, which come out beautifully! however the actual file shares still aren't accessible
Depending on my settings, if I have security = user then when I access from the windows machine I get a username and password box - I dont want this functionality, I want the system to access right away as it would between two windows shares.
If i change security = share then it simply lists the shares, but tells me they are all inaccessible.
I've googled and searched here, tried various different things but I just can't see why/where its asking me for the username/password combo.
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
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.
Since "upgrading" (ha!) to lucid I have had a number of problems that I am working my way through. The latest is accessing samba shares from a Win7 PC. It takes minutes to open the requested share from the Windows 7 PC. File transfers, once the directory is accessed, can be measured in bytes. It is an absolute trickle.
AFAIK the smb.conf is unchanged and, in any case, there is no problem accessing the shares from another linux PC.
I wonder how to get Samba share access working well...Dolphin supports Samba but it doesn't really mount anything, it seems... Non-KDE Applications therefor can't access samba that way. In Gnome there was a workaround for the same problem. You could simply go to ~/.gvfs in any application and find the samba mounted there.Is there anything like that in KDE? I set up a Samba mount via /etc/fstab for now but that is quite annoying because it fails after each Suspend, changing WLAN Access Points, etc. Then I have to go to the console and manually launch sudo mount -a to get it working again. How can I make things more comfortable?
P.S.: I'm even up for using something else than Samba to talk to my fileserver. However I don't know of anything that would work better in this regard. (NFS would have the exactly same problem for example)
I am having a problem accessing my samba shares from my notebook that has a fresh install of Fedora 15. I know that the server with the samba shares is working since I can access them from the windose box. I have just moved from using Ubuntu to Fedora and have definitely found my home. How would I tell if samba is running (or any service for that matter) on my notebook? I Installed samba-client
Code: yum install samba-client
Though I still cannot access the shares. All it shows is windows network.
provide support for a small business that uses Windows machines to access files stored on an Ubuntu server which has just been upgraded from 8.04 to 10.04 (32 bit version). Before the upgrade the users accessed their share by this batch file:
Code:
net use x: \servernamesharename /user:username
This would then prompt the user for his or her password which they would enter to allow them access to the share.Since upgrading to 10.04, the user gets a "system error 58" stating "The specified server cannot perform the requested operation"If the batch file command is changed to:
Code:
net use x: \servernamesharename
The same error message is given. The only work around I have found is to modify the file to read:
Code:
net use x: \servernamesharename /user:username password
This is not ideal at all as it makes the password protection useless.When I performed the upgrade I left the smb.conf unchanged. The smb.conf file is:
Code:
# # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the
When I boot up, or come out of standby, etc, it takes about a minute for my Windows shares on Win 7 to show up under Network. Is there anything I can try that will make this initial connection faster? Either on Debian or the Win7 machine? I have the latest Debian vanilla. This is over wifi. My other devices list the shares right away.
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.
Today I noticed my sdl modem flashing away when I had no internet access programs active as far as I was aware. I did a 'ps ax' to see what was running. I saw nothing that warranted internet access. I didn't recognize the gvfsd-computer process and tried finding documentation about it on my system. I began to feel uncomfortable when I couldn't find anything showing what it was. Finally, I killed the process and the internet access immediately stopped. Research on the net showed that gvfsd-computer is a file browser. I find this very disturbing. Why was a file browser accessing my disk drive (the light was flashing) and why was it accessing the internet without my requesting such an action?
i have 3 ubuntu machines running 9.10. All of them are running SMB so that the Windows machines can access the shares on the Ubuntu machines, but the ubuntu machines can not access shares on the Windows machines. When I click to connect to a windows machine ( all of them running XP), it says "connecting to COMPUTERNAME.." It never opens the computer, and it always comes back with an error saying that it failed to connect. I haven't been using ubuntu for very long, so im not as savvy with it as I am on windows. All windows machines can see all ubuntu shares, just not the other way around and I'd like it to be both.
I just got my Ubuntu 10.10 laptop to finally be able to access my Windows 7 Professional's shares, and I'd like to share how I got it working. Whenever I would go to Places > Network on Ubuntu, and then double click on my Windows computer (sometimes after finding it in Windows Network > {workgroup name}), it would immediately bring up a box saying "Password required for {computer name}". My Windows password wouldn't work here, but I didn't even want to be asked for a password. In Windows, under Network and Sharing Center > Choose homegroup and sharing options > Change advanced sharing settings..., Turn off password protected sharing was already selected.
So, I eventually found out that samba (the program Linux uses to talk with Microsoft's SMB network share protocol) has a bug of sorts. The format of the SMB packets coming from a clean Windows 7 is known by samba. However, if you install Windows Live Sign-In Assistant (which is provided through Microsoft Update) on Windows 7, the packets coming from Windows 7 are modified, and samba can not handle this. A patch has been written for samba, but Ubuntu's repositories (which has samba version 2:3.5.4~dfsg-1ubuntu8.1) does not yet have that patch.
Also, it seems Microsoft has stopped Windows Live Sign-In Assistant from appearing in Programs and Features. It doesn't appear even if you specifically download and install it separately. I did, however, notice that the installer calls itself Windows Live Essentials 2011. So I found that in Programs and Features, and uninstalled it. It asked which components I wanted to uninstall, and I selected all of them. Rebooted Windows, and now I can access the share no problem. I also grabbed the offending packet using Wireshark before and after that uninstall. The packet is indeed different. Specifically, without Windows Live Essentials 2011, there is no mechToken in the packet.
The current version of samba available is 3.5.6. I may try downloading and compiling that later, and see if it deals with the change that Windows Live Essentials 2011 makes OK. Also, it may be possible to get the share working without uninstalling every single Windows Live Essentials 2011 component. You may want to try that if you would like to keep a component.
We are using spare parts (Socket 775 Biostar motherboard, OCZ 500wat PSU) to build a computer that will just be another system in the house. I want this system to be running Folding@Home, and the F@H SMP client for Linux is much less of a headache than its Windows couterpart, so I would like this computer to run Fedora. My dad loves networking, and knows how to do it in XP / Vista, so he has always opposed my frequent use of Linux. There are ways of accessing Windows shared folders from Linux, but that I haven't figured it out yet. I want to access Windows shared folders from my Fedora 10. I don't know how to go about doing this, can anyone point me in the right direction? Do I have to install anything special? I can go to Places, and then Network (in Gnome) and I see "Windows Network", but when I click it, I get "Unable to mount location Failed to retrieve share list from server"
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 ?
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 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
So my brother has a home network that is setup with multiple workgroups (don't ask why - I have no idea and he refuses to change it). Anyways I just installed Mint 9 (Ubuntu 10.04) on my mother's computer and I need it to be able to access the fileserver in her house where her data is stored. The Mint system is part of the default workgroup and can only see one other system in this workgroup.
The workgroup the file server is a part of is called "hobnw", the server's name is "fileserver", and the share I want to connect to is called "TV Shows" How can I connect to this network share on Linux? (I also know the username and password) When I browse the network under nautilus all I see is the default workgroup and no others. All of the Windows systems on the network (Windows XP, Vista, and Win7) all see and can access the file server without issues.
I'm having trouble setting up samba to work with my vista machine. Whenever I try to mount certain shares I'm getting error 13- permission denied. Specifically, I'm trying to mount my entire C: with this command at the console:
The funny thing is that I CAN mount some other shares, but not all. My distro is slack-current. I've been following as many relevant threads on this issue for a while now and have tried as many of the suggestions as I could understand, but it's getting to the point that I've lost track of what I've tried and what I haven't. Things I have tried:
Checking permissions on the shares: seem to be ok enabling encrypted passwords: not sure if I did it right. editing the registry for LmCompatablity
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.
After latest samba updates from updates-testing (F11) I can't copy any file from the network via samba: when copy process reaches almost end of the file, error message appears 'Invalid argument'. Such error happens with any read attempt on a network file - the last ~5% of a file can not be read.
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:
[300] path = /media/Secondary Storage available = yes browsable = yes public = yes writable = no
[500] 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
I use Ubuntu 9.10 on my laptop and Vista Premium on my two desktops. Until recently I was able to view and access my document files on my desktop from within Ubuntu. I can no longer do so.
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:
[URL]
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'm trying to setup two samba shares on ubuntu server 10.04.1 lts x64
The first is a Read-Only share for windows users that doesn't require a password. This i've managed to do so far.
The second is a Password protected Upload share. So far I am able to have both shares (which access the same directory) but am unable to log in to the pass word protected share.
I know i'm not doing things quite right, and would like a little bit of help
The smb.conf file is the default ubuntu file with these added shares:
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 some samba shares working where all I did was right click on the folder, enable sharing and enable guest access. These work fine.
However, when I tried to use the manual way:
[URL]
to create samba shares, so that they would be password protected, I cant access them. In windows 7, the shares are visible so I click them, click "use another account" and type in my samba name and password I created, but I can't access them.
Here is smb.conf
Code: # # Sample configuration file for the Samba suite for Debian GNU/Linux. # #