search for: joshkel

I'm trying to set up a new CentOS 4.2 desktop, and gdm refuses to start. It blanks the screen, displays the swirling blue circle mouse cursor that appears to be an hourglass equivalent, then drops back to the console window. It repeats this several times then displays the following error: The display server has been shut down about 6 times in the last 90 seconds, it is likely that something

I'm running Samba 3.0.21a (blastwave build) on Solaris 9. The Solaris servers have no printers attached or accessible, just file service. Samba users authenticate off a Win2003 AD controller and get printing from that. I got rid of the "Unable to connect to CUPS Server" errors by adding to smb.conf the line printing=bsd but I am still getting smbd[4809]: [ID 702911 daemon.error]

We upgraded from Samba 3.0.24 to 3.0.25a over the weekend and rebooted all of our clients afterwards. Since then, some of our clients are randomly getting the following error: "Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied." Unmapping and mapping the network drive fixes the problem, but one

I am using a Samba 3.0.21a share to centrally access my source code from multiple Windows workstations. Everything works as expected (in Samba), but there is a slight (but annoying) problem with the modification timestamp of the files on the Samba share. While I have verified that both server and workstation are synchronized to the same time (using NTP), it seems that there is a few milliseconds

The permissions are apparently set incorrectly on the vnc SRPM in the FastTrack repo on mirror; I get "permission denied" when I try to mirror it. Thanks. Josh Kelley

Is anyone using sk98lin Gigabit Ethernet adapters under CentOS 4.x? The version of the driver that ships with CentOS 4.x kernels was too old to support the onboard NICs on some Intel server boards that we recently got, so we installed a newer driver using DKMS. However, we're having problems finding a stable driver to use: the first version that we tried (7.09) gave a kernel panic when I ran

I'm having a very strange permissions problem with Samba 3.4.7 (installed via backports.org) running on Debian Lenny: If a Windows 7 or Windows Vista client tries to use Windows Explorer to access a user's home directory with permissions 0700, the client gets a permission denied error. If the directory is made world readable, it works. (For one user, group readable also works. For

Since upgrading from 3.0.24 to 3.0.25a this past weekend, network drive connections are randomly being closed and immediately reopened. This creates "Delayed write failed" errors for Firefox and Thunderbird, various errors for Outlook with its PST files on network drives, and errors from programs like InDesign that "The network connection was lost for the file, or the file was

...she is an IBM > Cleveland State University -Jeff Lynne > (216) 687-2214 > r.martel at csuohio.edu > *********************************************************************** > > > > ---------- Mensagem encaminhada ---------- > From: Josh Kelley <joshkel at gmail.com> > To: steve <steve at steve-ss.com> > Cc: "samba at lists.samba.org" <samba at lists.samba.org> > Date: Tue, 29 Jul 2014 16:50:08 -0400 > Subject: Re: [Samba] Winbind rid + SID History creating duplicate per-user > groups > On Tue, Jul 29, 20...

I'm in the process of setting up CentOS 4.3 on an old 400MHz K6 and found that the system hangs within several seconds of starting haldaemon. With haldaemon disabled, everything seems to work. >From what I've read, disabling haldaemon isn't a problem, but I thought I'd ask if anyone else has seen similar problems or if anyone had any troubleshooting tips. I found a similar

I'm setting up password complexity requirements on our Samba server, using the "check password script" option, the provided crackcheck.c program, and the "min password length" account policy. Everything works; however, the error message that a Windows client gets when a new password fails to pass crackcheck is not terribly helpful: "Your password must be at least 8

I'm seeing an oddity regarding ACLs. I have a user who wants others to be able to add stuff to her folder, but she wants to make sure that she has access by default to files added to her folder. The easiest way to do this, I thought, is to set the user's ACL to apply to this folder, subfolder, and files. (Right-click on the folder, choose Properties, click on Security, click Advanced,

Since upgrading to Samba 3.0.23a, mounting a Samba share using mount.cifs generates the following errors in the Samba server's logs: Aug 7 17:45:08 pccentos4 smbd[5345]: [2006/08/07 17:45:08, 0] libsmb/smb_signing.c:srv_check_incoming_message(720) Aug 7 17:45:08 pccentos4 smbd[5345]: srv_check_incoming_message: BAD SIG: seq 2 wanted SMB signature of Aug 7 17:45:08 pccentos4 smbd[5345]:

One of our users tried to change his password through Samba and was told that he was unable to do so. Samba logged the following error: user john.doe does not have permissions to change password I checked the Samba source code to see what this error meant, and I found that it meant that the "password can change" time was set to the maximum time allowed. However, when I ran pdbedit to

I periodically see smbfs questions get asked on this list, and they usually get one of two responses: 1. smbfs is a kernel module; this list is not the appropriate place to be asking smbfs questions. 2. You should be using cifs instead. (Please let me know if either if these is incorrect.) I was surprised to see, however, that the smbmount / mount.smbfs manpage makes no mention of cifs as being

I've had problems with nscd crashing every few days on my CentOS 4 mail server for a while now. The problems started maybe around CentOS 4.2, although I don't remember for sure. My debugging efforts let me to disable nscd's persistent cache, and that seemed to work for a while, but since upgrading to CentOS 4.4, the crashes have started again. When nscd crashes, the rest of the

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

We have a Linux user and group with the same name (username prox, group name prox) and a Samba share with "force user = prox" set. Since upgrading from Samba 3.0.21b to Samba 3.0.23a, that share no longer works. smbclient gives the following error when connecting to the share: tree connect failed: NT_STATUS_NO_SUCH_USER The Samba server logs the following error: [2006/08/07 09:38:26,

Since upgrading from Ubuntu 12.04 (Samba 3.6.3) to Ubuntu 14.04 (Samba 4.1.6), I've noticed some strange problems with our group mappings: First, each of our Active Directory users now has a corresponding group in Linux. I don't remember ever noticing this in Ubuntu 12.04 / Samba 3.6.3. Is this feature new? Is it documented anywhere? (I tried searching online and couldn't find

I'm having various problems accessing shares with dollar signs in their names (e.g., \\server\c$); however, there doesn't seem to be much consistency to the types of problems. Details: >From my CentOS 4.3 box running Samba 3.0.21b, mounting \\server\data$ (a Windows Server 2003 DC) or \\domain\data$ (the same share, shared over DFS) using mount.cifs doesn't give any errors, and I