SAMBA, swat, Windows connection

[cgswong]

I've installed SAMBA and configured it (or at least I think I have), but still can't connect via my Windows PC on my domain. Each time I get an error about "The account is not authorized to login from this station". Though I can log in from the same server. I also can not get SWAT to start even though I've made the changes to the /etc/services and /etc/inetd.conf files.

Please Help! How do I set-up SAMBA to connect from Windows on a domain (need a step by step straight-forward guide) and start SWAT?

Thanks much.

 

[Igaduma]

Hi,

I'm just running samba on map-everything-to-guest account. Can't be bothered to configure it for usernames & rights & such.
Only serving 40 people or so.
Got samba on another machine sharing printers from an ultra10 to NT network.
Is it running when you boot up ?
Create a test share & set it up to map everything to guest, that wat you bypass the username checking and you can atleast check if it's working OK that way.
Put in the IP of the wins, that way you can map to it using it's biosname.
after each change of parameters you need to restart the deamons.
Maybe post your conf file.

SWAT should work if it's correctly in the services file.
Maybe start up netscape on the localhost:901 and try to connect to it.

I

 

[jad]

if you made changes to inetd.conf, did you stop samba starting in /etc/init.d ?

if you have both running then they get confused ...

secondly do you have SWAT working, it's the easiest way to make lots of changes to the system.

thirdly have you got _any_ shares in your configuration file? (don't use the default file if you can help it ... unless you know what you're doing swat is much better than the default file)

if you are using the default file, make sure that it has the configuration directories set up correctly, if you are using the one from the companion CD it comes with a very silly default file.

the line in inetd.conf (if from the companion CD) is:

swat<tab>stream<tab>tcp<tab>nowait,400<tab>root<tab>/opt/sfw/sbin/swat<tab>swat

and /etc/services should have the line:

swat<tab>901/tcp

in it.

 

[cgswong]

Thanks guys, the problem with starting SWAT was that I had to specify "Bypass proxy for addresses" in my internet settings to start it. I've since started SWAT, configured the smb.conf file using it and got a connect working using a guest account with share security level.

However, I am still unable to only allow certain users (not necessarily a member of the 2000/NT domain, but Unix users) exclusive access (read and write) to specific shares. How do I accomplish this please?

Thanks.

 

[jad]

umm, is the question pertaining to controlling access of users accessing the disk not via samba? i.e. the unix users accessing the disk directly?

this is a much harder thing to do, and you'll need more unix skills to do this ... plus file locks in samba and file locks in the unix system don't always work well together ...

for instance we have staroffice on solaris, and staroffice on windows ... if windows opens the file, then no other windows box can access it as writable. if solaris opens the file it is 'helpful' and doesn't lock the file (keeps a copy in memory) so that others can access it easily at the same time.

is this the question you were asking?