samba - Jul 1999 - Samba shares accessible from Win98 but not WinNT

The subject line says it all really.  I'm running Samba 2.0.4.b on FreeBSD,
sharing a tree as I normally do (we use samba on about a dozen machines so
I'm reasonably familiar with it).  This one particular machine is not
accessible from Windows NT Workstation 4.0 clients.  It works fine for
Windows 95 and Windows 98 clients.

The machine does not show up in the Network Neighborhood for anyone - that
part is understandable, it is on a different subnet.  Using Find->Computer
on *some* NT boxes detects the computer, but on other NT boxes it doesn't
even find it.

If the NT box can find it, opening it gets the "\\flaya is not accessible,
the network path was not found" error message.

Any ideas?  Let me know if you need more information.  Thanks.




Jon Drukman
Director Of Technology
GameSpot

On Fri, 2 Jul 1999 23:10:54 +1000 samba@samba.org wrote
 concerning 'SAMBA digest 2152':
> The subject line says it all really.  I'm running Samba 2.0.4.b on
FreeBSD,
> sharing a tree as I normally do (we use samba on about a dozen machines so
> I'm reasonably familiar with it).  This one particular machine is not
> accessible from Windows NT Workstation 4.0 clients.  It works fine for
> Windows 95 and Windows 98 clients.
> 
> The machine does not show up in the Network Neighborhood for anyone - that
> part is understandable, it is on a different subnet.  Using
Find->Computer
> on *some* NT boxes detects the computer, but on other NT boxes it
doesn't
> even find it.
> 
> If the NT box can find it, opening it gets the "\\flaya is not
accessible,
> the network path was not found" error message.
> 
> Any ideas?  Let me know if you need more information.  Thanks.
I had a similar problem, tracked it down eventually to bad hostname
resolution.  Once I added the server to lmhosts
(/winnt/system32/drivers/etc from memory) it worked ok, even showed up 
on the other subnet (using remote announce).  So I'd either try that,
or make sure you have either wins or valid dns hostname resolution.

Cheers,

Dan

Dan Boger - Georgetown Institute for Cognitive and Computational Sciences
dan@giccs.georgetown.edu                                     ICQ: 1130750
Georgetown University Medical Center                       Washington, DC

Sounds like a plain text password issue.  See the document ENCRYPTION.txt
in the docs/textdocs directory.