: > but when I reboot into NT, I consistently
: > get "The account is not authorized to log on from this station."
: > The smbd is version 1.9.17p4. All other activity (ftp, telnet,
: > etc) work between the machines, no problem. No hosts.allow or
: > hosts.deny problems. **And the Linux box can smbmount the NT
: > machine!**
: I am getting this *exact* error message myself, with the very latest RPM
: of Samba from their website: samba-1.9.18p3-50.2.i386.rpm (this a RH5
: box). The NT box is NT4WS, with SP3 and IE4. The two boxes can see each
: other just fine for telnet and ping.
: The Samba share does not show in Network Neighborhood, but if I enter
: the server name manually -- "\\burns\" (minus the quotes), I get a 30-60
: sec. delay, then a username/password request (username and password are
: identical on both boxes), another 15-30 sec. delay, and then the same
: error you posted (the first mention of the error message I've been able
: to find). I get the same results if I use a FQDN too. Running the tests
: in Diagnostics.txt that came with the Samba rpm gave the following
: results: complete success until it came to "net use x: \\BIGSERVER\TMP",
: where I returned to my original error message. hosts/allow & hosts/deny
: are fine. The NT box is listed in my smb.conf hosts allow line.
One problem that comes up alot in NT to Samba Communication is a problem
that Service Pack 3 introduced. It has to do with Plain Text Authorization
try the following fix (posted a while back by tim somehting can't remember
the guys name) and see if it solves your problem:
Run regedt32 (not regedit)
From the HKEY_LOCAL_MACHINE subtree, go to:
Click Add Value on the Edit menu.
Value Name: EnablePlainTextPassword
Data Type: REG_DWORD
Exit and reboot; it should work now.
Puritanism: The haunting fear that somehow,
somewhere, someone may be happy