Tag Info

New answers tagged

0

first you need to run sudo apt-get update then you can search for the available packages related to samba by typing sudo apt-cache search samba | grep samba also if the package was halfway installed you can fix the broken packages by using the following command sudo apt-get -f install Hope this helps. Good Luck.


0

In case anyone stumbles on this thread looking in vain for a solution - I've got (most) of a workaround after needing to change the Windows password again. Open Nautilus Choose: Files > Connect to Server Use a direct smb url to connect to the Windows machine (smb://) Sign in with the new credentials This isn't perfect, you can access the machine again ...


1

To fix the problem you may add the force user username to the list of valid users for the share. In your case: [Myshare] ... valid users = @bureau ... should be: [Myshare] ... valid users = nobody @bureau ...


-1

In Ubuntu 14.10 the printer has to been on line. That is Ubuntu must be able to make a connection. Otherwise it will fail (on my machine).


0

Unfortunatley I was unable to resolve this Issue using any of these answers or any suggestions from other forums and help. I have saved the neccessary data and will be doing a complete wipe of the HDD and re-installing Ubuntu 14.04 LTS 64-bit Server afresh. I will then instal a fresh instance of SAMBA and use security = share using this share parameters in ...


0

sec=ntlm worked for me too... I had load of problems with this from the CLI and fstab but it worked fine from the GUI (on Fedora 20) to a home NAS and to rule out things like complex passwords I created a user with a simple username and password and then used the CLI command mount.cifs to test with. I kept getting permission denied (13) all the time so ...


0

