This bug was reported to me as http://qa.mandrakesoft.com/show_bug.cgi?id=14668

I have reproduced it as follows:

I had an existing Windows NT4SP6 Server (winnt4) serving the domain NT4, and a
Windows 2003(no service pack) Server (win2k3) serving the domain HP441
(hp441.co.za).

I subsequently established a trust relationship between these two domains, with
NT4 as the trusted domain, HP441 the trusing domain (ie "External" trust on win2k3).

I then logged in to a Windows 98SE host (virual in Win4Lin) which was setup for
"Domain Logons" to NT4, as a user in the NT4 domain (ntuser1) and could access
shares (ie NETLOGON) on win2k3.

I then migrated the NT4 domain to the samba server (host hp441node107 running
3.0.10-0.1.100mdk on Mandrake Corporate Desktop 3 - which is basically 10.0 with
updates), and disabled the relevant services on winnt4.

I then logged in to the win98 host as ntuser1 again, but could not access the
shares on win2k3 (although I could access all shares on the samba server, and
could also access the shares on win2k3 via smbclient using the NT4 domain
account ntuser1).

I stopped samba on the samba server on node107, started the relevant services on
winnt4, logged into the win98 host as ntuser1 again, and could again access the
shares on win2k3.

I will attach dumps from the win2k3 server which were made when accessing (or
trying to) win2k3 from the win98 client, samba.cap when samba was running as the
NT4 DC, winnt4.cap when NT4 was running the relevant services).

I can provide additional logs if necessary (however at some stage I need to
restore node107 to its usual status ...).

Please note the original bug reported that 3.0.13 was still affected by this.