This is a discussion on SWAT advice needed please within the Linux Networking forums, part of the Linux Forums category; I'm after a few pointers please! I've set up a network of 2 machines with Win XP and ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I'm after a few pointers please!
I've set up a network of 2 machines with Win XP and 1 Linux box running Mandrake 9.2. I can telnet into the box,run VNCserver with no problems.What I need to do next is set up the SWAT server.I have looked at the MAN pages and all the settings that are mentioned there seem to be ok but I cannot access SWAT through my web browser. Any ideas? |
|
|||
|
Hi,
> I've set up a network of 2 machines with Win XP and 1 Linux box running > Mandrake 9.2. > > I can telnet into the box,run VNCserver with no problems.What I need to do > next is set up the SWAT server.I have looked at the MAN pages and all the > settings that are mentioned there seem to be ok but I cannot access SWAT > through my web browser. sorry, but this is way to small information to really haelp you..... Ok, i can describe, how swat is used on my private file server. As defined by the distro's install routines (i don't use Mandrake), swat server is started via inetd. So /etc/inetd.conf contains a line for the swat-server. I don't know, if you start the server as a daemon or if you use (x)inetd, too. Anyway, make sure you pointed to the right binary:-) inetd won't start the service, when it can't find the swat-binary. Ok, when i want to access swat from, let's say a windows box, i start my browser and type: http://<ip of my file server>:901 This is neccessary, since the swat service is provided on port 901 and not the std. HTTP-port 80. After this, a login Window pops up, where i have to give user and passwd. It has to be a user installed on the linux box (e.g. root, makes sense to use this account). That's all, the swat-pages appear and i can set up things. 2 add. hints: - i use Mozilla FireFox browser, but any other one should do it - when you want to restart/start/stop samba daemons (smbd and nmbd) from swat, make sure, they also listen on the loopback interface (127.0.0.1, localhost) of your server. -> "interfaces" and "bind interfaces only" options in smb.conf If these hints don't help you out, please describe more details of your configuration. You also might want to post in NG comp.protocols.smb, which is related to all samba stuff. Ciao Ralf |
|
|||
|
Paul wrote:
> I'm after a few pointers please! > > I've set up a network of 2 machines with Win XP and 1 Linux box running > Mandrake 9.2. > > I can telnet into the box,run VNCserver with no problems.What I need to do > next is set up the SWAT server.I have looked at the MAN pages and all the > settings that are mentioned there seem to be ok but I cannot access SWAT > through my web browser. > > Any ideas? Yeah, change in the file /etc/xinet.d/swat a line to "disable=no" then do an "/etc/init.d/xinetd restart" and you might also want to adjust the line "only_from = 192.168.0.1" which limits access to this rather powerfull tool. Jan |
|
|||
|
Thanks for that advice Jan & Ralf.
This is where it gets weird.I was asdvised to try Webmin,which works spot on and I can even log on using SWAT via Winmin which seemed odd to me. Anyway thanks for your advise,all I need now is to setup the other bits n pieces" "Jan Geertsma" <jan@islief.com> wrote in message news:c80j8h$s0u$1@phys-news1.kolumbus.fi... > Paul wrote: > > I'm after a few pointers please! > > > > I've set up a network of 2 machines with Win XP and 1 Linux box running > > Mandrake 9.2. > > > > I can telnet into the box,run VNCserver with no problems.What I need to do > > next is set up the SWAT server.I have looked at the MAN pages and all the > > settings that are mentioned there seem to be ok but I cannot access SWAT > > through my web browser. > > > > Any ideas? > > Yeah, change in the file /etc/xinet.d/swat a line to "disable=no" > then do an "/etc/init.d/xinetd restart" and you might also want to > adjust the line "only_from = 192.168.0.1" which limits access to this > rather powerfull tool. > > Jan |