The first four parameters have been removed, not the last two (see: https://www.samba.org/samba/docs/man/manpages/smb.conf.5.html#FORCEUSER). So, just put them back in the config file and that should solve the problem. If you want write permissions to users in a particular group, add the write list parameter. It provides ability to grant write permissions ...


-2

This may be due to following reason: If valid users is provided in smb.conf cross check the smbpasswd Check the hosts file.


1

I had the same issue after upgrading from Debian Squeeze to Wheezy. Other posts I saw suggested installing the libpam-smbpass package. After I installed libpam-smbpass, changes to a user's system password were immediately reflected by Samba. (If the share was previously connected on a Windows machine, I did find that I had to log off and log back on to that ...


1

As far as my own experience tells me, you just have to: sudo apt-get install apache2.2-bin libapache2-mod-dnssd


0

Webmin is outdated and has security problems and should not be used. I had the same problem on 14.04. Many people answered my question and said Samba was not so screwed up on previous versions of Ubuntu. But this is a function and alias I add to my $HOME/.bashrc. #################### # $1 is parameter for function function fAdduser { if [ -z $1 ]; then ...


0

I have a function in my $HOME/.bashrc file which sets up one user to use Samba. Make sure you followed all the steps I have. Put this in your .bashrc file: #################### # Set Samba permissions for directory in /home. # $1=username function fSetsambaperm { echo " " # Now change permissions for Samba on their home dir. if [ -z $1 ]; then echo ...


0

I would use the following parameter force create mode (resp. force directory mode) (see: https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#FORCECREATEMODE). This will force the creation of the files (resp. directories) with the minimal settings of '770', allowing access (rwx) to all users from a group that you correctly set via 'force group'. ...


0

i would change the samba config to : [TEST-NEW-SERVER] comment = All Users path = /mnt/TEST-NEW-SERVER valid users = @users force group = users create mask = 2770 directory mask = 2770 writable = yes browseable = yes and run these command manually once chown -R root:users /mnt/TEST-NEW-SERVER find /mnt/TEST-NEW-SERVER -type d -exec ...


0

After lots of research i've found an answer. Decided to answer incase anyone else ever needs this: So the best way to do this (i think) is to install ubuntu on the computer's hard drive and then use the external drive for file shares. After installing ubuntu on the internal drive, format the external drive to ext4 (ext3 if you wish). You can do this from ...


1

This issue may be that you are mounting it as a filesystems etc, which is more complicated - using FTP (File Transfer Protocol) would be ideal for this, as it just transferring a file. To use it you first need to install a server (probably easiest on the Ubuntu machine) - you can do that with: sudo apt-get install vsftpd You then need to edit the ...


1

You can use TCP as well : How to network two Ubuntu computers using ethernet (without a router)? Looks this question has been asked before, just install openssh-ssh server it's easier to use rsync with this tool


0

http://lmgtfy.com/?q=install+smb+ubuntu 3rd one down looks good. Just install on both computers. You could also use rsync to keep the same folders on both machines, or SCP/SFTP if you want to get crazy with it.


0

Actually the problem was that i hadn't restart the system, so i had mounted nothing. Restarting the system or just forcing the mount everything works perfectly. I've just typed: sudo mount -a


0

Samba troubles could be a number of things, i'm just going to list a few things you could try: Rule out the firewall. Disconnect the Internet then disable the firewalls and see if it works, if you hook up something you now have something to work on. make sure your "smb.conf" file has a mention of: "name resolve order" with your prefered settings. If the ...


0

just add users in /etc/fstab like that: //192.168.0.72/Triple_RDF /media/Triple cifs credentials=/home/ubuntu/.smbcredentials,iocharset=utf8,sec=ntlm,users 0 0


0

I have the same Ubuntu. Make sure you have a space on BOTH sides of the '=' sign in the /etc/samba/smb.conf file. Samba is really picky. Also when you change something in samba, restart it like this: sudo restart smbd; sudo restart nmbd Here's a link I tried too. To show you smb.conf file do this: testparm -s You can send that output to a file, and ...


0

This error message may appear after a samba connection has been idle (Bug #1321354). Microsoft servers drop idle connections after 15 minutes. This behavior can be disabled by the following command as administrator (Article ID: 297684). net config server /autodisconnect:-1 Alternatively, adding the following script to the gnome startup applications keeps ...


2

List the iptable configuration with the command sudo iptables -L Then use the following script to open CUPS connection on the port 631 ## open cups (printing service) udp/tcp port 631 for LAN users ## iptables -A INPUT -s 192.168.1.0/24 -p udp -m udp --dport 631 -j ACCEPT iptables -A INPUT -s 192.168.1.0/24 -p tcp -m tcp --dport 631 -j ACCEPT Allow ...


0

Here is the detailed description of accessing samba from Windows8. I'm using this method and works pretty fine! create one user in ubuntu server #useradd smb1 #passwd smb1 Set the password accordingly # smbpasswd -a smb1 For example, set the password as samba123$. Add a user to a Samba share Open via vi /etc/samba/smb.conf [accounts] comment = ...


0

While you upgrade your machine from 14.04 to 14.10 packages which was referring the wireless printer would get differed and this is reason it was not showing your wireless printer. Reinstall your printer which may fix this issue. Also, Please check whether the new printer connection is trusted connection in your new firewall settings. Hope this helps!


0

I have only a little Ubuntu experience, and less Zentyal experience, but I had a similar issue today. I was restoring files from an old Ubuntu/Samba fileserver to a new Ubuntu/Zentyal fileserver. I set/updated ACLs, used my administrator:adm ownership, but could not browse on a windows client. I then did a chown shareuser:sharegroup (a user/group that ...


0

According to man pam.conf, sufficient and optional have longer equivalents: sufficient [success=done new_authtok_reqd=done default=ignore] optional [success=ok new_authtok_reqd=ok default=ignore] The guide changes sufficient to [success=ok default=ignore], which is close to optional, so I think what it really wants to achieve is change sufficient ...


2

Since the latest version of Samba available on Ubuntu is 4.1.11 for 14.10, and the Samba team's PPAs are long dead, it looks like the only way you can upgrade to 4.1.13 is installing from source.


2

Just install the samba client: sudo apt-get install smbclient


0

Announce downtime to your users stop samba on old server copy data to new server copy samba config to new server start samba on new server and look at the logfiles If everything is OK, announce the move to your users, if not, open an new question with the specific error message(s).



Top 50 recent answers are included