Hi, I'm running samba 1.9.17p2 on a Linux (Debian1.3.1) machine as a file server for W95 clients. Everything's working fine and fast, except for one problem... When accessing big files (>1MB) with i.e. Excel, the performance suddenly is incredible bad; it takes several minutes to open an 1MB xls-file. The same thing happens when I open a database with another CASE-program I'm working with. While accessing the file, the Linux machine and the network show no big load, less than 10%, so it doesn't depend on the net or processor load. Copying big files works fast and I can achieve more than 800kB/s; I was even able to open a 8MB file within less than 15 seconds from MS-word(!). So the problem seems to depend on the program that is accessing the fileservice and not on the configuration of samba. Are there different methods to access files from the network? Has anyone similar experiences or, even better ;-) , an idea or solution to the problem? Thanks, Markus _______________________________________________________________ Markus Gebhardt email: magebhar@fe13603.fe.bosch.de ETAS GmbH & CO. KG Phone: +(49)711-89661-278 Borsigstrasse 10 D-70469 Stuttgart Fax: +(49)711-89661-105
With Windows 98 and NT SP3 it becomes increasingly important to support encrypted Windows passwords via the SAMBA smbpasswd file. However, there is no way to convert the UNIX /etc/passwd file encrypted passwords to smbpasswd, and it is virtually impossible to ask all users at a site to come to the sysadmins to type in their password for generating smbpasswd entries (neither users nor sysadmins would like such a solution). Some months ago the SAMBA developers talked about "automatically" generating smbpasswd entries from the clear-text passwords that are passed to the SAMBA server today. After a while, the smbpasswd file would be complete, and one could then launch a new service using encrypted passwords without involving the users directly. This sounds like the right thing to do in preparation for deployment of Windows 98 (and for the occasional NT workstation :-). Is this line of development being pursued, or is it even feasible with the present SAMBA code ?? Ole H. Nielsen Department of Physics, Building 307 Technical University of Denmark, DK-2800 Lyngby, Denmark E-mail: mailto:Ole.H.Nielsen@fysik.dtu.dk
Has anyone tried to setup a Samba print queue that would feed HylaFAX? If so, pointers would be appreciated. --- Tim Rand tim@datapage.com VP Information Systems +1-314-278-8888 (voice) Datapage Technologies International, Inc. +1-314-278-2180 (fax) 222 Turner Blvd. St. Peters, MO 63376 USA
> I'm trying to determine what is causing an NT workstation login such a > long time to complete.One thing to look at the configuration of your DNS. Make sure that it's pointing to a valid DNS with the correct domain. I've seen similar delays to this under Unix where the DNS has to timeout before the operation completes. Brett Worth
Hi I was very interrested when I read your message, because I have the same problem. I have installed Windows for Workgroups 3.11, together with MS TCP/IP 32. I need TCP/IP 32 because Samba can only hande SMB over TCP, and not TCP over NetBEUI (Standard in Win95, and the only posibility for WFW 3.11 without MS TCP/IP 32). So I think you cannot access Samba Servers with the DOS-Client from Microsoft. However, maybe there is something like TCP/IP 32 also for the MS Dos-Client. The Only solution I found for SMB over TCP under Dos was LANMANAGER-Client from IBM (Free, like the MS-Client). I didn't try it yet, but I will do so in the next days. If you have further questions or you find other solutions, please send me a mail (fgpqfgp.atnet.at) Greetings, fgp