2379 – net rpc trustdom establish does not work

Bug 2379 - net rpc trustdom establish does not work

Summary: net rpc trustdom establish does not work

Status:	CLOSED FIXED

Alias:	None

Product:	Samba 3.0
Classification:	Unclassified
Component:	net utility (show other bugs)
Version:	3.0.11
Hardware:	All Linux

Importance:	P3 normal
Target Milestone:	none
Assignee:	Jim McDonough
QA Contact:	Samba QA Contact

URL:
Keywords:

Depends on:
Blocks:

Reported:	2005-02-22 09:08 UTC by TAKAHASHI Motonobu
Modified:	2005-08-24 10:18 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description TAKAHASHI Motonobu 2005-02-22 09:08:05 UTC

In Samba 3.0.11, net rpc trustdom establish <domain_name> does not work. 
Cf. in Samba 3.0,7, this command reports error but works.

(1) Samba 3.0.11
# net -d3 rpc trustdom establish rumba
[2005/02/23 01:03:03, 3] param/loadparm.c:lp_load(3898)
  lp_load: refreshing parameters
[2005/02/23 01:03:03, 3] param/loadparm.c:init_globals(1314)
  Initialising global parameters
[2005/02/23 01:03:03, 3] param/params.c:pm_process(566)
  params.c:pm_process() - Processing configuration 
file "/usr/local/samba/lib/smb.
conf"
[2005/02/23 01:03:03, 3] param/loadparm.c:do_section(3400)
  Processing section "[global]"
[2005/02/23 01:03:03, 2] lib/interface.c:add_interface(79)
  added interface ip=192.168.135.37 bcast=192.168.135.255 nmask=255.255.255.0
Password:
[2005/02/23 01:03:04, 3] libsmb/cliconnect.c:cli_start_connection(1389)
  Connecting to host=MAYUKA
[2005/02/23 01:03:04, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 445
[2005/02/23 01:03:04, 2] lib/util_sock.c:open_socket_out(789)
  error connecting to 192.168.135.120:445 (Connection refused)
[2005/02/23 01:03:04, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 139
[2005/02/23 01:03:04, 1] libsmb/cliconnect.c:cli_full_connection(1477)
  failed session setup with NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT
Could not connect to server MAYUKA
[2005/02/23 01:03:04, 3] libsmb/cliconnect.c:cli_start_connection(1389)
  Connecting to host=MAYUKA
[2005/02/23 01:03:04, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 445
[2005/02/23 01:03:04, 2] lib/util_sock.c:open_socket_out(789)
  error connecting to 192.168.135.120:445 (Connection refused)
[2005/02/23 01:03:04, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 139
[2005/02/23 01:03:04, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
  cli_pipe: return critical error. Error was NT_STATUS_INVALID_HANDLE
[2005/02/23 01:03:04, 0] utils/net_rpc.c:rpc_trustdom_establish(4560)
  WksQueryInfo call failed.
[2005/02/23 01:03:04, 2] utils/net.c:main(859)
  return code = -1

(2) Samba 3.0.7
# /usr/local/samba-3.0.7/bin/net -d3 rpc trustdom establish rumba
[2005/02/23 01:04:16, 3] param/loadparm.c:lp_load(3897)
  lp_load: refreshing parameters
[2005/02/23 01:04:16, 3] param/loadparm.c:init_globals(1307)
  Initialising global parameters
[2005/02/23 01:04:16, 3] param/params.c:pm_process(566)
  params.c:pm_process() - Processing configuration 
file "/usr/local/samba/lib/smb.
conf"
[2005/02/23 01:04:16, 3] param/loadparm.c:do_section(3390)
  Processing section "[global]"
[2005/02/23 01:04:16, 2] lib/interface.c:add_interface(79)
  added interface ip=192.168.135.37 bcast=192.168.135.255 nmask=255.255.255.0
Password:
[2005/02/23 01:04:19, 3] libsmb/cliconnect.c:cli_start_connection(1376)
  Connecting to host=MAYUKA
[2005/02/23 01:04:19, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 445
[2005/02/23 01:04:19, 2] lib/util_sock.c:open_socket_out(789)
  error connecting to 192.168.135.120:445 (Connection refused)
[2005/02/23 01:04:19, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 139
[2005/02/23 01:04:19, 1] libsmb/cliconnect.c:cli_full_connection(1464)
  failed session setup with NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT
Could not connect to server MAYUKA
[2005/02/23 01:04:19, 3] libsmb/cliconnect.c:cli_start_connection(1376)
  Connecting to host=MAYUKA
[2005/02/23 01:04:19, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 445
[2005/02/23 01:04:19, 2] lib/util_sock.c:open_socket_out(789)
  error connecting to 192.168.135.120:445 (Connection refused)
[2005/02/23 01:04:19, 3] lib/util_sock.c:open_socket_out(752)
  Connecting to 192.168.135.120 at port 139
[2005/02/23 01:04:19, 3] rpc_parse/parse_lsa.c:lsa_io_sec_qos(181)
  lsa_io_sec_qos: length c does not match size 8
Trust to domain RUMBA established
[2005/02/23 01:04:19, 2] utils/net.c:main(792)
  return code = 0

# net rpc trustdom list -U /dev/null%""
Trusted domains list:

RUMBA               S-1-5-21-623665218-473260461-945835055

Trusting domains list:

RUMBA               S-1-5-21-623665218-473260461-945835055

Comment 1 Jim McDonough 2005-02-22 10:09:24 UTC

Hmm, I'm trying to recall, because I just had this happen last week, but I did
get  it working.  What's on the other side of the trust?

What I get in current svn is the same result as 3.0.7, the error message but
then it works (this is actually correct on the wire, as it is what windows does,
too).

Comment 2 Jim McDonough 2005-02-22 10:11:52 UTC

I recall now.  We were using the wrong pipe handle index due to a pervasive
change .  Fix has already been checked in (5339 in SAMBA_3_0).

Comment 3 Gerald (Jerry) Carter (dead mail address) 2005-02-22 11:20:17 UTC

patch available at http://samba.org/~jerry/patches/post-3.0.11/

Comment 4 TAKAHASHI Motonobu 2005-02-23 06:59:50 UTC

(In reply to comment #3)
> patch available at http://samba.org/~jerry/patches/post-3.0.11/

Thanks. This patch works well in my environment.

Comment 5 Gerald (Jerry) Carter (dead mail address) 2005-08-24 10:18:17 UTC

sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.