similar to: Win NT Authorization problems...

Given that I only have 10 client machines which could access Samba (v1.9.18p3), does it make any sense increase the "interface" mask to reduce the number of addresses broadcasted to? That is, would a parameter of interface = 192.168.0.1/28 be less of a burden on Samba that the standard 8-bit interface = 192.168.0.1/24 range of broadcast addresses? Thank you. *****

I have a few DOS and Win95 PC's connecting to our Linux 2.0.33 server running Samba v1.9.18p3. This weekend, I am installing a WinNT workstation on the LAN. I can't for the life of me connect the NT station to any of the SAMBA services. It keeps telling me I have the wrong username/password. My setup: Windows NT Workstation SP3 (with the registry set to disable encrypted passwords).

The Samba Team are pleased to announce Samba 1.9.18alpha13. This code release is very close to what we hope will become the 1.9.18 official release. Because of this, we would encourage as many people as possible to download and test this new release on their particular systems, in order to ensure as stable an official release as possible. Please bear in mind that this is still an alpha

Hi, On Mon, 11 Aug 2003, Kent Hauser wrote: > Hi Mike, > > Had any progress? I've also by stymied for a clean solution. Previously, I > used a simple SED script from executed from "/etc/ppp/ppp.linkup" to edit a > "setkeys" script which then negotiated with the office ascend router/gw & all > was VPN heaven. However, I now need to negotiate

Wether the dlm_lock needs to access lvb or not depends on dlm_lock_resource it belongs to. So a new parameter "struct dlm_lock_resource *res" is added to dlm_new_lock() so that we can know if we need to allocate lvb for the dlm_lock. And we have to make the lockres availale for calling dlm_new_lock(). Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> ---

The Samba Team are pleased to announce Samba 1.9.17p5. This is a patch release designed to fix the few bugs that users had reported with our last stable release, 1.9.17p4. This release adds no new functionality, and if you were not impacted by the bugs then there is no need to upgrade from 1.9.17p4. Note however, that *all* users should upgrade to at least Samba version 1.9.17p2 due to a

I am having some issues with Samba and Outlook... We just upgraded from 1.9.17 to 1.9.18 and now we seem to have some severe slow downs in using Outlook. The mailbox.pst files are stored in everyones home directories that are located on a linux share. Before when people searched for a name it would take no time. Now it acts like on every search that anyone does or opening of a calendar, etc. it is

The Samba Team are pleased to announce Samba 1.9.18p1. It may be fetched via ftp from : ftp://samba.anu.edu.au/pub/samba/samba-1.9.18p1.tar.gz This is a bugfix release, designed to address issues that users have reported with the 1.9.18 major release. Due to an oplock problem in 1.9.18 (fixed in this release) that could cause data loss in certain circumstances, it is recommended that all

Hi, We've been over this before many times, I think... it's about nmbd crashing in 1.9.17 (all patchlevels, AFAIK). Various suggestions have been suggested (cron jobs to kill off / restart nmbd every hour) but no fixes to nmbd itself (I think). Do the Samba team know of a fix (or could they do one; if they know what the problem is)? A new [fast] machine added to our network recently

> I have a few questions regarding this; > 1) Is the Windows SMB encryption approved for for export, a' la ITAR? > 2) If not, is WinNT40SP3 available outside the US/CA. > 3) Relative to 2), is this version of RedHat available outside US/CA? > 4) How does MS distribute SP3 outside US/CA? Here are some facts that I think will make it all clear: 1) All MS clients/servers have

Stephen L Arnold wrote: > > When the world was young, samba@samba.anu.edu.au carved some runes > like this: > > > Date: Thu, 13 Aug 1998 10:57:52 -0700 > > From: "Gil Salazar" <gsalazar@ag.arizona.edu> > > Subject: Win 98 problem > > > I have just upgraded to win98, andnow my samba shares wont recognize my > > passwords.. Anyone else

I've been handed a server environment with samba serving a 1.5 terabyte SAN mount, and find connections to the mount slow. Any attempt to read the filesystem remotely results in a 5-10 second lag before responding. Once the initial lag has passed, the filesystem can be read in a reasonable responsive manner. I'm not sure where to look to identify the problem. It's possible using

The Samba Team are pleased to announce Samba 1.9.18p4. It may be fetched via ftp from : ftp://samba.anu.edu.au/pub/samba/samba-1.9.18p4.tar.gz This is a bugfix release, designed to address issues that users have reported with the 1.9.18p3 release. There is some new functionality, described below. Password Changing. ------------------ Samba now supports Windows 95 clients changing both their

hey all, I'm just getting used to R and i'm having issues when it comes to reading my data in rows rather than columns. any good advice would be much appreciated ! here is the error: > data1 <- read.table(file.choose(),header=T) > x1 <- c(data1[1,1:5]) > shapiro.test(x1) Error in sort.int(x, na.last = na.last, decreasing = decreasing, ...) : 'x' must be atomic

I have a server running Red Hat Linux 5.2 with samba 1.9.18 installed (at least that's the rpm package). The server itself is mounting and sharing two SCSI cdrom drives - the kind that are capable of changing up to six cdroms each. The OS mounts the drives correctly. I can see the files. I have shared the drive contents and can map access to them over a Win95 network. I have set the

Hello, I have tried to compile openssh-3.1p1 and then two later snapshots. It seems that I can not have support for KTH-Krb4, according to this errorlist from make: gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o readconf.o clientloop.o -L. -Lopenbsd-compat/ -R/usr/local/ssl/lib -L/usr/local/ssl/lib -L/usr/local/lib -R/usr/local/lib -L/usr/athena/lib -R/usr/athena/lib -lssh

The Samba Team are pleased to announce Samba 1.9.18p7. It may be fetched via ftp from : ftp://samba.anu.edu.au/pub/samba/samba-1.9.18p7.tar.gz This release is a security patch fix for a security hole reported on BugTraq by Drago. No exploit code was published with the report, so no immediate 'canned' exploit was available to an attacker The security hole may have allowed

I have somehow managed to set SAMBA up so that I can't read my shares (none of them). I can browse them and write files to them, but I can't open them! There is also another user on the network, for which the Samba shares behaves in the exact same way. I would have thought that this behaviour was impossible to get! Thank you for your time! My smb.conf: [global] # workgroup =

Hi, guys! I am using internet via a proxy. When samba is not running, there is no problem, but when I start samba, there is no internet (although there is a ping to the proxy) and whenever I try to open a site, the message "Unauthorized..." appears in the browser. I am currently using Slackware 10.1, kernel 2.4, samba version 3.0.7 (but it was the same on Gentoo. Surprisingly, samba

A big hello to the list! I've installed since two years and since version 1.9.17 a Samba Server on a Linux Box running Slakware 3.0 with kernel patched up to 2.0.34. This box runs on the same network as a Netware 4.01 server and a NT server. All the clients are Windoze95 and, unfortunately, now there are some Windoze98 systems as well. I'm saying unfortunately because up to now