Выкладываю логи.
Сначала Основной контроллер домена на win2000:
Код:
Microsoft Windows 2000 [Версия 5.00.2195]
(С) Корпорация Майкрософт, 1985-2000.
C:\Documents and Settings\dmon_s>ipconfig /all
Настройка протокола IP для Windows 2000
Имя компьютера . . . . . . . . . : server-1s
Основной DNS суффикс . . . . . . : promed
Тип узла . . . . . . . . . . . . : Гибридный
Включена IP-маршрутизация . . . . : Нет
Доверенный WINS-сервер . . . . . : Нет
Порядок просмотра суффиксов DNS . : promed
Адаптер Ethernet Адаптер 1000 MBit:
DNS суффикс этого подключения . . :
Описание . . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connect
ion
Физический адрес. . . . . . . . . : 00-04-23-46-DD-8B
DHCP разрешен . . . . . . . . . . : Нет
IP-адрес . . . . . . . . . . . . : 192.168.0.100
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . : 192.168.0.1
DNS-серверы . . . . . . . . . . . : 192.168.0.1
192.168.0.100
Основной WINS-сервер . . . . . . : 192.168.0.1
-----------------------------------------------
C:\Documents and Settings\dmon_s>C:\dcdiag.exe /v
DC Diagnosis
Performing initial setup:
* Verifing that the local machine server-1s, is a DC.
* Connecting to directory service on server server-1s.
* Collecting site info.
* Identifying all servers.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\SERVER-1S
Starting test: Connectivity
* Active Directory LDAP Services Check
SERVER-1S's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(73ac8e18-9401-468b-999e-79bd83f8b149._msdcs.promed) couldn't be
resolved, the server name (server-1s.promed) resolved to the IP
address (192.168.0.100) and was pingable. Check that the IP address
is registered correctly with the DNS server.
......................... SERVER-1S failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER-1S
Skipping all tests, because server SERVER-1S is
not responding to directory service requests
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels
Running enterprise tests on : promed
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... promed passed test Intersite
Starting test: FsmoCheck
GC Name: \\server-1s.promed
Locator Flags: 0xe00001fd
PDC Name: \\server-1s.promed
Locator Flags: 0xe00001fd
Time Server Name: \\server-1s.promed
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\server-1s.promed
Locator Flags: 0xe00001fd
KDC Name: \\server-1s.promed
Locator Flags: 0xe00001fd
......................... promed passed test FsmoCheck
---------------------------------------------------------
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection
Owner of the binding path : ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: ¦шэшяюЁЄ WAN (IP)
Component Name : ¦ышхэЄ фы* ёхЄхщ Microsoft
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : ¦ышхэЄ фы* ёхЄхщ Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: ¦ышхэЄ фы* ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ёююс•хэшщ TCP/IP (ёхрэё SMB)
Owner of the binding path : ¦ышхэЄ фы* ёхЄхщ Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: ¦ышхэЄ фы* ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/100 Network Connection
Owner of the binding path : ¦ышхэЄ фы* ёхЄхщ Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: ¦ышхэЄ фы* ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection
Owner of the binding path : ¦ышхэЄ фы* ёхЄхщ Microsoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: ¦ышхэЄ фы* ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndiswanip
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: ¦шэшяюЁЄ WAN (IP)
Component Name : +хёяЁютюфэр* ъюэЇшуєЁрЎш*
Bind Name: wzcsvc
Binding Paths:
Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:
Component Name : TхЁтхЁ єфрыхээюую фюёЄєяр
Bind Name: msrassrv
Binding Paths:
Component Name : -шёяхЄўхЁ яюфъы¦ўхэшщ єфрыхээюую фюёЄєяр
Bind Name: RasMan
Binding Paths:
Component Name : ¦ышхэЄ єфрыхээюую фюёЄєяр
Bind Name: msrascli
Binding Paths:
Component Name : Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Microsoft
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Mi
crosoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ёююс•хэшщ TCP/IP (ёхрэё SMB)
Owner of the binding path : Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Mi
crosoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/100 Network Connection
Owner of the binding path : Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Mi
crosoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection
Owner of the binding path : Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Mi
crosoft
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Tыєцср фюёЄєяр ъ Їрщырь ш яЁшэЄхЁрь ёхЄхщ Microsoft
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndiswanip
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: ¦шэшяюЁЄ WAN (IP)
Component Name : LэЄхЁЇхщё NetBIOS
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : LэЄхЁЇхщё NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: LэЄхЁЇхщё NetBIOS
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/100 Network Connection
Owner of the binding path : LэЄхЁЇхщё NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: LэЄхЁЇхщё NetBIOS
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndis5
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection
Owner of the binding path : LэЄхЁЇхщё NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: LэЄхЁЇхщё NetBIOS
Lower Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
-Interface Name: tdi
Upper Component: ¦ЁюЄюъюы ъышхэЄр WINS (TCP/IP)
Lower Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
-Interface Name: ndiswanip
Upper Component: ¦ЁюЄюъюы LэЄхЁэхЄр (TCP/IP)
Lower Component: ¦шэшяюЁЄ WAN (IP)
Component Name : QoS RSVP
Bind Name: RSVP
Binding Paths:
Component Name : +с•шщ ъырёёшЇшърЄюЁ яръхЄют
Bind Name: Gpc
Binding Paths:
Component Name : Intel(R) PRO/100 Network Connection
Bind Name: {18380FE0-707C-4EC3-AE5C-6A554E70973A}
Binding Paths:
Component Name : Intel(R) PRO/1000 MT Network Connection
Bind Name: {A53C2EFD-CC5B-4DCA-BADB-B7CBCBB04121}
Binding Paths:
Component Name : ¦шэшяюЁЄ WAN (TхЄхтющ ьюэшЄюЁ)
Bind Name: NdisWanBh
Binding Paths:
Component Name : ¦шэшяюЁЄ WAN (IP)
Bind Name: NdisWanIp
Binding Paths:
Component Name : ¦Ё*ьющ ярЁрыыхы№эvщ яюЁЄ
Bind Name: {AAB3C471-72A8-46D6-8DDD-E50968186139}
Binding Paths:
Component Name : ¦шэшяюЁЄ WAN (PPTP)
Bind Name: {7344DFF9-B3C6-4208-BF53-C995B781E761}
Binding Paths:
Component Name : ¦шэшяюЁЄ WAN (L2TP)
Bind Name: {10D3E76F-44C1-4987-BB1E-969AB91DACB8}
Binding Paths:
Component Name : RAS рёшэїЁюээvщ рфряЄхЁ
Bind Name: {D531D6F9-60CC-46B1-8CCB-AF710C867FCC}
Binding Paths:
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.
IPSec Statistics
Oakley Main Modes : 0
Oakley Quick Modes : 0
Active Associations : 0
Soft Associations : 0
Authenticated Bytes Sent : 0
Authenticated Bytes Received : 0
Confidential Bytes Sent : 0
Confidential Bytes Received : 0
ReKeys : 0
Authentication Failures : 0
Negotiation Failures : 0
Packets not decrypted : 0
Packets not authenticated : 0
Invalid Cookies Rcvd : 0
Acquire fail : 0
Receive fail : 0
Send fail : 0
GetSpiFail : 0
KeyAddFail : 0
KeyUpdateFail : 0
Active Acquire : 1
Active Rcv : 0
Active Send : 0
Total Acquire : 0
TotalGetSpi : 0
TotalKeyAdd : 0
TotalKeyUpdate : 0
Inactive Associations : 0
Dead Associations : 0
Pending Keys : 0
Key Flushes : 0
Key Additions : 0
Key Deletes : 0
Phase 1 offers count is 4
OFFER #1:
PFS : No, Encryption : 3DES, Hash : SHA1, Group : Medium (2)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #2:
PFS : No, Encryption : 3DES, Hash : MD5, Group : Medium (2)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #3:
PFS : No, Encryption : DES, Hash : SHA1, Group : Low (1)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
OFFER #4:
PFS : No, Encryption : DES, Hash : MD5, Group : Low (1)
Quickmodes per MainMode : 0, Lifetime Seconds : 28800
Current Phase 1 SAs:
No SAs.
Current Phase 2 SAs:
No SAs.
The command completed successfully
Теперь смотрим логи доп. контроллера домена win2k3_sp1
Код:
Microsoft Windows [Версия 5.2.3790]
(С) Корпорация Майкрософт, 1985-2003.
C:\Documents and Settings\dmon_s>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : file-server
Primary Dns Suffix . . . . . . . : promed
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : promed
Ethernet adapter Подключение по локальной сети:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network Connection w
ith I/O Acceleration
Physical Address. . . . . . . . . : 00-15-17-11-C4-C0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.100
-----------------------------------------------
C:\Documents and Settings\dmon_s>D:\dcdiag.exe /v
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine file-server, is a DC.
* Connecting to directory service on server file-server.
на этом повисло
-----------------------------------------------
C:\Documents and Settings\dmon_s>D:\netdiag.exe /v
Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
¦юфъы¦ўхэшх яю ыюъры№эющ ёхЄш
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
[WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '192.168.0.100'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Looking for a PDC emulator
Looking for a Windows 2000 DC
Gathering the list of Domain Controllers for domain 'PROMED'
Testing trust relationships... Passed
Testing Kerberos authentication... Failed
Testing LDAP servers in Domain PROMED ...
на этом повисло
Невооруженным глазом видно, что не все впорядке. Подскажите, что делать. Если можно, давайте конкретные рекомендации, а не "иди читай статьи", времени не очень много, да и надоела мне эта вся возня.
Спасибо!!!
