samba@samba.org ????????:> SAMBA Digest 2226
>
>For information on unsubscribing see http://samba.org/listproc/
>Topics covered in this issue include:
>
> 1) RE: weird printing problems.
> by "cbrink" <cbrink@allsportssupply.com>
> 2) Re: weird printing problems.
> by "John J. LeMay Jr." <jlemay@njmc.com>
> 3) Connection reset by peer
> by Martin Schapendonk <M.Schapendonk@kub.nl>
> 4) Re: Samba slower than FTP?
> by Chris Watt <cnww@hfx.andara.com>
> 5) RE: weird printing problems.
> by <jeremy@xxedgexx.com>
> 6) Ack... Printing
> by Keith Baker <toaster@ampere.dhs.org>
> 7) Re: Eudora problems
> by Christian Perrier <perrier@onera.fr>
> 8) NMB Problems.
> by Sean Armstrong <sarmstrong@swpolymers.com>
> 9) W95 speed issue - SOLVED!!!
> by Edward Schernau <ed@schernau.com>
> 10) AIX 4.32 SAMBA Install
> by "Antonio Sosa" <sosa19@idt.net>
> 11) multiple interfaces
> by "Tom Priore" <tpp109@psu.edu>
> 12) oplock_break problem
> by EC - Bridget Lung <blung@penang.png.intel.com>
> 13) Date garbage on NT share
> by Martin Ortlepp <martin.ortlepp@hannoversche-leben.de>
> 14) Problem joining to NT-PDC with my own scopeID
> by "Andrew Belgorodtsev" <Andrew@omsk.net>
> 15) AW-samba-digest-2225-case-sensivity-hpux
> by Schreiber Martin <martin.schreiber@siemens.at>
> 16) Fw: Problem joining to NT-PDC with my own scopeID
> by "Andrew Belgorodtsev" <Andrew@omsk.net>
> 17) SAMBA 2.0.5a oplock_break: client failure in break
> by Ole Holm Nielsen <Ole.H.Nielsen@fysik.dtu.dk>
> 18) functionality of lmhosts file
> by "M.Sapsed" <m.sapsed@bangor.ac.uk>
> 19) Dos error 59 messages
> by "Craig H. Anderson" <craiga@ggitpa.ggise.com>
> 20) HP-UX 10.20 compile
> by "Ansley, Michael" <Michael.Ansley@intec.co.za>
> 21) Re: LP print service stalls
> by "Roger Kennedy" <rkennedy@chaptech.com>
> 22) Windows can't browse Samba server
> by Mark Symmonds <msymmonds@ifleet.com>
>
>----------------------------------------------------------------------
>
>Date: Tue, 7 Sep 1999 08:37:49 -0700
>From: "cbrink" <cbrink@allsportssupply.com>
>To: <jeremy@xxedgexx.com>,
> "'Multiple recipients of list SAMBA'"
<samba@samba.org>
>Subject: RE: weird printing problems.
>Message-ID: <00ad01bef946$f16afc60$1c0100c0@allsportssupply.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>
>I just sent a message on this to this group under RE: LP Print Service
>Stalls
>
>
>
>>
>> I'm experiencing some weird printing problems with samba connected
>> printers. When I'll bring up a 95/98 workstation, sometimes
>> it will say
>> that the printer is offline, when it clearly isn't, or it will see
>> everything fine, but it simply won't print.
>>
>> These are remote lpd connected printer to the samba server,
>> and lpd can
>> print fine. These are JetDirect HP printers.
>>
>> Any troubleshooting tips? I thought perhaps the spool names
>> would have
>> something to do with it. The shares and the spools are weird names to
>> help aviod user confusion.
>>
>> [Bull Pen Printer]
>>
>> [Hall Way Printer]
>>
>> Thanks
>> -jeremy
>>
>>
>http://www.xxedgexx.com | jeremy@xxedgexx.com
>---------------------------------------------
>Y2K. We're all gonna die.
>
>
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 11:44:39 -0400 (EDT)
>From: "John J. LeMay Jr." <jlemay@njmc.com>
>To: jeremy@xxedgexx.com
>Subject: Re: weird printing problems.
>Message-ID:
<Pine.BSI.4.10.9909071142290.16755-100000@shell.monmouth.com>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
>This could do it. The win stations may not be able to resolve the long
>share names initially. You should probably try to rename one of the
>printers initially and see if it helps. I would receommend a different
>naming convention - perhaps color based. Name one printer "blue"
and hang
>a blue sheet of contruction paper over it with the name "blue",
name the
>other "red" and do similar. I've used this method in large
environments of
>several thousand users and it works quite well!
>
>On Wed, 8 Sep 1999 jeremy@xxedgexx.com wrote:
>
>>
>> I'm experiencing some weird printing problems with samba connected
>> printers. When I'll bring up a 95/98 workstation, sometimes it
will say
>> that the printer is offline, when it clearly isn't, or it will see
>> everything fine, but it simply won't print.
>>
>> These are remote lpd connected printer to the samba server, and lpd can
>> print fine. These are JetDirect HP printers.
>>
>> Any troubleshooting tips? I thought perhaps the spool names would have
>> something to do with it. The shares and the spools are weird names to
>> help aviod user confusion.
>>
>> [Bull Pen Printer]
>>
>> [Hall Way Printer]
>>
>> Thanks
>> -jeremy
>>
>>
>> http://www.xxedgexx.com | jeremy@xxedgexx.com
>> ---------------------------------------------
>> Y2K. We're all gonna die.
>>
>>
>
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 17:53:13 +0200 (CEST)
>From: Martin Schapendonk <M.Schapendonk@kub.nl>
>To: samba@samba.org
>Subject: Connection reset by peer
>Message-ID: <Pine.LNX.4.10.9909071744500.21016-100000@kubstu.kub.nl>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>Hi,
>
>I run Samba 2.0.5a on Linux 2.2.12 (Slackware).
>
>My clients get an error regularly (Windows95) "Network path not
found"
>and then they lose their connection completely.
>
>The server logs the following:
>[1999/09/07 17:30:01, 1] smbd/service.c:make_connection(521)
> sbit12 (137.56.40.139) connect to service sbitdata as user sbit (uid=1000,
gid=100)
(pid 134)>[1999/09/07 17:33:10, 0] lib/util_sock.c:read_socket_data(507)
> read_socket_data: recv failure for 4. Error = Connection reset by peer
>[1999/09/07 17:33:10, 1] smbd/service.c:close_cnum(557)
> sbit12 (0.0.0.0) closed connection to service sbitdata
>
>This happens unpredictable, very strange.
>
>Does anyone know how I can solve this problem, because it is very
>annoying :( and keeps us from working.
>
>I searched the internet, but there were only people with the same
>problem, but no solutions.
>
>Thanks in advance,
>
>Martin
>
>--
> Martin Schapendonk, M.Schapendonk@kub.nl, Phone: +31 (0)13-4678293
> Student Information Management and Technology at Tilburg University
> WEBMaster of the Students-WWW-server stuwww.kub.nl / PGP on request
>
>
>------------------------------
>
>Date: Tue, 07 Sep 1999 13:00:37 -0300
>From: Chris Watt <cnww@hfx.andara.com>
>To: samba@samba.org
>Subject: Re: Samba slower than FTP?
>Message-ID: <3.0.3.32.19990907130037.006c5d30@tito>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>
>At 08:57 PM 9/7/99 +1000, Nick Dobrovolski wrote:
>>Hello gurus,
>--- SNIP ---
>>faster than copy via samba share. Can you provide me with any helpful
>>advices on tuning samba server in order to speed the things up?
>
>I'm not exactly a Guru, but afaik the only serious tweaking you can do
is:
>
>- Enable and use WINS to avoid all that nasty broadcast traffic
>- Set your socket options to the reccomended setting in the smb.conf man
page.
>- Read but largely ignore Speed.txt and Speed2.txt (some of the advice in
>the latter file is genuinely harmful).
>- Hope for the best.
>
>On my LAN I tend to get around 2mb per second on get's and 3.x mb per
>second on puts with Samba, this compares to about 2mb per second on gets
>and 6mb per second on puts with FTP. All the machines involved are using
>LinkSys Etherfast 10/100 cards connected to a LinkSys 10/100 hub.
>Oddly enough when I connected a 10mbit/s client to the hub and tried samba
>out I got about 750kb/s put and 900kb/s get. . . If anyone can explain this
>I'm listening :)
>--
>
>Who is this General Failure, and why is he reading my hard disk?
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 12:22:09 -0400 (EDT)
>From: <jeremy@xxedgexx.com>
>To: cbrink <cbrink@allsportssupply.com>
>Subject: RE: weird printing problems.
>Message-ID:
<Pine.LNX.4.05.9909071221280.3874-100000@srv1.ecropolis.com>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
>Hmm, can't seem to find the message on the archives. I just joined the
>list, soo...
>
>if you could forward me the mail, it would be greatly appreciated.
>
>-jeremy
>
>> I just sent a message on this to this group under RE: LP Print Service
>> Stalls
>>
>>
>>
>> >
>> > I'm experiencing some weird printing problems with samba
connected
>> > printers. When I'll bring up a 95/98 workstation, sometimes
>> > it will say
>> > that the printer is offline, when it clearly isn't, or it will
see
>> > everything fine, but it simply won't print.
>> >
>> > These are remote lpd connected printer to the samba server,
>> > and lpd can
>> > print fine. These are JetDirect HP printers.
>> >
>> > Any troubleshooting tips? I thought perhaps the spool names
>> > would have
>> > something to do with it. The shares and the spools are weird
names to
>> > help aviod user confusion.
>> >
>> > [Bull Pen Printer]
>> >
>> > [Hall Way Printer]
>> >
>> > Thanks
>> > -jeremy
>> >
>> >
>> http://www.xxedgexx.com | jeremy@xxedgexx.com
>> ---------------------------------------------
>> Y2K. We're all gonna die.
>>
>>
>>
>
>
>http://www.xxedgexx.com | jeremy@xxedgexx.com
>---------------------------------------------
>Y2K. We're all gonna die.
>
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 12:56:36 -0400 (EDT)
>From: Keith Baker <toaster@ampere.dhs.org>
>To: samba@samba.org
>Subject: Ack... Printing
>Message-ID: <Pine.LNX.3.96.990907125504.521A-100000@alpha>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>I am trying to allow printing to my LaserJet III. I can print locally and
>I get no errors when I send a print job but I never get any printout. In
>the loging it says lp -c... blah returned 0 (no error yes?) Any hints?
>
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 18:27:25 +0200
>From: Christian Perrier <perrier@onera.fr>
>To: Multiple recipients of list SAMBA <samba@samba.org>
>Subject: Re: Eudora problems
>Message-ID: <19990907182724.B18493@mykerinos>
>Mime-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>
>Quoting Martin Sheppard (martins@dhn.csiro.au):
>
>[snip pb desc.]
>
>> Problem software:
>> Eudora Pro 4.1
>
>With Eudora Light 3.0.6, I didn't notice such problem. For
>information, can you try with this version?
>
>
>
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 16:09:06 -0500
>From: Sean Armstrong <sarmstrong@swpolymers.com>
>To: samba@samba.org
>Subject: NMB Problems.
>Message-ID: <99090716160801.00920@nelson.swpolymers.com>
>Content-Type: text/plain
>MIME-Version: 1.0
>Content-Transfer-Encoding: 8bit
>
>Sorry for this newbie question, but I seem to have a problem with NMB
services
>on bootup. I was able to get an [OK] on NMB services at boot up when I
>did not add anything to resolv on netconf and my resolv.conf file just read
>search. However, I was not able to connect to the internet. When I deleted
>the line search from resolv.conf and added my DNS server and nameserver
address
>to the resolv portion of netconf, I was able to connect to the internet but
got
>a [fail] for NMB services on bootup. There is another linux box on the
network
>that NMB works fine on and the only difference between it's netconf and
mine
>are that it has a static IP adress and I use DHCP. I don't want a
static IP
>address. Is there a way around this problem with DHCP?
>thanx,
>SA
>
>------------------------------
>
>Date: Tue, 07 Sep 1999 17:30:50 -0400
>From: Edward Schernau <ed@schernau.com>
>To: samba@samba.org
>Subject: W95 speed issue - SOLVED!!!
>Message-ID: <37D5840A.8B4A0AC0@schernau.com>
>MIME-Version: 1.0
>Content-Type: multipart/mixed;
> boundary="------------E6F88B222901CE064E88CBA0"
>
>This is a multi-part message in MIME format.
>--------------E6F88B222901CE064E88CBA0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Turns out a complete uninstall and reinstall of TCPIP and the network
>components in W95 did the trick. I can now pull files from Samba at
>a reasonable, if not perfect speed.
>
>NB. I am now running without any of the DUN upgrades, maybe they broke
>it.
>
>Ed
>--------------E6F88B222901CE064E88CBA0
>Content-Type: text/x-vcard; charset=us-ascii;
> name="ed.vcf"
>Content-Transfer-Encoding: 7bit
>Content-Description: Card for Edward Schernau
>Content-Disposition: attachment;
> filename="ed.vcf"
>
>begin:vcard
>n:Schernau;Edward
>x-mozilla-html:FALSE
>adr:;;;;;;
>version:2.1
>email;internet:ed@schernau.com
>title:Network Architect
>x-mozilla-cpt:;-10656
>fn:Edward Schernau
>end:vcard
>
>--------------E6F88B222901CE064E88CBA0--
>
>
>------------------------------
>
>Date: Tue, 7 Sep 1999 18:20:36 -0500
>From: "Antonio Sosa" <sosa19@idt.net>
>To: <samba@samba.org>
>Subject: AIX 4.32 SAMBA Install
>Message-ID: <003d01bef987$98541120$0100000a@pdc_tony>
>MIME-Version: 1.0
>Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0038_01BEF95D.AE741330"
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_0038_01BEF95D.AE741330
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>I've just become aware of a problem with Samba and AIX 4.32. I tried to
>compile the source and found I could but the binaries do not work
>correctly. SMBCLIENT times out and has a READ error. I guess this is a
>known problem with 4.32 because I recieved a number of e-mails asking me
>if I had AIX 4.32 and not 4.3. It turns out I do have 4.32 and was
>wondering if anybody has found a workaround to get samba to work on this
>version of AIX. Thanks goes to all who e-mailed me.
>
>
>P.S. Does anybody know why Samba has a problem with this version?
>Tony
>
>------=_NextPart_000_0038_01BEF95D.AE741330
>Content-Type: text/html;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
><HTML>
><HEAD>
>
><META content=3Dtext/html;charset=3Diso-8859-1
>http-equiv=3DContent-Type>
><META content=3D'"MSHTML 4.72.3110.7"'
name=3DGENERATOR>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT color=3D#000000 size=3D2>I've just become aware
of a problem >with Samba=20
>and AIX 4.32. I tried to compile the source and found I could but the
>binaries=20
>do not work correctly. SMBCLIENT times out and has a READ error. I guess
>this is=20
>a known problem with 4.32 because I recieved a number of e-mails asking
>me if I=20
>had AIX 4.32 and not 4.3. It turns out I do have 4.32 and was wondering
>if=20
>anybody has found a workaround to get samba to work on this version of
>AIX.=20
>Thanks goes to all who e-mailed me.</FONT></DIV>
><DIV><FONT color=3D#000000
size=3D2></FONT> </DIV>
><DIV> </DIV>
><DIV><FONT color=3D#000000 size=3D2>P.S. Does anybody know why
Samba has >a problem=20
>with this version?</FONT></DIV>
><DIV><FONT color=3D#000000
size=3D2>Tony</FONT></DIV></BODY></HTML>
>
>------=_NextPart_000_0038_01BEF95D.AE741330--
>
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 02:02:23 -0400
>From: "Tom Priore" <tpp109@psu.edu>
>To: "Samba Mailing List" <samba@samba.org>
>Subject: multiple interfaces
>Message-ID: <NDBBKFGKIKCIKFGNDOAICELMCDAA.tpp109@psu.edu>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>
>I'm having a problem getting samba to work on 2 interfaces
>I have a machine set up with 2 nics. It is a red hat linux 6.0 computer
>running samba 2.0.5a. The machine is set up as a firewall so that the
>computers on the local side are protected from all those evil people on the
>@home network:)
>
>previously the machine was set up only to share on the internal network, and
>it worked great. now though the machine needs to be accessed by someone on
>the external network, so i changed my interface line my adding the 2nd nics
>ip with a /24 after it, and added the users ip to the host allow list.
>
>it didnt work. so then i figured i'll test one thing at a time. i
dissable
>the host allow, letting every one in. it still didnt work.
>
>i can ping the user on the external network.
>
>Thanks for any help.
>Tom
>
>
>------------------------------
>
>Date: Wed, 08 Sep 1999 18:46:12 +0800
>From: EC - Bridget Lung <blung@penang.png.intel.com>
>To: samba@samba.org
>Subject: oplock_break problem
>Message-ID: <199909081046.SAA01080@penang.png.intel.com>
>Mime-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>
>I have referred to the archive and some of you were having the oplock_break
>problem. Does anyone have any solution for this? Will reboot fix the
problem?
>
>Please advise.
>
>regards,
>Bridget
>
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 13:08:02 +0200
>From: Martin Ortlepp <martin.ortlepp@hannoversche-leben.de>
>To: samba@samba.org
>Subject: Date garbage on NT share
>Message-ID: <99090813145803.00343@ortldev>
>Content-Type: text/plain
>MIME-Version: 1.0
>Content-Transfer-Encoding: 8bit
>
>Hi,
>
>I?m running Samba 2.0.5a and Linux 2.2.3. When I try to mount a NT share it
>works but I always get differences between the file date on nt share and
>linux on the other side. I have filedates from year 1900 to 2060 (on the
linux
>side). File dates on the NT sides are correct.
>
>Any ideas?
>
>Martin
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 19:00:19 +0700
>From: "Andrew Belgorodtsev" <Andrew@omsk.net>
>To: <samba@samba.org>
>Subject: Problem joining to NT-PDC with my own scopeID
>Message-ID: <000a01bef9f1$b9484b70$8f4da1c3@omsk.net>
>MIME-Version: 1.0
>Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0007_01BEFA2C.65561D40"
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_0007_01BEFA2C.65561D40
>Content-Type: text/plain;
> charset="koi8-r"
>Content-Transfer-Encoding: quoted-printable
>
>
>
>------=_NextPart_000_0007_01BEFA2C.65561D40
>Content-Type: text/html;
> charset="koi8-r"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
><HTML><HEAD>
><META content=3D"text/html; charset=3Dkoi8-r"
http-equiv=3DContent-Type>
><META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV> </DIV></BODY></HTML>
>
>------=_NextPart_000_0007_01BEFA2C.65561D40--
>
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 14:15:00 +0200
>From: Schreiber Martin <martin.schreiber@siemens.at>
>To: "'samba@samba.org'" <samba@samba.org>
>Subject: AW-samba-digest-2225-case-sensivity-hpux
>Message-ID:
<F3A2AEBAD9DAD211A2C20800060DA32610611A@vieg127a.gud.siemens.at>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 8BIT
>
>
>Hello everybody,
>I refer to case-sensivity problem on hpux,
>
>in your global section only activate "preserve case = true" , case
sensitiv
>should be the default value which is false !! . We use this setting in a
>great clearcase environment
>nt - hpux 10.20 and it works great. fot further settings you can contact me.
>
>regards martin schreiber
>email martin.schreiber@siemens.at
> SIEMENS Siemens AG ?sterreich
> Competence Center Information
> Technology and Networking
> Gudrunstrasse 11
> A-1101 Wien
>
> Martin Schreiber Phone +43 1 1707 47565
> Server-Administration Fax +43 1 1707 57560
> mailto:martin.schreiber@siemens.at
> http://www.siemens.at
>
>Wichtiger Hinweis: Diese Information ist fuer den Gebrauch durch die Person
>oder die Firma/Organisation bestimmt, die in der Empfaengeradresse benannt
>sind. Wenn Sie nicht der angegebene Empfaenger sind, nehmen Sie bitte zur
>Kenntnis, dass Weitergabe, Kopieren, Verteilung oder Nutzung des Inhalts
>dieser Email-Uebertragung unzulaessig ist. Falls Sie diese Email irrtuemlich
>erhalten haben, benachrichtigen Sie den Absender bitte unverzueglich
>telefonisch oder durch eine Email
>
>
>
>
>
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 19:03:57 +0700
>From: "Andrew Belgorodtsev" <Andrew@omsk.net>
>To: <samba@samba.org>
>Subject: Fw: Problem joining to NT-PDC with my own scopeID
>Message-ID: <001b01bef9f2$3af13240$8f4da1c3@omsk.net>
>MIME-Version: 1.0
>Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0018_01BEFA2C.E7349300"
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_0018_01BEFA2C.E7349300
>Content-Type: text/plain;
> charset="koi8-r"
>Content-Transfer-Encoding: quoted-printable
>
>hi*&
>
>I have troubles with joining 2 NT PDC because I can not specify scopeID
>for smbpasswd command. What can I do? There is analogu problem with
>smb_mount, that not understand different scopeIDs.
>Any advices?
>Thanks.
>
>
>
>
>------=_NextPart_000_0018_01BEFA2C.E7349300
>Content-Type: text/html;
> charset="koi8-r"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0
Transitional//EN">
><HTML><HEAD>
><META content=3D"text/html; charset=3Dkoi8-r"
http-equiv=3DContent-Type>
><META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DArial
size=3D2>hi*&</FONT></DIV>
><DIV><FONT face=3DArial
size=3D2></FONT> </DIV>
><DIV><FONT face=3DArial size=3D2>I have troubles with joining 2
NT PDC >because I can=20
>not specify scopeID for smbpasswd command. What can I do? There is
>analogu=20
>problem with smb_mount, that not understand different
>scopeIDs.</FONT></DIV>
><DIV><FONT face=3DArial size=3D2>Any
advices?</FONT></DIV>
><DIV><FONT face=3DArial
size=3D2>Thanks.</FONT></DIV>
><DIV><FONT face=3DArial
size=3D2><BR> </DIV></FONT>
><DIV> </DIV></BODY></HTML>
>
>------=_NextPart_000_0018_01BEFA2C.E7349300--
>
>
>------------------------------
>
>Date: Wed, 08 Sep 1999 15:27:12 +0200
>From: Ole Holm Nielsen <Ole.H.Nielsen@fysik.dtu.dk>
>To: samba@samba.org
>Subject: SAMBA 2.0.5a oplock_break: client failure in break
>Message-ID: <37D66430.E8455285@fysik.dtu.dk>
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>We are running Samba 2.0.5a on an AIX 4.2.1 box, and since
>we upgraded from 1.9.18, a Windows 95 client reports
>intermittent problems (timeouts) when saving small files.
>The log.smb file has entries from those events:
>
>[1999/09/08 14:59:07, 0] smbd/oplock.c:oplock_break(905)
> oplock_break resend
>[1999/09/08 14:59:17, 0] smbd/oplock.c:oplock_break(905)
> oplock_break resend
>[1999/09/08 14:59:27, 0] smbd/oplock.c:oplock_break(905)
> oplock_break resend
>[1999/09/08 14:59:37, 0] smbd/oplock.c:oplock_break(922)
> oplock_break: receive_smb timed out after 30 seconds.
> oplock_break failed for file breve/weco.tex (dev = 290001, inode =
621734).
>[1999/09/08 14:59:37, 0] smbd/oplock.c:oplock_break(992)
> oplock_break: client failure in break - shutting down this smbd.
>
>After reading the manual I though that this line in smb.conf
>ought to solve the problem:
> oplock break wait time = 50
>However, this does not improve things (I even tried 250 msecs).
>
>So something is going wrong with the oplocks, and even if
>one may blame Windows 95, my question is: What should I
>do to eliminate this oplock problem ? Is it really a
>client problem ?
>
>Ole H. Nielsen
>Department of Physics, Technical University of Denmark,
>
>------------------------------
>
>Date: Wed, 08 Sep 1999 14:35:33 +0100
>From: "M.Sapsed" <m.sapsed@bangor.ac.uk>
>To: Multiple recipients of list SAMBA <samba@samba.org>
>Subject: functionality of lmhosts file
>Message-ID: <37D66625.88084E1C@bangor.ac.uk>
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Hi all,
>
>Once upon a time, if you had an entry in the lmhosts file of a samba server
>call bigserver (say) like
>
>0.0.0.0 myserver
>
>then any query from a client to bigserver asking for \\myserver would be
>answered by bigserver. This functionality seems to have disappeared going
>from perhaps 1.9.17 to 1.9.18? I was wondering why and whether there were
>any plans to put it back?
>
>I was also wondering about progress towards wins replication but whether
>this would allow for a name to which all servers would respond, although
>since any client here can only see one server that's fine.
>
>Does this make any sense??
>
>Cheers
>
>Martin
>
>--
>Martin Sapsed Tel: +44 (0)1248 382409
>Computing Lab Fax: +44 (0)1248 383826
>University of Wales, Bangor m.sapsed@bangor.ac.uk
>North Wales, LL57 2DG
> Press any key to continue or any other key to quit...
>
>------------------------------
>
>Date: Wed, 08 Sep 1999 11:19:18 -0400
>From: "Craig H. Anderson" <craiga@ggitpa.ggise.com>
>To: samba@samba.org
>Subject: Dos error 59 messages
>Message-ID: <37D67E76.EEA8011E@ggise.com>
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>Hi there,
>
>I just upgraded from samba-1.9.18p8 to 2.0.5a on my Solaris 2.5 server,
>and I'm getting "Dos error 59" messages on my NT-4.0/SP4
boxes when
>they
>attempt to run an old windows app "TimeTrax" off the server. Any
ideas?
>
>I made sure kernel oplocks is off, but this doesn't seem to help.
>
>Note also that the following messages:
>
>[1999/09/08 10:50:35, 0] smbd/nttrans.c:call_nt_transact_ioctl(2387)
> call_nt_transact_ioctl: Currently not implemented.
>
>are being logged whenever one of the NT boxes tries to run the app in
>question.
>
>Any help is greatly appreciated,
>
>CRaig
>--
> ----------------------------------------------------------------------
>| Craig H. Anderson | logan@ggise.com |
>| Systems Administrator-------------------------+----------------------|
>| Genesis Group / | www.ggise.com |
>| Biological Research Associates | www.biolresearch.com |
> ----------------------------------------------------------------------
>.. Any resemblance between the above views and those of my employer,
>my terminal, or the view out my window are purely coincidental. Any
>resemblance between the above and my own views is non-deterministic.
>The question of the existence of views in the absence of anyone to hold
>them is left as an exercise for the reader. The question of the
>existence of the reader is left as an exercise for the second god
>coefficient. (A discussion of non-orthogonal, non-integral polytheism
>is beyond the scope of this article.)
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 17:30:19 +0200
>From: "Ansley, Michael" <Michael.Ansley@intec.co.za>
>To: "'samba@samba.org'" <samba@samba.org>
>Subject: HP-UX 10.20 compile
>Message-ID: <1BF7C7482189D211B03F00805F8527F748C04B@S-NATH-EXCH2>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>
>Hi, all
>
>I'm trying to get samba to compile on said platform, and it's
telling me
>that file locking is not available. And yet this configured fine on another
>very similar machine. Anybody know why this happens? The main difference
>between the machines is that on the machine which fails, large file support
>is enabled; on the machine where samba works, it is not.
>
>Thanks...
>
>
>MikeA
>
>
>
>------------------------------
>
>Date: Wed, 8 Sep 1999 11:38:51 -0400
>From: "Roger Kennedy" <rkennedy@chaptech.com>
>To: <cbrink@allsportssupply.com>
>Cc: <samba@samba.org>
>Subject: Re: LP print service stalls
>Message-ID: <002301befa10$40d1e1f0$f3670cd8@chaptech.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>
>HP's tech. support pointed me back to the OS as the source of the
problem.
>I searched Sun's site for info. and found a patch for the lp system. It
>seems that if lpsched received a filename greater than 24 characters the
>service would die.
>The patch ID is 10359-10.
>
>----- Original Message -----
>From: cbrink <cbrink@allsportssupply.com>
>To: <rkennedy@chaptech.com>; 'Multiple recipients of list
SAMBA'
><samba@samba.org>
>Sent: Tuesday, September 07, 1999 11:36 AM
>Subject: RE: LP print service stalls
>
>
>> This is a limitation of the JetDirect card. A JetDirect card can only
>handle
>> one session at a time (1 printjob, 1 lpstat). Sounds like your printer
>> subsystem is not handling the timeout correctly. I would look into
that.
>You
>> can call HP's Tech Support they are very helpful on these problems.
>>
>>
>>
>> Hi All,
>>
>> When our server receives simultaneous print jobs from 2 or more
clients,
>the
>> print service stalls and I have to manually restart it (lpsched).
>> I am running Samba 2.0.4b under Solaris 2.5.1 on a SPARC 20 and I'm
using
>> system V printing. The printers are connected to the ethernet using HP
>> Jetdirect cards and administered by jetadmin on the Sun box.
>> Any ideas on how I could troubleshoot this?
>>
>> Thanks in advance.
>>
>> Here is the relevant smb.conf info:
>>
>> [global]
>> workgroup = GROUP
>> netbios name = SERVER
>> encrypt passwords = Yes
>> log file = /var/opt/samba/log.smb
>> socket options = TCP_NODELAY
>> os level = 65
>> create mask = 0770
>> directory mask = 0770
>> hosts allow = XXX
>>
>> [laser1]
>> comment = Laserjet 4
>> path = /tmp
>> read only = No
>> print ok = Yes
>> printer name = laser1
>>
>>
>
>
>------------------------------
>
>Date: Wed, 08 Sep 1999 11:52:39 -0400
>From: Mark Symmonds <msymmonds@ifleet.com>
>To: samba@samba.org
>Subject: Windows can't browse Samba server
>Message-ID: <37D68647.41E88E84@ifleet.com>
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>
>I have two Samba servers and three Windows clients (two 95 and one NT).
>One Samba server has been running for a while and is having no problems.
>I just installed a new Linux box and loaded up Samba (2.0.3). After
>configuring it to act as a PDC, WINS server, and master browser, I fired
>it up. Everything seems to be working fine, except no Windows clients
>can see the Samba server via Network Neighborhood, ping, or Find
>Computer. Samba passed tests 1,3,4,5 (for the other Samba server as
>ACLIENT), 6 (for the Samba servers), and 7. The Windows clients can see
>all the other machines (including the older Samba server), so I am
>assuming the Samba server is providing master browser services (and
>log.nmb reports that it is the domain and local master browser). smb is
>reporting no errors all the way to debug level 10. Any ideas?
>
>
>
>
>
>
>------------------------------
>
>End of SAMBA Digest 2226
>************************