search for: pedaa

In the course of tracking down a problem in Samba v2.0.4a, I set "debuglevel=3" and noticed something strange in the log file. While attempting to find the netlogon script, a number of variations on the name are tried (e.g. for Windows, it's *.COM, *.EXE, *.BAT). Here's the strangeness: the file NETLOGON"BAT is also looked for. Yes, that's a quotation mark in place

I took a look at the pid file generated after starting winbindd in the background (redhat's "daemon" shell function in the startup script). It looks like the pid reported in the file is wrong, unless I start winbindd in the foreground. My klooge in the startup file follows: WBPID=$(/sbin/pidof winbindd) ps $WBPID && { if [ $(cat $RUNDIR/winbindd.pid) -ne $WBPID ]

Hi everyone: I'll try to be both succinct and accurate here: Attempting to get a directory listing from a DFS export fails using "Samba 3.0", but works fine on windows (XP, 2K, NT4). This happens via smbclient and via "smbmount"ed directories. I had no problem joining this domain, and the user that I am connecting as has permissions to open these folders (I checked

Hi everyone: I'd appreciate any help here... Using smbclient I can change into a directory within a DFS share, but when I attempt to list it's contents, I receive the subject error. I can view the directory (folder) from a win client using the same credentials. I already posted much of my configuration, sans the "smb.conf", although if anyone suspects that there are

Hi: I had a problem joining a (red hat 8) machine (client) to our campus wide domain. Unfortunately I am in the dark as to many of the details of this network design here. So I am trying to back out some details. One machine had no problem joining the domain. Both are almost identically set up (compiled samba 3.0.2a). The other resisted a sucessful join until I added "-S" to the net

Hi: I recently encountered a problem reading directories via an XP Pro client shared from a samba server (redhat's rpm samba-2.2.7-5.8.0). File listing was sometimes VERRRY slow. It was not a DNS issue in this case. The symptoms, and my fix is below, but I wanted to ask, is there a way to deal with this from the server? (I dunno- like redirecting port 80 or something). >From the client,