Легенда:
 новое сообщение
 закрытая нитка
 новое сообщение
 в закрытой нитке
 старое сообщение
|
- Напоминаю, что масса вопросов по функционированию форума снимается после прочтения его описания.
- Новичкам также крайне полезно ознакомиться с данным документом.
|
Разрешилось, поднял старый дамп системного раздела, слава... 19.03.10 14:59 Число просмотров: 3971
Автор: Duke Статус: Незарегистрированный пользователь
|
|
Разрешилось, поднял старый дамп системного раздела, слава Акронису! ) Правда пришлось машины в домен передобавить, но все профили сохранились. Дело как мне кажется было в тесевых насторойках на контроллере домена..
|
|
<sysadmin>
|
Помогите по AD, не могу добавить машину в домен 18.03.10 11:41
Автор: Duke Статус: Незарегистрированный пользователь
|
Весь мозг себе уже сломал..
Вот такое сообщение вылазит:
Замечание: эта информация предназначена для сетевого администратора. Пожалуйста, сообщите эту информацию вашему сетевому администратору. Для удобства, она уже сохранена в файле "C:\WINDOWS\debug\dcdiag.txt".
Вероятно, доменное имя "MED" является NetBIOS-именем домена. Проверьте, что имя домена правильно зарегистрировано в WINS.
Если вы убеждены, что это имя не является NetBIOS-именем домена, то следующая информация поможет в исправлении ошибки в конфигурации DNS вашей сети.
DNS успешно запросила запись ресурса размещения службы (SRV), используемой для выяснения размещения контроллера домена для домена "MED":
Опрос проводился для SRV-записи для _ldap._tcp.dc._msdcs.MED
Этим запросом были идентифицированы следующие контроллеры домена:
black.med
К возможным причинам этой ошибки относятся:
1. Записи узлов (A), которые сопоставляют имя контроллера домена его IP-адресам утеряны или содержат неправильные адреса.
2. Котроллеры доменов, зарегистрированные в DNS не подключены к сети или не запущены.
Для получения подробной информации щелкните кнопку "Справка".
nslookup black.med работает!
пингуется!
nslookup med. работает
nslookup med - не работает!! Что значит эта чертова точка в конце? Может в ней дело?
Пытался переименовать домен в med.local по инструкции майкрософта, не получилось, вроде все без ошибок прошло но домен не переименовался..
Вот что говорит dcdiag на сервере:
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine black, is a DC.
* Connecting to directory service on server black.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\BLACK
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... BLACK passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\BLACK
Starting test: Replications
* Replications Check
* Replication Latency Check
......................... BLACK passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC BLACK.
* Security Permissions Check for
DC=ForestDnsZones,DC=MED
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=MED
(NDNC,Version 2)
* Security Permissions Check for
DC=ForestDnsZones,DC=med,DC=local
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=med,DC=local
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=MED
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=MED
(Configuration,Version 2)
* Security Permissions Check for
DC=MED
(Domain,Version 2)
......................... BLACK passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\BLACK\netlogon
Verified share \\BLACK\sysvol
......................... BLACK passed test NetLogons
Starting test: Advertising
The DC BLACK is advertising itself as a DC and having a DS.
The DC BLACK is advertising as an LDAP server
The DC BLACK is advertising as having a writeable directory
The DC BLACK is advertising as a Key Distribution Center
The DC BLACK is advertising as a time server
The DS BLACK is advertising as a GC.
......................... BLACK passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
Role Domain Owner = CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
Role PDC Owner = CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
Role Rid Owner = CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
Role Infrastructure Update Owner = CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
......................... BLACK passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1604 to 1073741823
* black.med is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1104 to 1603
* rIDPreviousAllocationPool is 1104 to 1603
* rIDNextRID: 1165
......................... BLACK passed test RidManager
Starting test: MachineAccount
Checking machine account for DC BLACK on DC BLACK.
* SPN found :LDAP/black.med/MED
* SPN found :LDAP/black.med
* SPN found :LDAP/BLACK
* SPN found :LDAP/black.med/MED
* SPN found :LDAP/d7d88c83-407d-4183-93b1-86c6d027659e._msdcs.MED
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/d7d88c83-407d-4183-93b1-86c6d027659e/MED
* SPN found :HOST/black.med/MED
* SPN found :HOST/black.med
* SPN found :HOST/BLACK
* SPN found :HOST/black.med/MED
* SPN found :GC/black.med/MED
......................... BLACK passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... BLACK passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
BLACK is in domain DC=MED
Checking for CN=BLACK,OU=Domain Controllers,DC=MED in domain DC=MED on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED in domain CN=Configuration,DC=MED on 1 servers
Object is up-to-date on all servers.
......................... BLACK passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... BLACK passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... BLACK passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... BLACK passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 14:38:01
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 14:38:01
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 14:51:32
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 14:51:32
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 14:56:08
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 14:56:08
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:00:58
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:00:58
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:00:59
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:01:06
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:01:07
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:35:00
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:35:00
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:35:00
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 03/17/2010 15:35:00
(Event String could not be retrieved)
......................... BLACK failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=BLACK,OU=Domain Controllers,DC=MED and backlink on
CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
are correct.
The system object reference (frsComputerReferenceBL)
CN=BLACK,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=MED
and backlink on CN=BLACK,OU=Domain Controllers,DC=MED are correct.
The system object reference (serverReferenceBL)
CN=BLACK,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=MED
and backlink on
CN=NTDS Settings,CN=BLACK,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=MED
are correct.
......................... BLACK passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : MED
Starting test: CrossRefValidation
......................... MED passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... MED passed test CheckSDRefDom
Running enterprise tests on : MED
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... MED passed test Intersite
Starting test: FsmoCheck
GC Name: \\black.MED
Locator Flags: 0xe00003fd
PDC Name: \\black.MED
Locator Flags: 0xe00003fd
Time Server Name: \\black.MED
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\black.MED
Locator Flags: 0xe00003fd
KDC Name: \\black.MED
Locator Flags: 0xe00003fd
......................... MED passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
Куда смотреть, что делать?
|
|
Разрешилось, поднял старый дамп системного раздела, слава... 19.03.10 14:59
Автор: Duke Статус: Незарегистрированный пользователь
|
|
Разрешилось, поднял старый дамп системного раздела, слава Акронису! ) Правда пришлось машины в домен передобавить, но все профили сохранились. Дело как мне кажется было в тесевых насторойках на контроллере домена..
|
|
|
подробно о проекте
Анализ криптографических сетевых...
