Debian Configuration :: Samba - Cannot Access Server After Upgrade
Mar 12, 2016
Following yesterday's and then today's upgrade of my Debian 8 32-bit system (among other things to samba 2:4.1.17+dfsg-2+deb8u2 (yesterday: ...deb8u1)) I cannot connect my Mint 17.3 laptop to the server anymore. Were there any changes to smb.conf regarding authentication or other aspects that might lead to this problem? I am enclosing part of my smb.conf. By the way - I also have trouble using ssh to connect to the Debian machine, such as the ssh-command taking "for ever" and then getting the message "Write failed: Broken pipe" when entering an ls-command on the command line.
workgroup = RAINERMUSIK
netbios name = hsdesk
server string = Samba Server hsdesk
Let me introduce myself, my name is Carlos Alegría from Chile and I'm System administrator for a educational Institute. We use samba+ldap, for login accounts and file sharing but we not use samba with PDC.
Long time ago at the 2009 year, I was Installing the same system and this worked perfectly. But on our summer the hard disk of server has broken, so i was need installing all the system again. So the problem is with SAMBA, when i connect to the network resource, this is to slow, and when i try transfer files are slow.
My sistem is on Debian 8 Jessie and the Samba Version is 2:4.1.17+dfsg-2+deb
Code: Select all[global] workgroup = LABORATORIO netbios name = Shinigami server string = debian
I've got a fresh Wheezy/Xfce install.I'm trying to access a remote samba share the gigolo way. It is an external USB hard drive connected to my router. I can access it read only using the following URL with Icedove: smb://bbox/
Anyway, this is just to try and give might-be-useful information, but ultimately, I don't really want to use fusesmb. I would rather have the gigolo way working, allowing local network shares browsing, auto-connect, etc.
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
wants some sort of logging capability on the system. to have a log of every change to every file, although that might be a bit unwieldy. perhaps a simpler compromise would be some way of monitoring a few specific folders, and tracking all changes to them, including the user that did so. Particularly important is that it should be possible to work with access through samba, as we want to track what users on the network are creating or changing files. Is there functionality like this already built into debian or samba? is there a useful additional app to gather this information? or am I going to need to be grep'ing log files to present something useable?
I have just upgraded to Jessie and everything seems to be OK apart from printing from a windows machine to my print share. This was working previously under wheezy. I can print a test page from Cups without any problems, but when I try and print from windows, Samba seems to crash completely and is constantly writing these messages to the logs. Then I lose access to the other shares, presumably while it repeatedly crashes.
STATUS=daemon 'smbd' finished starting up and ready to serve connectionsPANIC: assert failed at ../source3/printing/printing.c(486): pjob->jobid == jobid [2015/09/22 12:02:03.989596, 0] ../source3/lib/util.c:785(smb_panic_s3) PANIC (pid 3704): assert failed: pjob->jobid == jobid [2015/09/22 12:02:03.991930, 0] ../source3/lib/util.c:896(log_stack_trace) BACKTRACE: 27 stack frames:
A very strange thing happened to me today after upgrading a Lenny server to Squeeze. All seems to be working great except for the fact that I cannot join the server to our domain (made a work copy of the virtual machine holding Debian, upgraded that, renamed and changed IP).
The problem I'm having is related to Samba as far as I can tell. On the Lenny server(s) I have the 'net' command to join a server to a domain but not on the upgraded version (Squeeze). It just says command not found and there's indeed no 'net' in /usr/bin where it's supposed to be.
I imagine that something went wrong upgrading Samba although the rest works, the daemons are running, kerberos works (kinit, klist), and so on, I only miss the net command.
Is there a way to install that separately or which package do I have to reinstall (samba-common, sambafs, ...)?
I have other servers (clean install and upgrade from Lenny to Squeeze) that do have the command in /usr/bin. Can I just copy it over from one to another or do I have to remove and reinstall Samba all together?
"My network" is behind a firewall inside a larger windows network with AD. My network has a Debian Server with samba 3.2 running. One of the hosts that are on the outside of my firewall has a share that I and other Linux-users on the debian server wants to access.
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 run a mediaserver on Archlinux, working perfectly (or almost). I have set up NFS v3 and that worked for me on these clients:
- Debian Lenny - Archlinux 64bit
Now I've upgraded my Lenny-box to squeeze and I see that 2 of my 3 shared folders (tdone and twatch) are mounted like they should and the third one (media) doesn't come up. A 'mount -a' as root gives this error: mount.nfs4: access denied by server while mounting (null) My relevant fstab-lines:
I am using Squessze and Gnome. When I try to use the gui System>Administration>Network or Users and Groups I get the error The configuration could not be loaded. You are not allowed to access the system configuration.Everything was working before. I read around a bit. In some cases,it was caused by mismatching group and password files after using the gui. I do not know how to check if they are matching. Of course I do not know for sure that is the problem in my case.
I had set up as a NT4 style PDC. There is no longer any PDC/BDC dynamic with Samba4 and MS AD support.
I purged samba packages and winbind et al and provisioned the domain correctly, and everything works well now.
What follows is the original post.
========================================================================================== After much struggling with DNS settings, I finally got a basic samba AD controller up and running, and then that's about as far as I got.
As soon as I tried to use the RSAT I found that I could not connect RSAT to the AD server while logged in as root.
The error I get is:
Naming information cannot be located because: The specified domain either does not exist or could not be contacted. Contact your system adminsiotrator to verify that your domain is properly configured and is currently online.
i am running centOS 5.5 with samba 3.3.8 I have enabled wins to see if i can get my windows workstation to be able to browse for the samba server and also be able to ping by hostname. I don't know if i have missed something in the config but I was going to upgrade to see if its an issue with 3.3.8.
if an upgrade is the solution can someone give me a how to on the upgrade. I used yum install samba3 to install it and found a how to to install 3.5 but the how to said i need to in all them ./configure command as the original install and it should install over 3.3.8. I don't know how to find that because i used yum.
I'm new with Samba and have access problem with Samba on Rhel 5. I want to share iso directory, and user admin can read and write while user bill can read only. smb.conf file looks like this#======================= Global Settings =====================================
I'm setting up a LAMP production server for the first time. When I installed Ubuntu server edition, I selected to install Samba. My idea was to be able to easily access the server's files on the LAN using Windows. All was well and I could ping/ssh between Windows and the Ubuntu server without any problems using the host names. Later, I became concerned that running Samba on a production server might introduce security issues. Therefore, I used apt to purge Samba.
Now I am unable to ping/ssh between the Windows machines and the server using the host names. It only works if I use the IP address.
1.) Is it a security risk to run Samba on a production LAMP server?
2.) How do I get back to being able to use host names without installing Samba?
This is my first post. I am not all that new to Linux. I have done lots of reading on the OS but always felt a little timid when it came to trying out stuff.Here is my problem I have a stand alone samba server I am trying to setup to share all my digital photos and other doc. I can see the share from other machines. On the windows machines you can see the users home directory and the share itself in an folder icon. Whenever I try to access the share it asks for a passwd. I enter the passwd and the share folder is visible when I click on the folder I get and error message.
I'm planning to use a virtual CentOS box for web development (to use the same software as on the real server). I configured Samba to have root guest access to /var/www/ but it doesn't let me in /var. Chmod 777 doesn't help. Nethertheless, I have full access to /sbin and /etc.
The problem I am facing is, with the Samba server configuration.I have configured Samba server with a folder shared between server and client machines. I have tried downloading data from the shared folder on the server to the client machine which is successfully downloaded, however I am not able to upload any data to the shared folder in the samba server.
I'm running sid, reasonably updated. I decided to add a samba share. I installed samba (2:3.4.8~dfsg-2), samba-tools, smbclient, smbfs, & samba-client. I did a "/etc/init.d/samba start" and even rebooted. But when I try to add a samba password for my regular user I can't.
# smbpasswd -a praxis bash: smbpasswd: command not found I did a "locate smbpasswd" but I'm only seeing:
I'm using Xfce 4.8, which now provides built-in samba browing in thunar. This works like a charm. I can browse a samba share (external HD connecter to router via USB). Yet it appears to me now that the support is limited to thunar. I mean double clicking on a file allows me to open/edit that file if and only if the software itself has samba support. In practice, double-clicking on a movie opens it with vlc thanks to vlc's own smb support. Even then, I can't find a way to add the subtitle file. I reckon that to use the share transparently, I would need to mount it the "mount" way. Either on a mount point like /mnt/hard_drive or something like .gvfs/hard_drive.
Is my understanding correct ? Is that my only option? Considering the disk won't be switched on at startup, fstab is not the solution. Would gigolo be the right choice? I spent some time trying gigolo a few days ago, following an easy tuto found on the web and it didn't work as expected. If needed I could give it another try.
I upgraded the samba on Ubuntu Server 8.04 to 3.5.2 so Windows 7 would be able to log into the domain. Now Samba isn't using ACL permissions and I can't alter the ACL with the Windows security dialog. All the permissions still show correctly on the server. Did something change with Samba 3.5.2? How to get the ACL to work with Samba 3.4.3 or newer?
I have a perfectly functional Samba file and print server. I will be adding several Window 2008 servers to serve as terminal server hosts running in virtual machines. I would like to convert my Samba server to a PDC (Primary Domain Controller) for these terminal servers to use. And leave everyone else as a work group (the current situation). I'd like to
1) use /etc/password and /etc/samba/smbpasswd as the source of the user accounts
2) limit what users the terminal servers can see based on a particular group (/etc/group)
So far I have tried the example howto's on the samba site and wound up having to restore /etc/nsswitch.conf in rescue mode.