Frank,
Where are you trying to connect to the server from? Remotely, or on the
Samba server itself? If remotely, what IP address are you connecting from?
As a side note, Swat is not required to run Samba... You can manually edit
the smb.conf file, which is how I have done in the past. I did not even know
about Swat till this thread. Next time I set up Samba, I'm gonna give it a
shot...
Doug
----- Original Message -----
From: "Frank Roberts - SOTL" <sotl155360@earthlink.net>
To: <slug@nks.net>
Sent: Monday, August 06, 2001 7:44 PM
Subject: Re: [SLUG] xinetd
> Doug Thanks
>
> Final objective is to set up a 2 computer network.
> Since I had no idea of how to do this I searched for HOWTO on this. I
found 2
> and only 2 that pertain to a newbie setting up a network with Rh both for
RH
> 6.1.
>
> RH linux 6.x as an Internet Gateway for a Home Network by Paul Ramsey
> Samba Server by Ying Zhang
> and the setup notes from the Samba project
> Samba Project Documentation
>
> Well from Ramsey I was able to setup a network. I can ping the Linux box
from
> the Win 98 and vice verse. One big problem here that stumped me for days
was
> that I had either LAN or Internet but not both. Connection to the internet
is
> by modem. Partial solution to this problem is not to have LAN initiate on
> boot but to initiate it by user action after boot.
>
> Next I tried to set up Samba by editing configuration files. This may be
> possible but further reading suggest that I must have inetd or xinted.
This
> was confusing because Zhang referees to inetd not xinted so there were
> several post over that.
>
> After sorting out that RH 7.1 uses xinted I checked to find out it it was
> there and running. The answer to this was yes on both accounts.
>
> Now as far as I can tell I am down to the portion of where Zhang starts to
> configure Samba by SWAT. At this point he says that to use your favorite
> browser go to http://192.168.1.1:901 and if all goes well you should see a
> box pop up asking for a username and password. When I attempt this I get a
> message saying that the browser is unable to connect to 901.168.1.1 at
port
> 901.
>
> Now since I assume he knows more than I do - he did make at least one
network
> work to write his nice publication - I am assuming that I have something
> configured incorrectly.
>
> For more details on my exact setup go to:
> http://home.earthlink.net/~sotl166360
>
> For Zhang's procedure:
> http://dcfonline.sfu.ca/ying/linux/samba/
>
> For Ramsey's procedure see:
> http://www.coastnet.com/~pramsey/linux/homenet.html
>
> Thanks
> Frank
>
> PS: I am not cutting this because configuration files fo;;ow.
>
>
>
> On Monday 06 August 2001 06:40 pm, you wrote:
> > Frank,
> >
> > I don't think xinetd will be available at http://192.168.1.1:901... As
far
> > as I know, xinetd has no web administration interface (maybe there is a
> > component that can be added to Webmin to administer xinetd?). I think
what
> > you are looking for is a web management interface for Samba, if I recall
> > correctly from your original posts on this thread.
> > xinetd just monitors incoming requests, and wakes up the proper service
to
> > respond to them (in this case, SWAT). Not that any of the above actually
> > helps you with the issue...
> >
> > Where are you trying to connect to the server from? Remotely, or on the
> > Samba server itself?
> >
> > Doug
> >
> > ----- Original Message -----
> > From: "Frank Roberts - SOTL" <sotl155360@earthlink.net>
> > To: <slug@nks.net>
> > Sent: Monday, August 06, 2001 5:36 PM
> > Subject: Re: [SLUG] xinetd
> >
> > > > > Sorry to bother you people about the same old problems but I am
not
> > > > > following this.
> > >
> > > Well if this was working and if I had any additional ideas I would not
be
> > > posting this. Basically the problem is that when I go to Xinted by a
> >
> > browser
> >
> > > at: http://192.168.1.1:901 my browser say that there is no route to
this
> > > address. Different browsers express this differently but all with the
> > > same meaning.
> > >
> > > Whit follows first is the xited configuration file. May be there is
> >
> > something
> >
> > > wrong is so I don't see it.
> > > Following this is the resolve.conf file and the host.allow file. The
host
> > > deny file is empty.
> > >
> > > > > If I understand this correctly xinted should be accessible by a
> >
> > browser at
> >
> > > > > http://192.168.1.1:901 which is the address of my server at port
901.
> > > > >
> > > > > All I am able to get is "No route to host."
> > > > >
> > > > > My etc/xinted.d/swat file
> > > > >
> > > > > # default: off
> > > > > # description: SWAT is the Samba Web Admin Tool. Use swat \
> > > > > # to configure your Samba server. To use SWAT, \
> > > > > # connect to port 901 with your favorite web browser.
> > > > > service swat
> > > > > {
> > > > > port = 901
> > > > > socket_type = stream
> > >
> > > The following was added:
> > > protocol = tcp
> > >
> > > > > wait = no
> > > > > only_from = 127.0.0.1
> > >
> > > Changed to:
> > > > only_from = 192.9.168.10 192.9.168.11
> > > >
> > > > > user = root
> > > > > server = /usr/sbin/swat
> > > > > log_on_failure += USERID
> > > > > disable = no
> > > > > }
> > >
> > > -----------------------
> > > etc/hosts.allow file
> > > #
> > > # hosts.allow This file describes the names of the hosts which are
> > > # allowed to use the local INET services, as decided
> > > # by the '/usr/sbin/tcpd' server.
> > > #
> > > ALL: ALL
> > > -----------------------
> > > etc/hosts.allow file
> > > search localdomain
> > > nameserver 127.0.0.1
> > > nameserver 192.168.1.1
> > > nameserver 192.168.1.2
> > > -----------------------
> > > If anyone has any suggestions I would appreciate it.
> > > Please no RTFM as I am reading the manual.
> > >
> > > Thanks
> > > Frank
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:44:52 EDT