samba - Feb 2005 - rpc trust gives NT_STATUS_INVALID_HANDLE with 3.0.11

When I try to establish a trust from SAMBA 3.0.11 to Windows 2003 I get the 
error: NT_STATUS_INVALID_HANDLE. I have no problem the other way. I had no 
problem either, when I ran SAMBA 3.0.9, and the problem disappeared when I 
down-graded to 3.0.9.

Here is what happens ('CALYPSO' is the Windows-server and
'KONTOR' is its
domain-name):

[root@linux /root]# net rpc trustdom establish kontor
Password:
Could not connect to server CALYPSO
[2005/02/16 17:20:27, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
  cli_pipe: return critical error. Error was NT_STATUS_INVALID_HANDLE
[2005/02/16 17:20:27, 0] utils/net_rpc.c:rpc_trustdom_establish(4560)
  WksQueryInfo call failed.

When run with SAMBA 3.0.9 the sentence 'Could not connect to server
CALYPSO'
is also given, but the trust is established anyway.

SAMBA is compiled from the SRPM-package on Redhat 7.1. Windows 2003 is 
upgraded with all current security-updates.

Thorkil Olesen wrote (samba Digest, Vol 26, Issue 26):
> Date: Wed, 16 Feb 2005 17:11:16 +0000 (UTC)
> From: Thorkil Olesen <thorkil@pip.dknet.dk>
> Subject: [Samba] rpc trust gives NT_STATUS_INVALID_HANDLE with 3.0.11
> 
> When I try to establish a trust from SAMBA 3.0.11 to Windows 2003 I get the
> error: NT_STATUS_INVALID_HANDLE. I have no problem the other way. I had no 
> problem either, when I ran SAMBA 3.0.9, and the problem disappeared when I 
> down-graded to 3.0.9.
> 
> Here is what happens ('CALYPSO' is the Windows-server and
'KONTOR' is its
> domain-name):
> 
> [root@linux /root]# net rpc trustdom establish kontor
> Password:
> Could not connect to server CALYPSO
> [2005/02/16 17:20:27, 0] rpc_client/cli_pipe.c:rpc_api_pipe(435)
>   cli_pipe: return critical error. Error was NT_STATUS_INVALID_HANDLE
> [2005/02/16 17:20:27, 0] utils/net_rpc.c:rpc_trustdom_establish(4560)
>   WksQueryInfo call failed.
> 
I get exactly the same error message when trying to build a trust from
Samba 3.0.11 (samba.org binaries on Debian, using ldap backend) to
Windows NT 4.0.
I see EventID 537 on the NT 4.0 Server (An error occured during
logon...) which is different from what I get when I enter a wrong
trust password.

Any hints?

Using --debug=10 gives me a lot of output. I'm not sure whether
I should post that to this list.

-- 
Wolfgang Ratzka  Phone: +49 6421 2823531  FAX: +49 6421 2826994
Uni Marburg,  HRZ, Hans-Meerwein-Str., D-35032 Marburg, Germany
          http://www.uni-marburg.de/hrz/mitarbeiter/ratzka.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wolfgang Ratzka wrote:

| I get exactly the same error message when trying to build a trust from
| Samba 3.0.11 (samba.org binaries on Debian, using ldap backend) to
| Windows NT 4.0.
| I see EventID 537 on the NT 4.0 Server (An error occured during
| logon...) which is different from what I get when I enter a wrong
| trust password.

Patch is at http://www.samba.org/~jerry/patches/post-3.0.11/





cheers, jerry
====================================================================Alleviating
the pain of Windows(tm)      ------- http://www.samba.org
GnuPG Key                ----- http://www.plainjoe.org/gpg_public.asc
"I never saved anything for the swim back."     Ethan Hawk in Gattaca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCLKBvIR7qMdg1EfYRAk0/AKDF9PPJUUQ8+cQobonNmZv2QVyYWgCfTiUH
QUdwI9POV6KWPn+h5vxNk/g=LwZi
-----END PGP SIGNATURE-----

Gerald (Jerry) Carter wrote:
> Wolfgang Ratzka wrote:
> 
> | I get exactly the same error message when trying to build a trust from
> | Samba 3.0.11 (samba.org binaries on Debian, using ldap backend) to
> | Windows NT 4.0.
> | I see EventID 537 on the NT 4.0 Server (An error occured during
> | logon...) which is different from what I get when I enter a wrong
> | trust password.
> 
> Patch is at http://www.samba.org/~jerry/patches/post-3.0.11/
> 
I decided to go for the bleeding edge and built debian packages from
3.0.12-pre1, which as far as I can see contains the patch. I now get:

Could not connect to server NTRZ04
[2005/03/08 23:14:51, 0] rpc_parse/parse_prs.c:prs_mem_get(537)
   prs_mem_get: reading data of size 4 would overrun buffer.
[2005/03/08 23:14:51, 0] utils/net_rpc.c:rpc_trustdom_establish(4566)
   WksQueryInfo call failed.


(I can produce more output, if necessary.)

Regards,
Wolfgang