Re: trying to create trusts on NT4 domain and 2003 domain

Tech-Archive recommends: Fix windows errors by optimizing your registry

Ok I think I have got a bit further with this. I have managed to configure
the TRUSTING domain on the NT4 box

I see the new domain is showing up as mycompany not mycompany.local so I am
guessing it's not necessay for me to input .local part of the name. Hence
there is now enough characters space to input the new domain name into the
add trusted domain box .

However, when I try to add trusted domain on the NT4 box it comes up with
the 'could not find domain controller for this domain.'
The NT4 machine can 'see' the new domain if I browse servers on network.



"-keevill-" <keevill@xxxxxxxxx> wrote in message
news:%23sopbTtlIHA.6032@xxxxxxxxxxxxxxxxxxxxxxx
I fear I am going to be around this NG for a few more days yet seeking
assistance.
I have an NT4 server for a domain with 40+ winxp/2000 clients.
I now want to migrate over to new hardware and Win2003 domain.

I have bought a new server machine on which I have installed win 2003
server. This has been configured as a domain controller - name of new
domain is mycompany.local

The old NT4 domain is My_Company.

I am trying to create trusts from each domain to the other.
On the new 2003 server I try to set up a two way directional trust /
domain-wide authentication . I do not confirm the outgoing trust since the
other side on the NT4 server has not yet been done. I get a successful
trust created message.

Now when I go over to the NT4 server to create the trust the other way, I
go to trust relationships/ add trust then I have insufficient character
space to input 'mycompany.local' .
I have tried just inputting 'mycompany' but that just brings up domain not
found errors.
What am I doing wrong ?




.

Relevant Pages

  • Re: Trust creatation with NT4 and 2003AD
    ... > Have successfully created "trusting" trust on NT4 ... You don't need both (Lmhosts AND WINS Server) if you do ... LMhosts is tedious, easy to mess up, and difficult to maintain ...
    (microsoft.public.windows.server.migration)
  • RE: Migration NT4 to W3K AD
    ... The netdom command is now working also netdom verify. ... software loaded on the NT4 server that i have uninstalled. ... verify the trust from the command line does not work like i wrote earlier. ...
    (microsoft.public.windows.server.active_directory)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... For Windows 2000 and 2003 these settings may be applied/configured via ... Digitally sign communications (if server ... With NT4 the only way to verify the settings is with the Regedt32 tool. ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)
  • Re: pcanywhere routing question
    ... The nt4 machine is not upgradable due to software running on it. ... > The server Internal nic ip is lets say 192.168.10.2, ... > routing and remote access in a 2 nic situation. ...
    (microsoft.public.windows.server.sbs)
  • Re: creating trust relationship
    ... I have an article on this for NT4 to 2003 which you may want to take a look ... I have Forest A trying to create a ... I can ping both PDCs from the opposite server. ... created the trust on both sides. ...
    (microsoft.public.windows.server.active_directory)