I've just configured a samba 2.5 on a box running redhat 7.1. The box's name is linuxweb.

My problem is this when I click on linuxweb (or access it from run on the start menu) I get a enter network password dialog box. When I enter the username of amiller (which is listed as a valid user) I get the following message:

\\linuxweb is not accessible
the account is not authorized to login from this station.

My hosts allow = 127.0.0.1 10.186.32.44 10.186.32.

I am attempting to access linuxweb from an NT4 box addressed as 10.186.32.44.

Does anyone know what the problem is?

Make sure the user is both a local user(i.e. in /etc/passwd and also a Samba user ( smbpasswd -a amiller ). Then try to log in to the share.

tarballedtux,

thanks for the response, but unfortunately, your solution didn't help. any other ideas?

try putting in the name of the machine, I remember that Unix sees 127.0.0.1 and machine name as different things. Can you login as root from that machine ?, can you ping the Linux box from your NT 4 machine ?, if yes to both then in your samba settings allow all users, login as your user account, if it works then it's something to do with users. If not then your problem lies else where. Make sure your firewall allows connections, can you administer the Samba Linux off the NT 4 machine using the browser ? (Web config).. Anyhow's good luck.

Quoting from the portmapper man page:

Access control
By default, host access control is enabled. However, the host that runs
the portmapper is always considered authorized. The host access control
tables are never consulted with requests from the local system itself;
they are always consulted with requests from other hosts.

In order to avoid deadlocks, the portmap program does not attempt to look
up the remote host name or user name, nor will it try to match NIS net-
groups. The upshot of all this is that only network number patterns will
work for portmap access control.

Sample entries for the host access-control files are:

/etc/hosts.allow:
portmap: your.sub.net.number/your.sub.net.mask
portmap: 255.255.255.255 0.0.0.0

/etc/hosts.deny
portmap: ALL

The syntax of the access-control files is described in the
hosts_access(5) and hosts_options(5) manual page that comes with the tcp
wrapper (log_tcp) sources. The safe_finger command comes with later wrapper releases.

The first line in the hosts.allow file permits access from all systems within your own subnet. Some rpc services rely on broadcasts and will contact your portmapper anyway; and once an intruder has access to your local network segment you're already in deep trouble.

The second line in the hosts.allow file may be needed if there are any
PC-NFS systems on your network segment.

And quoting from the hosts_access manpage:

ACCESS CONTROL
allow

deny Grant (deny) service. These options must appear at the end of a rule.

The allow and deny keywords make it possible to keep all access control rules
within a single file, for example in the hosts.allow file.

To permit access from specific hosts only:

ALL: .friendly.domain: ALLOW
ALL: ALL: DENY

To permit access from all hosts except a few trouble makers:

ALL: .bad.domain: DENY
ALL: ALL: ALLOW

Notice the leading dot on the domain name patterns.

you're not going to believe this!

i changed encrypted = no to yes, and now i have connectivity!

thanks for all your help!

If your all talking about samba, sure it believe it
In order for samba to acccept windows password that has
to be set in smb.conf.

Keep in mind you also have to use smbpasswd
to create smb login for each user, and keep password
synced betwen win and samba.