Files
mars-smart/doc/FAQ
2026-04-21 02:12:28 +02:00

42 lines
2.4 KiB
Plaintext

Well, okay, nobody asked any question yet, but well, somebody might want to ask
this question:
Q: AAAARGH! My browser keeps complaining about wrong authentication!
A: Well, the authentication system of my webserver is very simple, the first
time you log into the webserver, the program asks for a username/password,
and that username/password will be saved in the config-file. But maybe I
forgot to delete the Authentication line from the config-file, so just edit
the webserve.conf file and remove that line. Login, and type your favourite
name/password pair, and don't forget them... Well, you can just re-delete
the line, but I don't think that's very handy. You can also disable the
password check, but I don't think that's very handy either...
Q: Hey, the user editor/bindery browser doesn't work!
A: Maybe you haven't installed the ncpfs package yet, this is needed to edit
the user list in the bindery. Also, don't forget to start the server,
'cause you can't edit the bindery when the server is not in the air.
And it is possible that you've changed the SUPERVISOR password, and SMArT
doesn't know the new password yet. Use SMArT configuration to tell SMArT
the new password.
It's also possible that the ncpfs utilities can't contact the server...
Maybe you haven't set the right frametypes, etc... Ahh, no, of course
you have, you're running MARS_NWE already, aren't you? Anyway, I have
been looking for a non-existing bug for a long time, I was thinking
the nwb[op]* utilities that came with RHL6.1 didn't work anymore, but
I forgot that my client system, doesn't create an IPX device at
startup. It wasn't a bug.... Interesting, isn't it??? NOT!
Q: SMArT, why on earth do you call it SMArT?
A: Well, you know SWAT, the webconfig tool for SaMBa? I changed that name a
little bit, Simple MARS_NWE Administration tool instead of Samba Web
Administration Tool. I don't think SMAT is a good name, so let's call it
SMArT! Please don't forget the lower case r...
Q: Help! My client can't contact the SMArT server...
A: I have had this problem too, and at my place, it was because of the
knfsd NFS server, it likes to use the port 902, sometimes, but
that's the SMArT port... You can solve this by changing the port
number, in the /etc/services file. Just look for a line like this:
smart 902/tcp
and change the number 902 into something else.