samba - Oct 1998 - Password authentication across sub-nets.

It would appear that Samba <-> Samba across subnets works fine, but Samba
<-> NT is a problem.
Does anybody else concur with this statement?

Specifically, running Samba 1.9.18p10 (Solaris) and directing all password
authenication to an NT server
on a subnet causes the following output in the log file:

---------------------------------------------------------------------------
------------
Requested protocol [PC NETWORK PROGRAM 1.0]
Requested protocol [MICROSOFT NETWORKS 3.0]
Requested protocol [DOS LM1.2X002]
Requested protocol [DOS LANMAN2.1]
Requested protocol [Windows for Workgroups 3.1a]
Requested protocol [NT LM 0.12]
Connecting to 161.102.144.9 at port 139
connected to password server 161.102.144.9
161.102.144.9 rejected the session
Selected protocol NT LM 0.12
1998/10/16 16:59:24 Transaction 2 of length 158
switch message SMBsesssetupX (pid 15470)
Domain=[ENG]  NativeOS=[Windows 4.0] NativeLanMan=[Windows 4.0]
sesssetupX:name=[MUNNS]
Scanning username map /usr/local/samba/lib/users.map
password server  is not connected
SMB Password - pwlen = 24, challenge_done = 1
Checking SMB password for user munns (l=24)
get_smbpwd_entry: end of file reached
Couldn't find user munns in smb_passwd file.
1998/10/16 16:59:24 error packet at line 644 cmd=115 (SMBsesssetupX)
eclass=2 ecode=2
error string = No such file or directory
end of file from client
Closing connections
---------------------------------------------------------------------------
---------------

Can anybody else confirm this behaviour, if so, is it a bug or
mis-configuration?
(BTW This works fine if the NT and Samba server are on the same subnet)

Thanks in advance
Neil Davis

Email: neil@tectonic.co.uk

You wrote:
> It would appear that Samba <-> Samba across subnets works fine, but
Samba
> <-> NT is a problem.
[snip]
> Connecting to 161.102.144.9 at port 139
> connected to password server 161.102.144.9
> 161.102.144.9 rejected the session
	That sounds a bit like the NT server didn't think it
	should let the remote Samba server ``log in''.  One
	of the things you need to guarantee if you're using 
	security = server is that the NT box will allow
	people to log in **as if they're users on the Samba
	server**.

	This may be part of your problem.

--dave
-- 
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | davecb@hobbes.ss.org, canada.sun.com
N2M 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb

> > Connecting to 161.102.144.9 at port 139
> > connected to password server 161.102.144.9
> > 161.102.144.9 rejected the session
> 
>         That sounds a bit like the NT server didn't think it
>         should let the remote Samba server ``log in''.  One
Also make sure that the "password server = NetBIOS_name_of_PDC"
and not the IP address.





j- 
________________________________________________________________________
                            Gerald ( Jerry ) Carter	
Engineering Network Services                           Auburn University 
jerry@eng.auburn.edu             http://www.eng.auburn.edu/users/cartegw

       "...a hundred billion castaways looking for a home."
                                  - Sting "Message in a Bottle" ( 1979
)