[Samba] PCs can't login to replacement PDC

sam...@nym.hush.com

unread,

Dec 9, 2013, 12:40:02 PM12/9/13

to

I’m still struggling to swap PCs to a replacement PDC.

Is there a way to reset the machine account (trust relationship)
between an existing PC (Windows XP) and a replacement PDC with the
same settings as the original PDC? I think it works if I take the
PC off the domain by setting it to a workgroup and then put it back
onto the domain when connected to the new PDC. However, I’d feel a
lot happier if there was another way to do this!

Thanks.

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Tompkins, Michael

unread,

Dec 9, 2013, 2:00:01 PM12/9/13

to

When I run a cross-compiled version(for ppc) of smbclient with -m SMB2 parameter, I get:

Bad SMB2 signature for message
[0000] E1 90 A0 C5 31 A8 26 31 10 D8 96 CF 68 14 E9 97 ....1.&1 ....h...
[0000] CA EF F3 A8 AA C7 4D C1 05 34 39 F1 B4 7E 79 43 ......M. .49..~yC
session setup failed: NT_STATUS_ACCESS_DENIED

If I run it without the -m SMB2 parameter, everything works fine. If I run a version of 4.1.0 from my linux box(not cross-compiled) and the 4.1.2 version on my ppc platform, with the same parameters, they both look the same with the first 7 packets, in WireShark. Then the 4.1.2 version, just quits with the above message. Any help or direction is greatly appreciated.

- Mike

Jeremy Allison

unread,

Dec 10, 2013, 6:30:02 PM12/10/13

to

On Mon, Dec 09, 2013 at 06:46:10PM +0000, Tompkins, Michael wrote:
> When I run a cross-compiled version(for ppc) of smbclient with -m SMB2 parameter, I get:
>
> Bad SMB2 signature for message
> [0000] E1 90 A0 C5 31 A8 26 31 10 D8 96 CF 68 14 E9 97 ....1.&1 ....h...
> [0000] CA EF F3 A8 AA C7 4D C1 05 34 39 F1 B4 7E 79 43 ......M. .49..~yC
> session setup failed: NT_STATUS_ACCESS_DENIED
>
> If I run it without the -m SMB2 parameter, everything works fine. If I run a version of 4.1.0 from my linux box(not cross-compiled) and the 4.1.2 version on my ppc platform, with the same parameters, they both look the same with the first 7 packets, in WireShark. Then the 4.1.2 version, just quits with the above message. Any help or direction is greatly appreciated.

To debug this - first run an x86 smbclient version against
Windows and Samba on little-endian x86 - that
should (obviously) work.

Next run your cross-compiled version against Windows and
Samba on little-endian x86. Does it work against both ? If
it works against Windows but not against Samba then that's
a little trickier. But if it fails against both then use
the (known correct) Samba server code to debug your
client implementation, one crypto step at a time (using
printf debug statements).

Hope this helps,

Jeremy.

Tompkins, Michael

unread,

Dec 12, 2013, 12:30:02 PM12/12/13

to

In addition to this question, I noticed there are 2 versions: smbclient and smbclient4. For 4.x, should we use the smbclient4. When I run this, my output is different:

dos charset 'CP850' unavailable - using ASCII
Connection to \\13.121.10.166\ScanRepo failed - NT_STATUS_REVISION_MISMATCH

Regards,
- Mike

-----Original Message-----
From: Tompkins, Michael
Sent: Monday, December 09, 2013 1:46 PM
To: sa...@lists.samba.org
Cc: USA Xerox Samba
Subject: smbclient 4.1.2 with -m SMB2 gives Bad SMB2 signature for message

When I run a cross-compiled version(for ppc) of smbclient with -m SMB2 parameter, I get:

Bad SMB2 signature for message
[0000] E1 90 A0 C5 31 A8 26 31 10 D8 96 CF 68 14 E9 97 ....1.&1 ....h...
[0000] CA EF F3 A8 AA C7 4D C1 05 34 39 F1 B4 7E 79 43 ......M. .49..~yC
session setup failed: NT_STATUS_ACCESS_DENIED

If I run it without the -m SMB2 parameter, everything works fine. If I run a version of 4.1.0 from my linux box(not cross-compiled) and the 4.1.2 version on my ppc platform, with the same parameters, they both look the same with the first 7 packets, in WireShark. Then the 4.1.2 version, just quits with the above message. Any help or direction is greatly appreciated.

- Mike

Jeremy Allison

unread,

Dec 12, 2013, 12:40:02 PM12/12/13

to

On Tue, Dec 10, 2013 at 08:47:02PM +0000, Tompkins, Michael wrote:
> In addition to this question, I noticed there are 2 versions: smbclient and smbclient4. For 4.x, should we use the smbclient4. When I run this, my output is different:

Don't use smbclient4. It's test code only.

When you "make install" the installed smbclient is just
smbclient, so use that.

Tompkins, Michael

unread,

Jan 8, 2014, 3:40:01 PM1/8/14

to

I can't seem to reliably get samba 4.1.0 to cross compile. I seem to be stuck at:

default/source4/heimdal/lib/gssapi/asn1_gssapi_asn1.c:23: error: expected ';', ',' or ')' before 'HEIMDAL_UNUSED_ATTRIBUTE'

The samba4 directory seems to be causing me issues. All I need to compile is smbclient! Is there a way I can just do that?

Regards,
- Mike

-----Original Message-----