similar to: SAMBA digest 2391 / Samba 2.0.6 on SCO Unix 5.0.5

We seem to be experiencing some problems with Samba 2.0.6 on SCO Unix Openserver 5.0.5. I'm wondering if anybody else is using this version of Samba on SCO. I used an older version 3 years ago and rarely had a problem. I just installed this version and am experiencing an annoying problem: We use windows 95, 98 and NT4.0 (SP3/SP6) workstations. All passwords are set to clear text. The samba

Hi, Frankly spoken you have a real RTFM problem. The manual pages for smb.conf say that "create mask" and "create mode" are equal. It also says that there is only a "force XXXX mode" (where XXXX is either create or directory). So a replacement of mask with mode will do the thing. The other mistake is that there is no "force create group" parameter. The

Hello Brian, There is a very annoying problem with UNIX systems and network printing. On nearly all SYSV systems the spooler stores only the address of the (temporarily) print file. This does not cause any problem if it is created by a local application. If the temporarily print file was created via a network application (Samba, NFS, etc.) it will be removed shortly afterwards. In the most

Jens Rieck wrote: >>Can anyone help me? >> >>I have Samba 2.0.5a running on SuSE Linux 6.0 (2.0.36) and >>Windows NT Server 4.0 SP4 (PDC). >> >>When I try to do a "smbclient -L MYUNIX" (according to the trouble >>shooting guide) I get the following message: >> >>Addes interface ip=195.90.254.xxx bcast=195.90.254.255

I have problems with one Windows NT. I installed Samba 2.0.2, but that did not helped. Kari Hurtta wrote: >Actually situation gone worst. Adding > nt support = no >halped somewhat (new problems seems disappeared). >That new errors was that printing try caused >that NT reported about IO-errors. >I just want indicate that special nt support >code perhaps have some

Hello, I have a strange problem with Samba 2.04b and M$ Outlook97 on NT 4.0 SP4. I am using a SCO OpenServer 5.04 system as mailserver (POP3) and nameserver as well as Samba Server. For backup reasons I have installed Outlook in such a way that its own mail file (postfach.pst) is on the Samba share. If the NT box and Outlook are freshly started I can retrieve mails from the POP3 or send

Massimo Lambertini wrote: >I have a big problem . >I'he upgrade my Server from ( Linux 2.0.36 and Samba 1.19 ) to >Linux 2.2.7 and Samba 2.0.3 ( redhat 6.0 ). >I have used the same smb.conf but the systen do not work the same . >I have a linux directory shared by 10 users with M$ Office 97 . >With Old System ( Samba 1.19) when i open a file from one client if i >try

We are experiencing problems with Adobe Photoshop and Samba, all versions up to 2.0.6. We run Samba off Compaq Alphaservers (ie 64 bit). Symptoms: 1) On doing a "Save As" in Photoshop, we intermittently get: "Could not save as F:\<filename> because the file is already in use or was left open". A zero length file is left on the Samba share. 2) Problem only

Why is www.secnet.com down ? i'm looking for the samba-audit-tool and didn't find any mirror. Thomas On Fri, 30 Apr 1999 samba@samba.org wrote: > SAMBA Digest 2073 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) Group-Shares > by Johannes Scherbaum <scherj@funkhaus.de> >

Hello, I am trying to run SCO unix 5.0.5 with KVM. I have created the Virtual Machine with virt-manager. The installation runs correctly, but when the virtual machine reboots from hard disk, i obtain this message : "FATAL: No bootable device." If i run manually the virtual machine without the suboption "boot=on" in the "-drive" option, the virtual machine boots

James A. Mutter wrote: >Does anyone know of any issues with 2.0.5 and SCO Openserver 5.0.5? A >friend told me that he had "real problems", but couldn't elaborate. >Is there something I should be aware of before I try this? >Thanks, >Jim Hi, As far as I know there are no problems with running Samba on a SCO system, beside the normal Samba configuration problems.

Hi folks, I'm trying to install OpenSSH 2.3.0 on a SCO OpenServer Release 3.2 v.5.0.5 box. I downloaded the tarball from the 'portable' directory and uncompressed. ./configure --with-egd-pool=/dev/random <-- works with no errors. Output attached here: (See attached file: output.txt) make displays: root:/tmp/OpenSSH/openssh-2.3.0p1 # make cc -g -I. -I.

These issues affected previous 2. versions of openssh and still affects openssh-2.1.1p1. The environment is SCO OS 5.0.5 with the SCO development environment (not gcc, gmake, etc.) There are two issues, the first is a compilation problem, and the second is a run-time problem. The first problem is simply that MAXPATHLEN is not defined. I found it to be defined in

Ok assuming I don't want to record calls using * but instead want a dedicated server that listens to a mirror port and records calls. Is there a cheap software package out there for doing this for mgcp/sccp? I know if evern cut over to * there is a way but I doubt I will even cut 100% over to * so I was wonder what the list has heard of for call recording via sniffing my gates. I know there

Hi, I've just installed a binary version of Samba 2.0.3 on SCO 5.0.5 and am having some problems. I'm basically following "SAMS Teach yourself Samba in 24 hrs" book. On a Win98 machine I can see the SCO machine in the Network Neighborhood. When I try to connect it asks for a passwd and says that the passwd is incorrect when I enter it. It also displays

I downloaded openssh-2.5.1p1 as soon as it was on the ftp servers just to get the setluid patch. After compiling and installing on 5.0.5 I saw that the luid still wasn't being set correctly whether sshd was run from inetd or as a daemon from /etc/rc2.d/. I fiddled around and moved the setluid() stuff up higher in session.c and now luid is now being set correctly. I provided a regular diff

Hi folks, just I installed openssh 2.1.1p4 on a sco OpenServer 5.0.5 machine and it works fine. The only problem I have is the X11 forwarding. I have allowed this feature in the /etc/sshd_config and the /etc/ssh_config, respectively and the /usr/bin/X11/xauth program was in the PATH during compilation. As you can see in the logfile the sco system enables the X11 forwarding and sets the DISPLAY

Ok, using openssh-SNAP-20010126.tar.gz, two versions of the server both compiled with the configure commands as below, one with USE_PIPES defined and one without. This is on SCO OpenServer 5.0.5 (using SCO dev environment, SCO make, etc.) The client is always linux, openssh 2.3.0p1. export CCFLAGS='-L/usr/local/lib -I/usr/local/include' ./configure --sysconfdir=/etc/ssh

Trying to compile openssh-3.1p1 on SCO using: export CCFLAGS='-L/usr/local/lib -I/usr/local/include' ./configure --sysconfdir=/etc/ssh --with-rsh=/usr/bin/rcmd --exec-prefix=/usr OpenSSH has been configured with the following options: User binaries: /usr/bin System binaries: /usr/sbin Configuration files: /etc/ssh Askpass

Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store