Hi guys ,

I have worked hard at trying to get samba run .. but heck!.. it doesn't !

I can see the linux server in my network neighbourhood ..
on clicking on it .. I get the user/password box. I entered the user(xyz) password(abc) , and it says ... "account is not authorised to login from this station"

I have added user 'xyz' using the smbadduser and set the password as (abc).

Ahh .. I had logged in as 'pqr' on this nt box ..is that the problem ?? ..do I need to relogin as xyz ?? .. let me see .. changing login to xyz .. hang on ..

.. okay I treid that as well ..doesnt work !

where am I going wrong ? I'm sure its something very simple ! samba config can't be this difficult ..

can somebody send me a copy of a working smb.conf and maybe if possible a list of todo's to get the samba working .. please?

thanks for your time
Ashwin



[Edited by ashpai on 03-08-2001 at 04:35 AM]

Try creating entries on your /etc/hosts file on your Linux server for the boxes you are trying to connect from.
Also, make sure that Samba is using encrypted passwords unless you have altered Windows to send plain text.
You can try adding an entry in the LMHOSTS file on the Windows box for the Linux server as well.


check http://www.linuxdoc.org for the SMB HOW-TO

I'm in a similar boat. But most of the time everything works real sweet-like. Except when I loose my connection to the internet, then I lose my local area network as well. (Thouhts, hints suggestions?)

My network is small. 4 win2k Pro boxes thtat share files off of a samba (Redhat 7.0 samba veriosn 2.07) server that is also my gateway.

Anybody else have this problem?

El

Same on me,
I tried both encrypted and non-encrypted and got same result. I did changed winme to plaintextpassword to use non-encrypted, still not get thing to work.

Have u tried enabling WINS Server in the smb.conf
and adding the server ip to your WINS section on the 2k boxes

Just a suggestion it worked 4 me

Everything dies when you loose your internet connection because the box can no longer perform DNS lookups and the connection will eventually hang while trying to do the lookup.

In my case what I did was start named on the linux box and configure it as a caching nameserver. Then, I made the server master for 192.168.1.in-addr.arpa as well as a fake domain such as local.domain. This will solve the problem, but I think you could also just put entries for all you hosts in /etc/hosts as suggested above. Either way should solve the problem, but I like the benefits of having a caching nameserver on my network.

-Mark