samba and inetd problems

[Ron Alexander]

I don't know the details of the bug(s) in inetd or the stcp stack in
general.

I do know, that swat is now working for the 1st time! This is a bonus!

Keep in mind that the connection looks like this:

>From my NT4.0 SP6a thru 2 firewalls on my PC(ZoneAlarm and AtGuard) out the
@home cable network thru? a hardware firewall (VPN, RADIUS) to the Stratus.

I have been able to update files on the Stratus from my PC, but nothing
works in the other direction. I think it has something to do with browsing
etc., but I am not sure. I am going to attempt to put a Linux firewall at
the cable modem, and create a network behind it of my NT Workstation and a
new NT4.0 server. The server can become the Master Browser? and hopefully
allow browsing from the Stratus back to my PC.

Later,
Ron

-----Original Message-----
From: James Sutherland [mailto:jas88 at cam.ac.uk]
Sent: May 19, 2000 1:46 PM
To: Ron Alexander
Cc: 'Multiple recipients of list SAMBA-TECHNICAL'
Subject: RE: samba and inetd problems


On Fri, 19 May 2000, Ron Alexander wrote:

> I should have explained that although I have been in the computer biz for
33
> years, I am new to Unix and all things to do with communications
> (intentionally).

Fairy nuff. I can understand you avoiding both areas - they do seem rather
user-hostile in parts :-)

> I also probably mislead you when I said recommended. What I should have
said
> is that several books document how to start the Samba daemons from either
> inetd or startup scripts (I think that is the proper Unix phrase).

Aha! TBH, they really should have explained "you CAN run it via inetd, but
don't do it unless SMB is VERY rarely used". (I run FTP this way, for
example, as I mentioned.)

> The specific books are:
> Using Samba		                  pg. 46-48
> Samba, Unix & NT Internetworking	pg. 24-28, 93, 260
> Teach Yourself Samba in 24 hours	pg. 55-56
>
> I now understand that inetd is used for low traffic situations and other
> technical reasons. VOS has the concept of a boot script, and I have no
> problem starting it that way.

That's certainly the best way for most situations.

> It also appears that there is a bug in the POSIX port that is happening in
> parallel. I just got notified that they are restarting the stcp stack and
I
> can test again.

What's this bug?

> If anyone is interested, I will post the results of further testing.
Please
> respond in the affirmative if you are interested.

Speaking only for myself, I would certainly be interested in any further
reports, especially of Samba on VOS - success reports preferred, of course
:-)


James.