Installing TCP/IP, DNS, DHCp, WINS

[chomite]

I installed NT 4 server, and made a LAN network somehow got it working. I currently have the NT4 as the main server and XP as the part of it. But problem arised as I changed the domain and computer name and everything screwed up.

I have no problem go into NT4 server comptuer using XP. But When I tried otherwise, the error occurs which says i have no trustrelationship between the XP and NT4. And I tried to establish one and it says domain controller not found.

I got an answer from one guy. He siad that I should reinstall TCP/IP, then DNS, DHCP, and WINS services on the NT server that is my domain controller and configure them appropriately. How do I do that?

p.s.1 will it help just format the harddisk and reinstall the NT4?

Edited May 25, 2006 by chomite

[Zartach]

On NT4 you dont really want to rename the domaincontroller or the domain, its just too inconvenient in my experience.

You can reinstall the services via the control -> panel software -> windows components. i believe. been a while since i installed one tho and i dont have a VM running NT4 at the moment.

However, you might want to try simple solutions first like dropping the computeraccount from the domain and rejoin the Winxp machine into the domain.

You should also check WINS via the administrative tools to check if the addresses are set up correctly, WINNT does not lean heavily on DNS though so it should not generate too mutch problems. But you can always change the configuration via the DNS tool.

for WINS i believe you should see the servername and the domainname pointing to your server IP address, i cant remember any other requirements at the moment.

Nothing should have changed in the TCP/IP configuration except for the name of the server but you can check the TCP/IP via the properties of the netword card.

But as i said it may all be simple and you may just need to rejoin the PC to the domain.

[cluberti]

Well, considering that renaming DCs in NT4 is unsupported (because it breaks the trust between the server and the domain), I'm not surprised things are failing. DC renames are only supported in AD, and domain renames are only supported in 2003 AD. You're going to have to kill the old domain and create a new one before things start working properly again, I'm afraid.