samba - Jan 1999 - Config problem

I'm using 1.9.18p7 with RedHat 2.0.35
----------------------
/etc/smb.conf contains

[global]
hosts allow = myhost
-------------------------
/etc/lmhosts contains

myhost's-IP-address    myhost
------------------------------------
smbd and nmbd are run as daemons.

When I run smbclient //myhost/tmp, I get 'not listening for calling
name',
but if I specify hosts allow = myhost's-IP-address it works OK. Why does it
resolve myhost on the command line but not in the .conf file?

Thanks,

Steve Cabito
=======

I am running samba (4.0.4b) on a Sun/Solaris (7) box that provides file and 
printer services to a single Win/NT (4.0 SP5) box.  That box just died, and 
I brought in a new box that is almost identically configured to the old one 
(same IP address, name, and workgroup).  For reasons beyond myself and two 
cohorts, I cannot access anything on the unix box from the new NT 
box.  Only change made on the unix side was to the ethers file to map IP to 
cardID.

Best example of what happens is:

1.  Go into explorer and click on the unix server name under NetHood
2.  Dialog box comes up complaining about name and/or password and asks for 
both.
3.  Both are entered (using same name/password used with old box).
4.  Error box comes up with
     \\SERVER is not accessible
     The account is not authorized to login from this station

I ran a snoop on the server during one attempt, and it looks like the NT 
box terminates the interaction at the point where it should be sending the 
name and password back to the unix box (we compared with a snoop running on 
a healthy network).

If I try to use smbclient from the unix end (smbclient -L ntname) I get a 
"session setup failed: ERRDOS - ERRnoaccess" denial.

I'm sure this is something simple and stupid, but I've already lost a
day
to it.  Any help is greatly appreciated.  (Yes, I've waded through the 
DIAGNOSTICS.txt suggestions - no help there.)  Both NT and unix boxes have 
gone through several ground-up reboots, so there are no hanging zombies 
anywhere.  Again, this was working fine on another machine that (I think) 
had at least the TCP/IP stuff configured identically to the new one.

Jim
*---------------------*-------------------------------*
| Jim Secan           | Northwest Research Assoc, Inc |
| (jim@nwra-az.com)   | 9040 S Rita Road, Suite 2214  |
| (520) 663-3570      | Tucson, Arizona 85747         |
|                     | http://www.nwra-az.com/       |
*---------------------*-------------------------------*

Should have noted in my first e-mail that I have made the necessary changes 
to the NT registry to permit plain-text passwords.  In any event, it 
doesn't look like the username/password even makes it to samba (this from 
looking at the snoop results and at the log file with level=10).

Jim
*---------------------*-------------------------------*
| Jim Secan           | Northwest Research Assoc, Inc |
| (jim@nwra-az.com)   | 9040 S Rita Road, Suite 2214  |
| (520) 663-3570      | Tucson, Arizona 85747         |
|                     | http://www.nwra-az.com/       |
*---------------------*-------------------------------*