search for: smb_nobody

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.

...ourrier.com'" <r_ducomun@netcourrier.com>, > >I saw a msg that reminded me of something: >it may be the initial IPC$ connection that is >being denied. That's for the Guest user, I think. >Guest is the Win2k equivalent of Everybody. > >I created a user called smb_nobody, no login allowed >(can't use the account to hack in via a shell) >you can skip this and use the user ftp, as others do. > >in smbusers, mapped nobody=smb_nobody >or nobody=ftp, if you use the user ftp > >in smb.conf: >map to guest=Bad User >guest account=smb_nobody &...

...INVALID_PARAMETER Join to domain 'MYDOMAIN' is not valid: NT_STATUS_INVALID_PARAMETER root at mynas:/# The \\netlogon share on the PDC is open to guest access. log files on the PDC show 192.168.x.x (192.168.x.x ) connect to service IPC$ initially as user smb_nobody (uid=90001, gid=90001) (pid 19408) ... [2016/05/11 11:46:22.733380, 2] passdb/pdb_ldap.c:553(init_sam_from_ldap) init_sam_from_ldap: Entry found for user: MYNAS$ [2016/05/11 11:46:22.738212, 2] passdb/pdb_ldap.c:2427(init_group_from_ldap) init_group_from_ldap: Entry found for group: 515...

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

...VALID_PARAMETER >> root at mynas:/# >> >> >> >> The \\netlogon share on the PDC is open to guest access. >> >> >> log files on the PDC show >> >> 192.168.x.x (192.168.x.x ) connect to service IPC$ initially as user >> smb_nobody (uid=90001, gid=90001) (pid 19408) >> >> ... >> >> [2016/05/11 11:46:22.733380, 2] passdb/pdb_ldap.c:553(init_sam_from_ldap) >> init_sam_from_ldap: Entry found for user: MYNAS$ >> [2016/05/11 11:46:22.738212, 2] >> passdb/pdb_ldap.c:2427(init_group_fro...

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 =

...;MYDOMAIN' is not valid: > NT_STATUS_INVALID_PARAMETER > root at mynas:/# > > > > The \\netlogon share on the PDC is open to guest access. > > > log files on the PDC show > > 192.168.x.x (192.168.x.x ) connect to service IPC$ initially as user > smb_nobody (uid=90001, gid=90001) (pid 19408) > > ... > > [2016/05/11 11:46:22.733380, 2] passdb/pdb_ldap.c:553(init_sam_from_ldap) > init_sam_from_ldap: Entry found for user: MYNAS$ > [2016/05/11 11:46:22.738212, 2] > passdb/pdb_ldap.c:2427(init_group_from_ldap) > init_group_fro...

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,