How to change small network domain name with minimimal client impact?
- From: jtpr <bogus@xxxxxxxxx>
- Date: Tue, 30 Aug 2005 11:16:47 -0400
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
.
- Prev by Date: Domain Authentication Problem
- Next by Date: Raise DC functionality ?
- Previous by thread: Domain Authentication Problem
- Next by thread: Raise DC functionality ?
- Index(es):
Relevant Pages
|
