search for: smb_nobodi

I've discovered a couple of things while troubleshooting my printer setup problems. 1. print$ must be 0744. I ran a level-3 debug, and was seeing "chmod failed" errors. Upping it to level-10, I saw something that pointed to unix rights of 0744; my dir's were set to 0755 or 0777...neither worked. When I set print$ and it's subdir's to 0744, the chmod errors went away.

Ok, I solved the problem by myself. The problem was that the users with wich I tried to connect to the printer where defined as admin users, and I declared root as an invalid user in the samba configuration, so it always give me an access denied because it tried to connect as root. Anyway thanks for the time you waste trying to help me ;-) ----Message r?exp?di?---- >Date: Thu, 27 Jun 2002

I have a Synology NAS array appliance. It is linux based and uses samba for file sharing. Normally the config is done via a gui interface but you can ssh to the array. The domain controllers are running Samba 3.6.x in classic domain mode. I have member servers running 3.6.x and 4.3.8. no problem. I recently updated the Synology "OS." The current version of samba is

Desperate to find out why connecting to a samba share(on an AIX server) from W2K is so slow, I tried connecting to the same share from a Linux box, using smbclient: smbclient \\\\aixserver\\sharedir$ -U lynn The results were amazing. The connection was so MUCH FASTER then connecting from a W2K (pro) workstation: \\aixserver\sharedir$ (in the Start|Run edit box) When I examined the samba log

I'm looking for confirmation that what I am about to do will work. My intent is to decommission the existing Samba PDC hardware and put in its place the new hardware. I intend on having the users see no difference, in terms of what they have/had and will continue to have available. Right now I will be copying everything from the /etc/samba directory into the same on the new server, moving

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although

I'm currently having a problem with the new released Samba 2.2.5: I cannot print anymore on my shared printer. What is strange is that It worked fine with samba 2.2.4, but now I got an access denied whenever I try to access the printer... /var/spool/lpd/samba is chmod 777 and the username is in the group lp Here is part of my smb.conf: [global] workgroup = HOME netbios name =

Hi, I am not sure it's the same issue, but I had a similar problem when upgrading from DSM 5.x to 6.0 : error after domain join : "Connection failed. Please check your network settings" . With the help of the (very efficient) Synology support, we solved the problem by uninstalling an old Cluster HA DSM package that was installed on the NAS but not used. Just in case it could help.

I am upgrading from 3.0.37 to 3.5.9 on the same server and need some advice. I am running Solaris 10 on a domain server that services 10 XP and Win 7 clients. The existing Samba directory structure is not standard. I believe the engineer who built the Solaris install transferred all Samba 2.0 directories from the old server to the current server and then created additional directories for the

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise

I have been having a printing problem recently on a setup that has worked for quite some time. Configs below. The symtoms are slightly different on a W2K and a WinME workstation, but the result is the same; no printed output. However, when I print from the local Unix server or from any other Unix server in the network the output is as expected. The W2K machine reports 'Access denied,