similar to: No subject

Hi Guys, Has anyone come across or heard tale of a problem whereby you have a Samba share where you can't see certain directories in the root of the share?

This is the final results of sftp on SCO OpenServer. ---------- Forwarded message ---------- Date: Mon, 26 Feb 2001 12:27:51 -0700 From: Greg Jewell <gjewell at cnnxn.com> To: mouring at etoh.eviladmin.org Subject: RE: Problems with sftp under SCO OpenServer > -----Original Message----- > From: mouring at etoh.eviladmin.org [mailto:mouring at etoh.eviladmin.org] > Sent: Monday,

On Wed, Sep 12, 2018 at 03:27:37PM -0500, Kevin R. Bulgrien via samba wrote: > Looking back in the samba mailing list archives, I see not soancient requests > for samba on ancient SCO OpenServer systems. > > Recently faced with a situation where a Windows Server upgrade to 2012 R2 and > broke an smbclient upload from a SCO OpenServer 5.0.7 system. Directory > listings and file

I think what I need is a prebuilt package. I currently use Samba 2.2.12 running on SCO OpenServer 5.0.6 but I am in the process of upgrading to 5.0.7. Can't move to SCO version 6 because our application isn't guaranteed to work on it. Regards Dave -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Mauricio Tavares

On 09/12/18 16:56, Jeremy Allison via samba wrote: > On Wed, Sep 12, 2018 at 03:27:37PM -0500, Kevin R. Bulgrien via samba wrote: >> Looking back in the samba mailing list archives, I see not soancient requests >> for samba on ancient SCO OpenServer systems. >> >> Recently faced with a situation where a Windows Server upgrade to 2012 R2 and >> broke an smbclient

I never have had a problem compiling Samba until 2.2.2 after installing a SCO patch 506a on OpenServer 5.0.6. I noticed the following message when running configure that does not normally appear: WARNING: No automated network interface determination make output: Using FLAGS = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -DLOGFILEBASE ="/usr/local/samba/var"

If you upgrade to sco 5.0.7, you get samba 3.0.20 5.0.6 had samba 3.0.14. so im wondering why your using samba 2.2.. samba 3.0x. is on the supplimental discs. Gr. Louis >-----Oorspronkelijk bericht----- >Van: dave at anchor-tech.co.uk >[mailto:samba-bounces at lists.samba.org] Namens David Nolan >Verzonden: vrijdag 22 mei 2015 14:12 >Aan: 'Mauricio Tavares' >CC:

On Fri, May 22, 2015 at 8:31 AM, L.P.H. van Belle <belle at bazuin.nl> wrote: > If you upgrade to sco 5.0.7, you get samba 3.0.20 > 5.0.6 had samba 3.0.14. so im wondering why your using samba 2.2.. > samba 3.0x. is on the supplimental discs. > > Gr. > > Louis Been there, done that. Samba 2.2 was built into the base release, supplements weren't always stable or well

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.

You can download Ncurses for SCO OpenServer via ftp://ftp2.caldera.com/pub/skunkware/osr5/vols/ncurses-4.2-VOLS.tar This is a tar archive of media images suitable for installation with the SCO Software Manager (/etc/custom). Cheers, Ron Record rr@sco.com re: > Date: Wed, 26 Feb 2003 15:54:59 +0000 > From: Simon Hobson <shobson-lists@colony.com> > To: samba@lists.samba.org >

----------------------------------- Has anyone been able to compile a working version of Samba using the native compiler on SCO Openserver 5.0? The compile completes successfully. But I get the following on smbclient: #------------------------------------- $ smbclient \\\\larry\\c number of interfaces returned is: 2 Impossible netmask 255.255.255.0 - using defaults error connecting to

I downloaded the Openssh-2.3.0p1 file and ran configure only to have it fail reporting the lack of libz. I found that configure was failing beacuse the test program did not include the libtinfo and libm which are needed to resolve references in libprot. I made changes to the configure script to add those libraries for SCO Openserver and then tried to compile the programs only to run into another

Yo Andrew! What version of Openssh are you trying? RGDS GARY On Mon, 12 Jun 2000, Andrew McGill wrote: > Date: Mon, 12 Jun 2000 15:26:53 +0200 > From: Andrew McGill <andrewm at datrix.co.za> > To: djm at ibs.com.au > Cc: gem at rellim.com > Subject: Openssh on SCO Openserver Release 5 > > Hi there > > Your e-mail address appears in the README for openssh,

Dears Sirs; I'm tryng to compile and install samba 3.0.14a on a SCO Openserver 5.0.6 server (i want to use some shared printers from MS server2003 on a customer network, but with samba SCO ver 2.2, i can't obtain the authorization from the domain controller to use shared resources), but i'm havig a lot of trouble. I had dowloaded samba-3.0.14a.tar.gz fro Samba.org. I had put all the

Hi all, I'm writing to you becuase I have compiled PAM in SCO (now Caldera) Openserver 5.0.x, and when I tried to use SSH with PAM enabled, y realized that OpenSSH depends on the user to exist en the /etc/passwd, and /etc/shadow databases, or equivalent ones (it uses getpw...() functions to determine validity of the user). In Linux, the simlpe solution is to use nsswitch, but it seems to hard

Looking back in the samba mailing list archives, I see not soancient requests for samba on ancient SCO OpenServer systems. Recently faced with a situation where a Windows Server upgrade to 2012 R2 and broke an smbclient upload from a SCO OpenServer 5.0.7 system. Directory listings and file deletions did not fail, but all upload attempts produced empty files on the Windows server (this due,

Denis Caron wrote: >>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

Greetings, I recently discovered a problem with OpenSSH 3.6.1p2 and UnixWare 7.1.1 (as well as OpenServer 5.0.X and SCO 3.2v4.2) When I set up sshd_config as follows: PasswordAuthentication no PermitEmptyPasswords yes and try to connect to a password less account ( I know its a F*up, but that's the application ID10Ts .... ) I can get in using the SSH2 version without a valid key, the

Openssh 4.4p1 and 4.5p1 SCO Openserver 6 w/mp1, mp2 While installing v4.5p1, I noticed this sshd syslog error which began appearing when I upgraded from v4.3p2 to v4.4p1: Sep 1 17:54:41 tenzing sshd[12837]: error: Bind to port 22 on :: failed: \ Network is unreachable. sshd -d reports: debug1: Bind to port 22 on ::. Bind to port 22 on :: failed: Network is unreachable. debug1: Bind

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