Displaying 20 results from an estimated 200 matches similar to: "Slow write time to samba 2.0.5a from DOS"
2003 Jun 20
4
PXELINUX keeppxe mem footprint
Hi,
I want to use PXELINUX to load a DOS disk image which I currently use for
Win2K/XP unattended installs. I want to move away from reliance on specific
NDIS2 drivers and use the 3Com UNDIS3C driver instead. I have used this
successfully to start the MSClient, but the problem is that the UNDI and PXE
layer take about 90K of base memory, which means that WINNT.EXE has
insufficent memory to run
1999 Jun 14
1
msclient and Case
Hello Everyone,
I recently installed a MSCLIENT machine each time it writes to my samba
2.04b share it produces all uppercase filenames. Is the best way to handle
this with
"preserve case = yes/no" controls if new files are created with the case
that the client passes, or if they are forced to be the "default" case.
Default Yes.
"short preserve case = yes/no"
2002 Feb 25
1
Problems logging in with MSCLIENT.
I'm running Samba 2.2.3 with winbind for authentication. Much to my
surprise, I found I had a need to connect an MS-DOS system to the network.
I'm using MSCLIENT to do so. I can successfully log into the domain and map
drives on Windows NT servers, but I'm having trouble mapping Samba shares.
Examining the log shows that the DOS machine is apparently trying to connect
with a username
2003 Sep 25
1
Per-directory "create mask"?
Hi all
Please CC me any replies.
I am currently running samba 2.2.8a under Slackware 8.1 (kernel 2.4.18) to
provide fileserver services to a number of windows 2000 boxes via a single
"resources" share. One of the things stored in this share is a collection
of Protel libraries used in electronic circuit design.
The problem is that protel implements its own access control mechanism for
2002 Jun 21
1
Syslinux/isolinux: is this possible?
Hello Peter
I know very little (currently) about the BIOS interfaces/APIs available at
boot time except that most of them are buggy to some extent. However, I
have had an idea regarding another way to boot Linux and wanted to run it
past you.
As you'd be aware, many of the distributions now require multiple floppies
to hold their initial root fs to be used during installation. I was
2000 Jan 06
1
Wildcard '*.' matches inproper files (for SAMBA DOS clients)
Subject: Wildcard '*.' matches inproper files (for SAMBA DOS clients)
The problem does not appear when using W9x/NT clients.
Testing environment:
samba: 1.9.18p10i (compiled), 2.0.5a(binary distrib),
2.0.6(compiled) on Linux RedHat 6.0 and Solaris 2.5
smb.conf:
|
|[global]
| workgroup = WORKG
| server string = Samba %v
| encrypt passwords = Yes
| socket
2002 Aug 15
2
Samba Speed Problem
Hi..
Can anybody help me.. here is my problem:
I have a little LAN with a Samba Box (It's my PDC), and some DOS PCs,
running my core bussiness application (Foxpro 2.6)
All the Boxes are Intel 440BX2 whit Celeron 600MHZ, HD 10GB Maxtor 5400RMP,
64MB RAM and 3Com 905B Nic.
The DOS Box have MSDOS 6.22 with MSClient 3.0
everything it's Ok about the connection and autentication with
1999 Jul 31
0
Samba + Clipper problem!
Hi everyone,
Here is the problem:
I have a server running Red Hat 5.2 and Samba-2.0.4 as
file server for
about 20 diskless machines with MSClient boot disks (created with
NT
server SP3). The server shares a dir with a Clipper/DBF database
for
those clients and the EXE file is in a NT machine. For weeks I've
been
trying to put the things together but the clients always break
2000 Aug 23
0
Problem with smbclient->MSDOS Server
Hi All,
Here's an interesting one... I need to be able to connect smbclient on a
linux machine to a dos based machine, which is running MSCLIENT and the
WG1049 patch. I can browse to the machine and see all the files from
Network Neighbourhood in Windows, but if I try and go in with:
smbclient \\GAUGE1\C, or even just smbclient -L GAUGE1
all I get is:
Added interface ip=10.0.1.1
1998 Dec 03
2
Windows 3.1 and Samba
Has anybody got some experience with connecting machines running Windows3.1
or WfWG (3.11) to Samba? We would like to run a small lab network with
user accounts and a shared printer off the samba box. Samba is running fine
and there's no problem to connect to it from the Win95/WinNT machines...
Any help appreciated.
Frank Wornle,
Glasgow Caledonian University
Dept. of Engineering
2001 Nov 19
1
Slow writes from DOS client
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: Michael Stein.vcf
Type: application/octet-stream
Size: 455 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba/attachments/20011119/3a683333/MichaelStein.obj
2003 Oct 28
9
Using memdisk to remotely flash BIOS
I am using memdisk to remotely flash the BIOS and other firmware. It works well
for most flash programs. After the flash I need to initialize the NIC to send a
signal to my management server that the flash is complete.
I am curious as to how others have solved this problem.
Thanks.
1998 Jul 13
0
Making DOS Boot Disks for Samba
Thanks to several very helpful souls on this list we have been able to
replace ndis2 NIC drivers and boot successfully in DOS, map a Samba drive
... permitting us to use a DOS Ghost to build lab systems.
The guy who figured this stuff out last year has left the college and I
don't understand what protocols, or clients he used to support a DOS-Samba
connection. (I'ld be lost if I had to
2004 Nov 07
1
Network booting DOS with IPX support
Hi all,
I'm trying to work out how to boot DOS on a diskless PC, and I've come
to a bit of a stumbling block with loading IPX support (which is
extremely important, since most DOS games use IPX for network play ;-))
So far thanks to PXELinux and Memdisk I've gotten a DOS floppy image
booting successfully, but I'm stuck trying to get IPX support.
Admittedly I don't have much
2004 Nov 06
2
Upgrade from Hell
For those of you running SuSE 9.1, I do not recommend upgrading to 9.2
at this time.
Refer to http://shorewall.net/myfiles.htm for information on my
configuration:
a) On Ursa:
1) After the upgrade, both of the NICs were recognized as "configured"
in YAST yet neither of them would start; ifup claimed that no
configuration could be found for either interface. Only got them running
2013 May 16
5
ddos attack causes high ksoftirqd cpu use
Hello List!
I got a small (50mbits or so) application layer ddos attack against a
few name servers (thousands of IPs sending lots of bogus A record
requests - weird) - one of the name servers was behind a shorewall
firewall. That firewall was running a 2.6.18-194.11.1.el5 kernel and
shorewall-4.4.11.1-1. I noticed that the shorewall host had ksoftirqd
using 100% of the CPU during the
2004 Aug 06
4
icecast2 formats
I've been looking over icecast2 and notice that it's all ogg. Are there
plans for mp3 support in it, or will that be left to icecast1? I love ogg,
but still have a sizeable set of mp3's from before I found it. Is it
possible to have a stream of varying formats where songs could be either mp3
or ogg and the listening program uses the appropriate plugin/player to
handle decoding, or
1998 Apr 27
1
DOS-Client using SAMBA-Server
Hello,
I read some of your latest articles depending on DOS and Samba.
You always mentioned TCP/IP 32, LANMANAGER-Client from IBM and this
mysterios MS Client 3.0.
What I would like to know is, if there is a MS-DOS IP stack
available, which could use a WINS-server and connect to Samba using
NETBEUI over IP ???
I use TCP/IP 32 at the moment for my old windows-clients. Problem is,
I have some
2003 Mar 22
0
ext3 oops with 2.4.20
Bug report follows. Please CC me if you want me to read the reply, as
I'm not subscribed to ext3-users.
[1.] One line summary of the problem:
Ext3 has just causing filesystem corruption which required fsck to fix.
[2.] Full description of the problem/report:
I just had my machine lock up with an ext3 oops, preceeded by a bunch
of error messages in the logs. On rebooting, after replaying the
1999 Aug 25
4
Client on dos
I need to use a samba server (linux redhat 6.0 ) from a diskless dos
machine ( has a floppy drive for booting) . So i need a very little
tcp-ip stack for dos and a client for a NT server on dos so that they
will be small enough to be on a 1.44 system floppy.
Is that possible ?
Paul