similar to: 2.0.6 and FreeBSD 3.3-RELEASE + socket options = 2.5MB/sec

Synopsis: samba 2.0.6 running under FreeBSD 3.3-RELEASE is much faster than the same running under FreeBSD 3.4-RELEASE, even after replacing the 3.4-RELEASE kernel with the 3.4-STABLE kernel. (This has been reported to FreeBSD GNATS as "kern/16605") I have 2.0.6 running under FreeBSD using the following smb.conf: [global] workgroup = <NT Domain> server string =

I've now tried 2.0.6pre2 with a SuperMicro P6DNF dual PPro as well as the Everex StepDP/Pro dual PPro MB; same result, large (more than 1 MB) file copies usually crash with only a message about oplock errors in the logfile. Running a single CPU kernel works fine (pre2 seems much faster, but I haven't done any testing). 2.0.5a does the same. NFS and mars_nwe with the same hardware and

> > >Number: 16605 > >Category: kern > >Synopsis: samba 2.0.6 under 3.4-RELEASE can't open buffers Currently running 3.4-20000214-STABLE. Compiled samba 2.0.6 from /usr/ports; smbpasswd dies with a segmentation error but appears to complete writing the server SID and smbpasswd file (NT domain authentication works). Tried complete uninstall,

Using the patches from -current (aa thorugh bb) samba 2.0.6 release compiles under FreeBSD 3.3-RELEASE. "patch-ba" needs to be edited to change the location of the lines patched, and "patch-bb" needs to be edited to remove the first part (no longer needed) and also change the line location for the remaining part. Throughput using an NT4 SP6 P6/200 client connected at 100Mbits

2.0.6pre3 compiles and installs under FreeBSD 3.2-RELEASE; however, throughput from an NT 4 SP6 workstation with domain security and only TCP_NODELAY as a socket option is clocking around 200K/sec for large files (65MB). Hardware is PPro200, single CPU kernel (never have gotten 2.0.5 or later to work SMP), Adaptec 2944UW/3 Quantum 9GB Atlas II wide diff drives (clock 9MB/sec using bonnie), Intel

This is an automated email from the git hooks/post-receive script. arrfab pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new cd66094 Updated/Removed/Added sponsors to reflect actual list cd66094 is described below commit cd660941183914fe0e97c622fb0ec03828d4a0db Author: Fabian Arrotin <arrfab at

This is an automated email from the git hooks/post-receive script. arrfab pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new 567cac3 Removed sponsor from list 567cac3 is described below commit 567cac31956a9e97af492d089db91d0716e99614 Author: Fabian Arrotin <arrfab at centos.org> AuthorDate: Wed

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Buffer overflow in mars_nwe Advisory ID: RHSA-1999:037-01 Issue date: 1999-09-13 Updated on: Keywords: mars_nwe buffer Cross references: --------------------------------------------------------------------- 1. Topic: There are several buffer overruns in the mars_nwe

Hi there, we've got the following problem, while Windows-Clients works with samba and a DOS-Client connects over Mars_NWE to the same Linux-Server: When the DOS-Client opens a file on the linux-server and the WinClient opens the same file, and when both clients want to write the same file, the windows-client gets an error and crashes. We tried it only with the windows-clients and there

Hi at all . 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 to open from an other i have a Exxcel

One of our group companies has just 'gone live' on a new laboratory management package. Although the software is M$-based (ie: expects a M$ server at the heart of it), it is running with its core database on a CentOS3 server using Samba for client access - in fact, the developers are amazed at the performance and say it beats a Win2K/2K3 server 'hands down'!!! Anyway, the old lab

Dear Samba team & other readers, I'm a satisfied user using Samba as a file server for Windows based networks and I'm primarily using FreeBSD for this purpose. When I started to use Samba about half a year ago, I was upset about the lousy performance but tried my best to search for that problem at myself. The machine at this time as a Pentium/200 PC with some SCSI harddisks and 64

I have an Everex laptop (ick, but it was super cheap) that has an Atheros wireless NIC in it, but I can't seem to get it to connect to my wireless in-home LAN. Here's what I've done so far (that isn't working) - any suggestions? [root at marktop mark]# lspci | grep Ether 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c) 05:01.0 Ethernet controller:

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied

Greetings ... > Has anyone ever got command line only Windows 95 DOS to connect to a Samba > machine? I can connect to an NT machine no problem using "net use ...", but > the only machine the DOS machine will see on the network is the NT machine; > all of the others, including my Linux machines and a Win 2k machine, it just > refuses to see. First, any program you

FWIW, i had the same problem (obtaining a byte-range lock with an offset of 0xeffffff0..0xefffffff) quite some time ago causing dBase IV on DOS machines with VLM clients to a mars_nwe server to fail to synchronize. The solution was probably the same as here, to fold this range into 0x7ffffffx. -- Morio Taneda admin,sociology,humanities,karlsruhe university,germany

Hi folks, I've ran many circles about this topic, read tons of documents. But have not found a working solution. Here is the scenario: There is a network contains around 350+ nodes, mixed Win98 and Win2k. There are four mars_nwe servers they use. We'd like to migrate that 4 servers into an AFS cell and offer it thru Samba which should be acting as a PDC. So far it seems not too

Hi We are using a Debian 1.3.1 server (two Ethernet-Cards) with 18 Clients. The Clients remote-boot from the server using mars_nwe(Novell-Server emulation). Under Windows (WfW 3.11) the Clients user the Microsoft 32-bit Tcp-Stack to access the samba-server( 1.9.18p7). The problem is that the clients can't see the samba-server in their browse-lists, nor can they access the server with net

https://bugs.freedesktop.org/show_bug.cgi?id=27720 Summary: Hard Hang on suspend - 8600M GS Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

> 1) RE: Windows 2000 > by "Alex Yu" <yua@artlover.com> 2.0.6 when compiled with crypt support (FreeBSD 3.4-STABLE) is working fine with encrypted passwords where the FreeBSD host is a domain member and I'm athenticating against the domain PDC. I had to update to 3.4-STABLE from 3.4-RELEASE to get speeds up to something similar to 3.3-RELEASE, and as of the 2/14