How to change small network domain name with minimimal cli..

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

I think I have things all botched up. I currently have a small
network
at home with ~5 clients and 2 domains, each with just one PDC, no
BDC's. I did this to learn and experiment.


Anyway, the main problem I have is I cannot see anything in the domain
from a security standpoint, just users local to any given client.
Secondly, I always get netlogon errors on the event log:


Event ID: 5719
No Domain Controller is available for domain MY_DOMAIN due to the
following:
There are currently no logon servers available to service the logon
request. .
Make sure that the computer is connected to the network and try again.
If the problem persists, please contact your domain administrator.


So, what I thought would be best is to get rid of the second domain
(OTHER), and then use the PDC for that domain as a BDC for MY_DOMAIN.
Also, I want to change the name from MY_DOMAIN to HOUSE, as I have
heard that having underscores in domain names can be a bad thing.


So, all this being said, what would be the best way to attack this?
Everybody that logs in, logs into the domain MY_DOMAIN at this point.
Will they lose all their local settings when I am done renaming the
domain? Will I have to recreate all the users? What impact will it
have on them?


-Jim

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Start here

Try running netdiag, repadmin and dcdiag. Look for fail, error and warning
errors.

If you don't have the tools installed load them from your install disk.

d:\i386\adminpak.msi (Server tools for remote management of servers)
d:\support\tools\setup.exe (Server Utilities)

Copy the following to a cmd file and run look for error, fail and warn
within the reports. Post any errors you can't figure out. make sure you
modify DC_Name to the name of a dc in your domain.

@echo off

c:
cd \
cd "program files\support tools"

del c:\dcdiag.log
dcdiag /e /c /v /sC_Name /f:c:\dcdiag.log
start c:\dcdiag.log

netdiag.exe /v > c:\netdiag.log
start c:\netdiag.log

repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
start c:\repl.txt


See for more details

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/1d4ce93c-54f2-4069-a708-251509c38837.mspx

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


"jtpr" <bogus@bogus.com> wrote in message
news:1125410883.78ec7692663b202edebca825f4586c40@bubbanews...
>
>
> I think I have things all botched up. I currently have a small
> network
> at home with ~5 clients and 2 domains, each with just one PDC, no
> BDC's. I did this to learn and experiment.
>
>
> Anyway, the main problem I have is I cannot see anything in the domain
> from a security standpoint, just users local to any given client.
> Secondly, I always get netlogon errors on the event log:
>
>
> Event ID: 5719
> No Domain Controller is available for domain MY_DOMAIN due to the
> following:
> There are currently no logon servers available to service the logon
> request. .
> Make sure that the computer is connected to the network and try again.
> If the problem persists, please contact your domain administrator.
>
>
> So, what I thought would be best is to get rid of the second domain
> (OTHER), and then use the PDC for that domain as a BDC for MY_DOMAIN.
> Also, I want to change the name from MY_DOMAIN to HOUSE, as I have
> heard that having underscores in domain names can be a bad thing.
>
>
> So, all this being said, what would be the best way to attack this?
> Everybody that logs in, logs into the domain MY_DOMAIN at this point.
> Will they lose all their local settings when I am done renaming the
> domain? Will I have to recreate all the users? What impact will it
> have on them?
>
>
> -Jim
>
>
>