Ru-Board.club
← Вернуться в раздел «В помощь системному администратору»

» Создание второго "равноправного" контроллера домена

Автор: Gabzya
Дата сообщения: 26.06.2006 14:19
GOODmen

Цитата:
вобщето считается что все контроллеры равны. Однако....много чего зависит от ролей

100% есть главный контроллер домена на кот роли и все такое... так вот роли я передал, а почему он не стал главный незнаю

Цитата:
Копни работу ДНС, права той учетки. Быть может как в моем случае АД признает только учетку старого админа

и там и там под одной учетной записью вхожу...
Автор: GOODmen
Дата сообщения: 27.06.2006 07:54
Ну тогда будем ждать профи-ГУРУ, мне тоже интересно
Автор: beneth
Дата сообщения: 27.06.2006 08:57
Gabzya
ipconfig /all с первого и второго контроллера
ps если все роли переданы нормально, то тот ДК на котором все роли должен работать даже без понижения старого(dcpromo).
для нормального отката назад после неудачного понижения ДК проще всего перед этой оперецией сделать с него образ, например acronis' ом
Автор: Gabzya
Дата сообщения: 27.06.2006 09:22
с нового : [more=ipconfig]C:\Documents and Settings\gabzya.HQ>ipconfig /all

Настройка протокола IP для Windows

Имя компьютера . . . . . . . . . : TBIH2
Основной DNS-суффикс . . . . . . : hq.tbih-sb.com.ua
Тип узла. . . . . . . . . . . . . : неизвестный
IP-маршрутизация включена . . . . : нет
WINS-прокси включен . . . . . . . : нет
Порядок просмотра суффиксов DNS . : hq.tbih-sb.com.ua
tbih-sb.com.ua
com.ua

Подключение по локальной сети - Ethernet адаптер:

DNS-суффикс этого подключения . . :
Описание . . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Физический адрес. . . . . . . . . : 00-30-48-77-85-02
DHCP включен. . . . . . . . . . . : нет
IP-адрес . . . . . . . . . . . . : 192.168.1.79
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . :
DNS-серверы . . . . . . . . . . . : 192.168.1.79
192.168.1.11[/more]
со старого: [more=ipconfig]
Настройка протокола IP для Windows

Имя компьютера . . . . . . . . . : TBI
Основной DNS-суффикс . . . . . . : hq.tbih-sb.com.ua
Тип узла. . . . . . . . . . . . . : неизвестный
IP-маршрутизация включена . . . . : да
WINS-прокси включен . . . . . . . : да
Порядок просмотра суффиксов DNS . : hq.tbih-sb.com.ua
tbih-sb.com.ua
com.ua

internal - Ethernet адаптер:

DNS-суффикс этого подключения . . :
Описание . . . . . . . . . . . . : Intel(R) PRO/1000 MT сетевое подключение
Физический адрес. . . . . . . . . : 00-30-48-2C-1F-1E
DHCP включен. . . . . . . . . . . : нет
IP-адрес . . . . . . . . . . . . : 192.168.1.11
Маска подсети . . . . . . . . . . : 255.255.255.0
Основной шлюз . . . . . . . . . . :
DNS-серверы . . . . . . . . . . . : 192.168.1.79
192.168.1.11[/more]

Цитата:
если все роли переданы нормально, то тот ДК на котором все роли должен работать даже без понижения старого(dcpromo).

запустил я на старом dcpromo вот результат!!
ПАМАГИТЕ че за фигня
Автор: G14
Дата сообщения: 27.06.2006 09:48
Gabzya
dcdiag /v и netdiag /v с обоих контроллеров. Сюда - только ошибки в теге more.
Автор: Gabzya
Дата сообщения: 27.06.2006 10:52
с нового
[more=dcdiag]C:\Documents and Settings\gabzya.HQ>dcdiag /v

Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine TBIH2, is a DC.
* Connecting to directory service on server TBIH2.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\TBIH2
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... TBIH2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TBIH2
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
* Replication Site Latency Check
......................... TBIH2 passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
(Configuration,Version 2)
* Security Permissions Check for
DC=hq,DC=tbih-sb,DC=com,DC=ua
(Domain,Version 2)
......................... TBIH2 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... TBIH2 passed test NetLogons
Starting test: Advertising
The DC TBIH2 is advertising itself as a DC and having a DS.
The DC TBIH2 is advertising as an LDAP server
The DC TBIH2 is advertising as having a writeable directory
The DC TBIH2 is advertising as a Key Distribution Center
The DC TBIH2 is advertising as a time server
The DS TBIH2 is advertising as a GC.
......................... TBIH2 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-Fir
st-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role Domain Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-Fir
st-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role PDC Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role Rid Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role Infrastructure Update Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers
,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC
=ua
......................... TBIH2 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2103 to 1073741823
* TBIH2.hq.tbih-sb.com.ua is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1603 to 2102
* rIDPreviousAllocationPool is 1603 to 2102
* rIDNextRID: 1603
......................... TBIH2 passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
* SPN found :LDAP/TBIH2.hq.tbih-sb.com.ua
* SPN found :LDAP/TBIH2
* SPN found :LDAP/TBIH2.hq.tbih-sb.com.ua/HQ
* SPN found :LDAP/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2._msdcs.hq.tbih-s
b.com.ua
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/a5c8ed3e-2f49-4298-b7
8b-6dd8a50801e2/hq.tbih-sb.com.ua
* SPN found :HOST/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
* SPN found :HOST/TBIH2.hq.tbih-sb.com.ua
* SPN found :HOST/TBIH2
* SPN found :HOST/TBIH2.hq.tbih-sb.com.ua/HQ
* SPN found :GC/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
......................... TBIH2 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
......................... TBIH2 passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
TBIH2 is in domain DC=hq,DC=tbih-sb,DC=com,DC=ua
Checking for CN=TBIH2,OU=Domain Controllers,DC=hq,DC=tbih-sb,DC=com,DC=
ua in domain DC=hq,DC=tbih-sb,DC=com,DC=ua on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site
-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua in domain CN=Confi
guration,DC=hq,DC=tbih-sb,DC=com,DC=ua on 1 servers
Object is up-to-date on all servers.
......................... TBIH2 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... TBIH2 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... TBIH2 passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minut
es.
......................... TBIH2 passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... TBIH2 passed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=TBIH2,OU=Domain Controllers,DC=hq,DC=tbih-sb,DC=com,DC=ua and
backlink on
CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuratio
n,DC=hq,DC=tbih-sb,DC=com,DC=ua
are correct.
The system object reference (frsComputerReferenceBL)
CN=TBIH2,CN=Domain System Volume (SYSVOL share),CN=File Replication Ser
vice,CN=System,DC=hq,DC=tbih-sb,DC=com,DC=ua
and backlink on
CN=TBIH2,OU=Domain Controllers,DC=hq,DC=tbih-sb,DC=com,DC=ua are
correct.
The system object reference (serverReferenceBL)
CN=TBIH2,CN=Domain System Volume (SYSVOL share),CN=File Replication Ser
vice,CN=System,DC=hq,DC=tbih-sb,DC=com,DC=ua
and backlink on
CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Site
s,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
are correct.
......................... TBIH2 passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences

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 : hq
Starting test: CrossRefValidation
......................... hq passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hq passed test CheckSDRefDom

Running enterprise tests on : hq.tbih-sb.com.ua
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... hq.tbih-sb.com.ua passed test Intersite
Starting test: FsmoCheck
GC Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
PDC Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
Time Server Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
KDC Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
......................... hq.tbih-sb.com.ua passed test FsmoCheck
[/more]
[more=netdiag]
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... Failed
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
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.79' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.11' and other DCs also have some of the names 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 'HQ'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain HQ ...
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.


Computer Name: TBIH2
DNS Host Name: TBIH2.hq.tbih-sb.com.ua
DNS Domain Name: hq.tbih-sb.com.ua
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
Hotfixes :
Installed? Name
Yes KB890046
Yes KB893756
Yes KB896358
Yes KB896422
Yes KB896424
Yes KB896428
Yes KB898715
Yes KB899587
Yes KB899588
Yes KB899589
Yes KB899591
Yes KB900725
Yes KB901017
Yes KB901214
Yes KB902400
Yes KB904706
Yes KB904942
Yes KB905414
Yes KB908519
Yes KB909520
Yes KB910437
Yes KB911562
Yes KB911567
Yes KB911927
Yes KB912812
Yes KB912919
Yes KB913446
Yes Q147222


Netcard queries test . . . . . . . : Passed

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: Прямой параллельный порт
Device: \DEVICE\{82BAF363-CE31-4BF7-BA44-E2DAF1C7FE4B}
GetStats failed for 'Прямой параллельный порт'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Минипорт WAN (PPTP)
Device: \DEVICE\{1C7F08B6-2726-4CE3-8B66-00C05B8C04AC}
GetStats failed for 'Минипорт WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Минипорт WAN (PPPoE)
Device: \DEVICE\{0F6D569A-3C96-4B3F-B08C-127778B7FF50}
GetStats failed for 'Минипорт WAN (PPPoE)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Минипорт WAN (IP)
Device: \DEVICE\NDISWANIP

Media State: Connected

Device State: Connected
Connect Time: 4 days, 21:11:57
Media Speed: 28 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (IP)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (L2TP)
Device: \DEVICE\{086A646B-DD01-48BE-8338-A8DD25C582CD}
GetStats failed for 'Минипорт WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Intel(R) PRO/1000 MT Network Connection
Device: \DEVICE\{27516356-BB2F-47C6-A2C4-13C5D7D0688B}

Media State: Connected

Device State: Connected
Connect Time: 4 days, 21:11:57
Media Speed: 100 Mbps

Packets Sent: 12322481
Bytes Sent (Optional): 0

Packets Received: 12204124
Directed Pkts Recd (Optional): 11905771
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

---------------------------------------------------------------------------
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : Подключение по локальной сети
Adapter ID . . . . . . . . : {27516356-BB2F-47C6-A2C4-13C5D7D0688B}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : TBIH2
Description. . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address . . . . . : 00-30-48-77-85-02
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.1.79
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.1.79
192.168.1.11

IpConfig results . . . . . : Passed

AutoConfiguration results. . . . . . : Passed
AutoConfiguration is not in use.

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
TBIH2 <00> UNIQUE REGISTERED
HQ <00> GROUP REGISTERED
HQ <1C> GROUP REGISTERED
TBIH2 <20> UNIQUE REGISTERED
HQ <1B> UNIQUE REGISTERED
HQ <1E> GROUP REGISTERED
AladinHaspV01.2<30> UNIQUE REGISTERED
HQ <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

        Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
Q <20> UNIQUE 192.168.1.51 560
TBI <20> UNIQUE 192.168.1.11 560
TBI.HQ.TBIH-SB.<43> UNIQUE 192.168.1.11 560
GABZYA-OLD <20> UNIQUE 192.168.1.44 560
HQ <1C> GROUP 80.78.40.166 560


WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
There are no WINS servers configured for this interface.
IPX test : IPX is not installed on this machine.


Global results:


IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Broadcast
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : HQ
Dns domain name. . . . . . . . : hq.tbih-sb.com.ua
Dns forest name. . . . . . . . : hq.tbih-sb.com.ua
Domain Guid. . . . . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Sid . . . . . . . . . . : S-1-5-21-1481786424-387845897-614410136
Logon User . . . . . . . . . . : gabzya
Logon Domain . . . . . . . . . : HQ


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed
PASS - you have at least one non-autoconfigured IP address


IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.


Default gateway test . . . . . . . : Failed

[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.


NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 16
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :6
Description: RSVP TCP Service Provider
Provider Version :6
Max message size : Stream Oriented
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{7E137140-5AA5-42A5-B0C5-C3F656B784F7}] SEQPACKET 5
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{7E137140-5AA5-42A5-B0C5-C3F656B784F7}] DATAGRAM 5
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E3603FF9-FD61-4006-BF7F-5ABCAF48A0B0}] SEQPACKET 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E3603FF9-FD61-4006-BF7F-5ABCAF48A0B0}] DATAGRAM 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{08DBE5B6-B4B9-43D2-85D5-7085EAEF130D}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{08DBE5B6-B4B9-43D2-85D5-7085EAEF130D}] DATAGRAM 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{BF8763F0-4306-45EB-8AEF-6B0318E6ED2E}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{BF8763F0-4306-45EB-8AEF-6B0318E6ED2E}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E79AF61E-813A-4159-8826-E4968E20BD19}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E79AF61E-813A-4159-8826-E4968E20BD19}] DATAGRAM 2
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {27516356-BB2F-47C6-A2C4-13C5D7D0688B}
DNS Domain:
DNS Servers: 192.168.1.79 192.168.1.11
IP Address: Expected registration with PDN (primary DNS domain name):
Hostname: TBIH2.hq.tbih-sb.com.ua.
Authoritative zone: hq.tbih-sb.com.ua.
Primary DNS server: TBIH2.hq.tbih-sb.com.ua 192.168.1.79
Authoritative NS:192.168.1.11 80.78.40.166 192.168.1.79
Check the DNS registration for DCs entries on DNS server '192.168.1.79'
The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.79 is:
DNS NAME = hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.79
A 192.168.1.11
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.772720f0-34ae-4c11-a892-d485dea3ec84.domains._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.772720f0-34ae-4c11-a892-d485dea3ec84.domains._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.79'.

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kerberos._tcp.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kerberos._tcp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kerberos._udp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 464 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kpasswd._tcp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 464 tbi.hq.tbih-sb.com.ua
SRV 0 100 464 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 464 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _kpasswd._udp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 464 tbi.hq.tbih-sb.com.ua
SRV 0 100 464 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.79 is:
DNS NAME = DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.79
A 192.168.1.11
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.79 is:
DNS NAME = ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.11
A 192.168.1.79
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

PASS - All the DNS entries for DC are registered on DNS server '192.168.1.79' and other DCs also have some of the names registered.
Check the DNS registration for DCs entries on DNS server '192.168.1.11'
The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.11 is:
DNS NAME = hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.11
A 192.168.1.79
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.772720f0-34ae-4c11-a892-d485dea3ec84.domains._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.772720f0-34ae-4c11-a892-d485dea3ec84.domains._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.11'.

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kerberos._tcp.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kerberos._tcp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 88 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kerberos._udp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 88 tbi.hq.tbih-sb.com.ua
SRV 0 100 88 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 464 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kpasswd._tcp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 464 tbi.hq.tbih-sb.com.ua
SRV 0 100 464 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 464 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _kpasswd._udp.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 464 tbi.hq.tbih-sb.com.ua
SRV 0 100 464 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.11 is:
DNS NAME = DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.79
A 192.168.1.11
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.11 is:
DNS NAME = ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.11
A 192.168.1.79
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.11'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.11', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.11 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.11'.

The Record is correct on DNS server '192.168.1.11'.

The Record is correct on DNS server '192.168.1.11'.

The Record is correct on DNS server '192.168.1.11'.

The Record is correct on DNS server '192.168.1.11'.

The Record is correct on DNS server '192.168.1.11'.

PASS - All the DNS entries for DC are registered on DNS server '192.168.1.11' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
The browser is bound to 1 NetBt transport.
Mailslot test for HQ* passed.


DC discovery test. . . . . . . . . : Passed

Find DC in domain 'HQ':
Found this DC in domain 'HQ':
DC. . . . . . . . . . . : \\TBIH2.hq.tbih-sb.com.ua
Address . . . . . . . . : \\192.168.1.79
Domain Guid . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Name . . . . . . : hq.tbih-sb.com.ua
Forest Name . . . . . . : hq.tbih-sb.com.ua
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'HQ':
Found this PDC emulator in domain 'HQ':
DC. . . . . . . . . . . : \\TBIH2.hq.tbih-sb.com.ua
Address . . . . . . . . : \\192.168.1.79
Domain Guid . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Name . . . . . . : hq.tbih-sb.com.ua
Forest Name . . . . . . : hq.tbih-sb.com.ua
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find Windows 2000 DC in domain 'HQ':
Found this Windows 2000 DC in domain 'HQ':
DC. . . . . . . . . . . : \\TBIH2.hq.tbih-sb.com.ua
Address . . . . . . . . : \\192.168.1.79
Domain Guid . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Name . . . . . . : hq.tbih-sb.com.ua
Forest Name . . . . . . : hq.tbih-sb.com.ua
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8


DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'HQ':
TBIH2.hq.tbih-sb.com.ua
TBI.hq.tbih-sb.com.ua


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed
Cached Tickets:
Server: krbtgt/HQ.TBIH-SB.COM.UA
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: krbtgt/HQ.TBIH-SB.COM.UA
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: ldap/TBI.hq.tbih-sb.com.ua
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: cifs/TBI.hq.tbih-sb.com.ua
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: LDAP/75eb4035-6f2c-40e7-af21-8955bfb112c3._msdcs.hq.tbih-sb.com.ua
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: cifs/TBIH2.hq.tbih-sb.com.ua
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: ldap/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
End Time: 6/27/2006 17:40:54
Renew Time: 6/30/2006 15:10:45
Server: cifs/Gabzya
End Time: 6/26/2006 22:00:52
Renew Time: 6/30/2006 15:10:45
Server: cifs/Pension1
End Time: 6/23/2006 19:27:53
Renew Time: 6/29/2006 13:47:51
Server: host/tbih2.hq.tbih-sb.com.ua
End Time: 6/22/2006 23:47:51
Renew Time: 6/29/2006 13:47:51


LDAP test. . . . . . . . . . . . . : Passed

Do un-authenticated LDAP call to 'TBIH2.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060627075152.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 119 CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 101716
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 23 TBIH2.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 42 hq.tbih-sb.com.ua:tbih2$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 102 CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'TBIH2.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060627075152.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 119 CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 101716
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 23 TBIH2.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 42 hq.tbih-sb.com.ua:tbih2$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 102 CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'TBIH2.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060627075152.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 119 CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 101716
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 23 TBIH2.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 42 hq.tbih-sb.com.ua:tbih2$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 102 CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
ldap/TBIH2.hq.tbih-sb.com.ua/ForestDnsZones.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/DomainDnsZones.hq.tbih-sb.com.ua
DNS/TBIH2.hq.tbih-sb.com.ua
GC/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
HOST/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
HOST/TBIH2.hq.tbih-sb.com.ua/HQ
ldap/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2._msdcs.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/HQ
ldap/TBIH2
ldap/TBIH2.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
E3514235-4B06-11D1-AB04-00C04FC2DCD2/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2/hq.tbih-sb.com.ua
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/TBIH2.hq.tbih-sb.com.ua
HOST/TBIH2
HOST/TBIH2.hq.tbih-sb.com.ua

Do un-authenticated LDAP call to 'TBI.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060627074928.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 117 CN=NTDS Settings,CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 7 1630798
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 21 TBI.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 40 hq.tbih-sb.com.ua:tbi$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 100 CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'TBI.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060627074928.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 117 CN=NTDS Settings,CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 7 1630798
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 21 TBI.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 40 hq.tbih-sb.com.ua:tbi$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 100 CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'TBI.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060627074928.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 117 CN=NTDS Settings,CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 7 1630798
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 21 TBI.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 40 hq.tbih-sb.com.ua:tbi$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 100 CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
ldap/TBIH2.hq.tbih-sb.com.ua/DomainDnsZones.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/ForestDnsZones.hq.tbih-sb.com.ua
DNS/TBIH2.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/HQ
ldap/TBIH2
ldap/TBIH2.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
ldap/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2._msdcs.hq.tbih-sb.com.ua
HOST/TBIH2.hq.tbih-sb.com.ua/HQ
HOST/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
GC/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
E3514235-4B06-11D1-AB04-00C04FC2DCD2/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2/hq.tbih-sb.com.ua
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/TBIH2.hq.tbih-sb.com.ua
HOST/TBIH2
HOST/TBIH2.hq.tbih-sb.com.ua


Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.79 192.168.1.79 10
192.168.1.79 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.1.255 255.255.255.255 192.168.1.79 192.168.1.79 10
224.0.0.0 240.0.0.0 192.168.1.79 192.168.1.79 10
255.255.255.255 255.255.255.255 192.168.1.79 192.168.1.79 1
No persistent route entries.


Netstat information test . . . . . : Passed


Interface Statistics

Received Sent
Unicast Packets 3865729185 2254805884
Non-unicast packets 302583 7697
Discards 0 0
Errors 0 1
Unknown protocols 95 523820

Interface index = 1
Description = MS TCP Loopback interface
Type = 24
MTU = 1520
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 3939352655
Output Queue Length = 0


Interface index = 65539
Description = Intel(R) PRO/1000 MT Network Connection
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-30-48-77-85-02
Administrative Status = 1
Operational Status = 1
Last Changed = 3939352656
Output Queue Length = 0



Active Connections

Proto Local Address Foreign Address State
TCP TBIH2:domain TBIH2.hq.tbih-sb.com.ua:35046 LISTENING
TCP TBIH2:http TBIH2.hq.tbih-sb.com.ua:55434 LISTENING
TCP TBIH2:hosts2-ns TBIH2.hq.tbih-sb.com.ua:30902 LISTENING
TCP TBIH2:kerberos TBIH2.hq.tbih-sb.com.ua:53451 LISTENING
TCP TBIH2:epmap TBIH2.hq.tbih-sb.com.ua:2208 LISTENING
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:55322 LISTENING
TCP TBIH2:microsoft-ds TBIH2.hq.tbih-sb.com.ua:18612 LISTENING
TCP TBIH2:kpasswd TBIH2.hq.tbih-sb.com.ua:20524 LISTENING
TCP TBIH2:475 TBIH2.hq.tbih-sb.com.ua:14377 LISTENING
TCP TBIH2:http-rpc-epmap TBIH2.hq.tbih-sb.com.ua:10391 LISTENING
TCP TBIH2:ldaps TBIH2.hq.tbih-sb.com.ua:49276 LISTENING
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:39166 LISTENING
TCP TBIH2:1027 TBIH2.hq.tbih-sb.com.ua:43252 LISTENING
TCP TBIH2:1057 TBIH2.hq.tbih-sb.com.ua:12523 LISTENING
TCP TBIH2:1071 TBIH2.hq.tbih-sb.com.ua:20723 LISTENING
TCP TBIH2:1093 TBIH2.hq.tbih-sb.com.ua:4295 LISTENING
TCP TBIH2:1260 TBIH2.hq.tbih-sb.com.ua:2176 LISTENING
TCP TBIH2:2937 TBIH2.hq.tbih-sb.com.ua:22613 LISTENING
TCP TBIH2:msft-gc TBIH2.hq.tbih-sb.com.ua:2224 LISTENING
TCP TBIH2:msft-gc-ssl TBIH2.hq.tbih-sb.com.ua:57479 LISTENING
TCP TBIH2:ms-wbt-server TBIH2.hq.tbih-sb.com.ua:59482 LISTENING
TCP TBIH2:5900 TBIH2.hq.tbih-sb.com.ua:2144 LISTENING
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1053 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1054 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1055 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1959 ESTABLISHED
TCP TBIH2:1053 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:1054 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:1055 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:1959 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:4034 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:4042 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:4044 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:4046 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:4048 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:epmap TBI:3432 ESTABLISHED
TCP TBIH2:netbios-ssn TBIH2.hq.tbih-sb.com.ua:47174 LISTENING
TCP TBIH2:ldap Q:1517 TIME_WAIT
TCP TBIH2:ldap Q:1518 TIME_WAIT
TCP TBIH2:ldap Q:1526 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1962 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3898 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:4033 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:4117 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:4119 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:4197 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:4198 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:4199 TIME_WAIT
TCP TBIH2:microsoft-ds pension3.hq.tbih-sb.com.ua:1128 ESTABLISHED
TCP TBIH2:microsoft-ds kashuba.hq.tbih-sb.com.ua:1069 ESTABLISHED
TCP TBIH2:microsoft-ds gluzdan.hq.tbih-sb.com.ua:1194 ESTABLISHED
TCP TBIH2:microsoft-ds pahomova.hq.tbih-sb.com.ua:1256 ESTABLISHED
TCP TBIH2:microsoft-ds romanenko.hq.tbih-sb.com.ua:1263 ESTABLISHED
TCP TBIH2:microsoft-ds vladimir.hq.tbih-sb.com.ua:3846 ESTABLISHED
TCP TBIH2:microsoft-ds p5.hq.tbih-sb.com.ua:1059 ESTABLISHED
TCP TBIH2:microsoft-ds p1.hq.tbih-sb.com.ua:1122 ESTABLISHED
TCP TBIH2:microsoft-ds GABZYA-OLD:1066 ESTABLISHED
TCP TBIH2:microsoft-ds nb2-impression.hq.tbih-sb.com.ua:1059 ESTABLISHED
TCP TBIH2:microsoft-ds nb4-hp-r.hq.tbih-sb.com.ua:1054 ESTABLISHED
TCP TBIH2:1025 TBI:2801 ESTABLISHED
TCP TBIH2:1025 TBI:3433 ESTABLISHED
TCP TBIH2:1025 TBI:3727 ESTABLISHED
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:1062 ESTABLISHED
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:1511 ESTABLISHED
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:4130 ESTABLISHED
TCP TBIH2:1062 TBIH2.hq.tbih-sb.com.ua:1025 ESTABLISHED
TCP TBIH2:1066 TBI:ldap CLOSE_WAIT
TCP TBIH2:1511 TBIH2.hq.tbih-sb.com.ua:1025 ESTABLISHED
TCP TBIH2:1962 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:2841 TBIH2.hq.tbih-sb.com.ua:ldap CLOSE_WAIT
TCP TBIH2:ms-wbt-server gabzya.hq.tbih-sb.com.ua:1400 ESTABLISHED
TCP TBIH2:3813 TBI:1025 ESTABLISHED
TCP TBIH2:3898 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:4009 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4010 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4035 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:4038 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4039 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4040 TBI:epmap TIME_WAIT
TCP TBIH2:4041 TBI:1025 TIME_WAIT
TCP TBIH2:4045 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:4047 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:4049 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:4050 TBI:1025 ESTABLISHED
TCP TBIH2:4110 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4111 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4112 TBI:microsoft-ds TIME_WAIT
TCP TBIH2:4114 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:4116 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:4119 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:4120 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4121 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4122 TBI:ldap TIME_WAIT
TCP TBIH2:4123 TBI:ldap TIME_WAIT
TCP TBIH2:4125 TBI:ldap TIME_WAIT
TCP TBIH2:4126 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4127 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4129 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4130 TBIH2.hq.tbih-sb.com.ua:1025 ESTABLISHED
TCP TBIH2:4190 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4191 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4192 TBI:microsoft-ds ESTABLISHED
TCP TBIH2:4194 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:4196 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:4198 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:4199 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:4200 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4201 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:4202 TBI:ldap TIME_WAIT
TCP TBIH2:4203 TBI:ldap TIME_WAIT
TCP TBIH2:4204 TBI:ldap ESTABLISHED
TCP TBIH2:4205 TBI:ldap TIME_WAIT
TCP TBIH2:4206 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:4207 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:30583 TBIH2.hq.tbih-sb.com.ua:28757 LISTENING
UDP TBIH2:microsoft-ds *:*
UDP TBIH2:475 *:*
UDP TBIH2:isakmp *:*
UDP TBIH2:1031 *:*
UDP TBIH2:1032 *:*
UDP TBIH2:1041 *:*
UDP TBIH2:ipsec-msft *:*
UDP TBIH2:11000 *:*
UDP TBIH2:domain *:*
UDP TBIH2:ntp *:*
UDP TBIH2:1029 *:*
UDP TBIH2:1040 *:*
UDP TBIH2:1052 *:*
UDP TBIH2:1058 *:*
UDP TBIH2:1065 *:*
UDP TBIH2:1076 *:*
UDP TBIH2:1163 *:*
UDP TBIH2:1306 *:*
UDP TBIH2:1309 *:*
UDP TBIH2:1441 *:*
UDP TBIH2:1448 *:*
UDP TBIH2:1924 *:*
UDP TBIH2:2840 *:*
UDP TBIH2:3005 *:*
UDP TBIH2:4195 *:*
UDP TBIH2:domain *:*
UDP TBIH2:bootps *:*
UDP TBIH2:bootpc *:*
UDP TBIH2:kerberos *:*
UDP TBIH2:ntp *:*
UDP TBIH2:netbios-ns *:*
UDP TBIH2:netbios-dgm *:*
UDP TBIH2:389 *:*
UDP TBIH2:kpasswd *:*
UDP TBIH2:2535 *:*


IP Statistics

Packets Received = 13 024 175
Received Header Errors = 0
Received Address Errors = 3 370
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 13 024 137
Output Requests = 10 403 196
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 4 818
Reassembly Required = 76
Reassembly Successful = 38
Reassembly Failures = 0
Datagrams successfully fragmented = 38
Datagrams failing fragmentation = 0
Fragments Created = 76
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60


TCP Statistics

Active Opens = 20 069
Passive Opens = 44 345
Failed Connection Attempts = 58
Reset Connections = 510
Current Connections = 42
Received Segments = 12 821 352
Segment Sent = 10 309 275
Segment Retransmitted = 15 099
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 120 000
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 143 813
No Ports = 27 564
Receive Errors = 0
Datagrams Sent = 22 134


ICMP Statistics

Received Sent
Messages 53 372 53 372
Errors 0 0
Destination Unreachable 13 13
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 33 638 33 638
Echo Replies 19 721 19 721
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
Component Name : NDIS-протокол ввода-вывода пользовательского режима
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Intel(R) PRO/1000 MT Network Connection


Component Name : Протокол точка-точка по Ethernet
Bind Name: RasPppoe
Binding Paths:
Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Intel(R) PRO/1000 MT Network Connection


Component Name : Туннельный протокол точка-точка
Bind Name: mspptp
Binding Paths:

Component Name : Туннельный протокол уровня 2
Bind Name: msl2tp
Binding Paths:

Component Name : NDIS-драйвер WAN удаленного доступа
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Прямой параллельный порт

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Минипорт WAN (PPPoE)

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Минипорт WAN (PPTP)

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Минипорт WAN (L2TP)

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: RAS асинхронный адаптер


Component Name : Протокол сообщений TCP/IP (сеанс SMB)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : Протокол клиента WINS (TCP/IP)
Bind Name: NetBT
Binding Paths:
Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Протокол Интернета (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (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: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Веб-клиент
Bind Name: WebClient
Binding Paths:

Component Name : DHCP-сервер
Bind Name: DHCPServer
Binding Paths:

Component Name : Беспроводная настройка
Bind Name: wzcsvc
Binding Paths:

Component Name : Балансировка нагрузки сети
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Intel(R) PRO/1000 MT Network Connection


Component Name : Сервер маршрутизации и удаленного доступа
Bind Name: RemoteAccess
Binding Paths:

Component Name : Сервер удаленного доступа
Bind Name: msrassrv
Binding Paths:

Component Name : Диспетчер подключений удаленного доступа
Bind Name: RasMan
Binding Paths:

Component Name : Клиент удаленного доступа
Bind Name: msrascli
Binding Paths:

Component Name : Служба доступа к файлам и принтерам сетей Microsoft
Bind Name: LanmanServer
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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (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: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Интерфейс NetBIOS
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Общий классификатор пакетов
Bind Name: Gpc
Binding Paths:

Component Name : Шлюз уровня приложения
Bind Name: ALG
Binding Paths:

Component Name : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2
Bind Name: {7E137140-5AA5-42A5-B0C5-C3F656B784F7}
Binding Paths:

Component Name : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Bind Name: {E3603FF9-FD61-4006-BF7F-5ABCAF48A0B0}
Binding Paths:

Component Name : Intel(R) PRO/1000 MT Network Connection #2
Bind Name: {08DBE5B6-B4B9-43D2-85D5-7085EAEF130D}
Binding Paths:

Component Name : Intel(R) PRO/1000 MT Network Connection
Bind Name: {27516356-BB2F-47C6-A2C4-13C5D7D0688B}
Binding Paths:

Component Name : Минипорт WAN (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Прямой параллельный порт
Bind Name: {82BAF363-CE31-4BF7-BA44-E2DAF1C7FE4B}
Binding Paths:

Component Name : Минипорт WAN (PPPoE)
Bind Name: {0F6D569A-3C96-4B3F-B08C-127778B7FF50}
Binding Paths:

Component Name : Минипорт WAN (PPTP)
Bind Name: {1C7F08B6-2726-4CE3-8B66-00C05B8C04AC}
Binding Paths:

Component Name : Минипорт WAN (L2TP)
Bind Name: {086A646B-DD01-48BE-8338-A8DD25C582CD}
Binding Paths:

Component Name : RAS асинхронный адаптер
Bind Name: {3CB73B49-3F8E-4341-8CBA-E5F3123703B7}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
[/more]
со старого
сек


Добавлено:
[more=dcdiag2]
Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine TBI, is a DC.
* Connecting to directory service on server TBI.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\TBI
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... TBI passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TBI
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=hq,DC=tbih-sb,DC=com,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
* Replication Site Latency Check
......................... TBI passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions Check for
DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
(Configuration,Version 2)
* Security Permissions Check for
DC=hq,DC=tbih-sb,DC=com,DC=ua
(Domain,Version 2)
......................... TBI passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
......................... TBI passed test NetLogons
Starting test: Advertising
The DC TBI is advertising itself as a DC and having a DS.
The DC TBI is advertising as an LDAP server
The DC TBI is advertising as having a writeable directory
The DC TBI is advertising as a Key Distribution Center
The DC TBI is advertising as a time server
......................... TBI passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role Domain Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role PDC Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role Rid Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Role Infrastructure Update Owner = CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
......................... TBI passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2103 to 1073741823
* TBIH2.hq.tbih-sb.com.ua is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1103 to 1602
* rIDPreviousAllocationPool is 1103 to 1602
* rIDNextRID: 1252
......................... TBI passed test RidManager
Starting test: MachineAccount
* SPN found :LDAP/TBI.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
* SPN found :LDAP/TBI.hq.tbih-sb.com.ua
* SPN found :LDAP/TBI
* SPN found :LDAP/TBI.hq.tbih-sb.com.ua/HQ
* SPN found :LDAP/75eb4035-6f2c-40e7-af21-8955bfb112c3._msdcs.hq.tbih-sb.com.ua
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/75eb4035-6f2c-40e7-af21-8955bfb112c3/hq.tbih-sb.com.ua
* SPN found :HOST/TBI.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
* SPN found :HOST/TBI.hq.tbih-sb.com.ua
* SPN found :HOST/TBI
* SPN found :HOST/TBI.hq.tbih-sb.com.ua/HQ
* SPN found :GC/TBI.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
......................... TBI 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
w32time Service is stopped on [TBI]
* Checking Service: NETLOGON
NETLOGON Service is stopped on [TBI]
......................... TBI failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
TBI is in domain DC=hq,DC=tbih-sb,DC=com,DC=ua
Checking for CN=TBI,OU=Domain Controllers,DC=hq,DC=tbih-sb,DC=com,DC=ua in domain DC=hq,DC=tbih-sb,DC=com,DC=ua on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua in domain CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua on 1 servers
Object is up-to-date on all servers.
......................... TBI passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... TBI passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... TBI 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.
......................... TBI passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0xC0000007
Time Generated: 06/27/2006 10:14:45
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0001B59
Time Generated: 06/27/2006 10:48:30
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0001B59
Time Generated: 06/27/2006 10:51:42
(Event String could not be retrieved)
......................... TBI failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)

CN=TBI,OU=Domain Controllers,DC=hq,DC=tbih-sb,DC=com,DC=ua and

backlink on

CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua

are correct.
The system object reference (frsComputerReferenceBL)

CN=TBI,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=hq,DC=tbih-sb,DC=com,DC=ua

and backlink on

CN=TBI,OU=Domain Controllers,DC=hq,DC=tbih-sb,DC=com,DC=ua are

correct.
The system object reference (serverReferenceBL)

CN=TBI,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=hq,DC=tbih-sb,DC=com,DC=ua

and backlink on

CN=NTDS Settings,CN=TBI,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua

are correct.
......................... TBI passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences

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 : hq
Starting test: CrossRefValidation
......................... hq passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hq passed test CheckSDRefDom

Running enterprise tests on : hq.tbih-sb.com.ua
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... hq.tbih-sb.com.ua passed test Intersite
Starting test: FsmoCheck
GC Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
PDC Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
Time Server Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
KDC Name: \\TBIH2.hq.tbih-sb.com.ua
Locator Flags: 0xe00003fd
......................... hq.tbih-sb.com.ua passed test FsmoCheck
[/more]
[more=netdiag2]
Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing Domain membership... Failed
[WARNING] Member : Netlogon service is not running.
Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Failed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
internal
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
[FATAL] File \config\netlogon.dns contains invalid DNS entries. [FATAL] File \config\netlogon.dns contains invalid DNS entries. [WARNING] The DNS entries for this DC cannot be verified right now on DNS server 80.78.35.2, ERROR_TIMEOUT.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS server 80.78.35.1, ERROR_TIMEOUT.
[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 'HQ'
Testing trust relationships... Failed
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain HQ ...
Gathering routing information
Gathering network statistics information.
[/more]
Автор: beneth
Дата сообщения: 27.06.2006 11:23
вот скорей всего прчина ошибки dcpromo

Цитата:
Checking Service: NETLOGON
NETLOGON Service is stopped on

запусти netlogon (net start netlogon)
Автор: G14
Дата сообщения: 27.06.2006 11:25
короче всех твоих логов я не осилил. Я просил " Сюда - только ошибки ".....
Из того, что сразу видно:

Цитата:
Testing DNS
[FATAL] File \config\netlogon.dns contains invalid DNS entries.
[FATAL] File \config\netlogon.dns contains invalid DNS entries.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS server 80.78.35.2, ERROR_TIMEOUT.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS server 80.78.35.1, ERROR_TIMEOUT.
[FATAL] No DNS servers have the DNS records for this DC registered.


Объяснять что значат эти ошибки? 80.78.35.1 - наверняка это DNS провайдера...ОТКУДА ему знать о твоих SRV-записях для домена AD ?


Цитата:
Testing Domain membership... Failed
[WARNING] Member : Netlogon service is not running.

Проверяй почему сервис не стартовал....
Пока не разберешься почему не стартует служба - дальше ковыряться бессмысленно...
Автор: GOODmen
Дата сообщения: 27.06.2006 11:32
быть может нетлогон стартует от имени пользователя который не может авторизоваться
Автор: Gabzya
Дата сообщения: 27.06.2006 11:41
beneth

Цитата:
запусти netlogon (net start netlogon)

понял ща запущу, в службах не нашел, зато через ком строку запустил, кстате а как в службах оно отображается, за что отвечает?

G14

Цитата:
короче всех твоих логов я не осилил. Я просил " Сюда - только ошибки ".....

сори там их так много я не вкурсе пока где именно ошибка...

Цитата:
Объяснять что значат эти ошибки? 80.78.35.1 - наверняка это DNS провайдера...ОТКУДА ему знать о твоих SRV-записях для домена AD ?

да есть еще одна сетевуха на нем(отключена сейчас)
на кот настроен внешний ай-пи раньше выходил в и-нет напрямую, для соединения по ВПН...

Цитата:
Проверяй почему сервис не стартовал....
Пока не разберешься почему не стартует служба - дальше ковыряться бессмысленно...

запустил ручками, где глядеть как он должен стартовать?


Добавлено:
снова запустил dcpromo, тоже окно, в процессе работы мастера писалось...остановка службы nelogon, затем снова тоже сообщение об ошибке....

Добавлено:
отключил вторую сетевуху ваще и вот вроде пошло
сначала так:

потом так:

потом так:

вроде пошло.....


Добавлено:
попроси л перезагрузку.... соглашаюсь

Добавлено:
вроде все ОККК
только второй сервак тоже перезагрузился
при загрузке выдал ошибку и в журнал записал такое
Тип события: Ошибка
Источник события: System Error
Категория события: (102)
Код события: 1003
Дата: 27.06.2006
Время: 12:24:40
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
Код ошибки 1000007f, параметр1 00000008, параметр2 f7737fe0, параметр3 00000000, параметр4 00000000.




Добавлено:
вроде все впорядке
только вот эта ошибка непонятно....
да еще [more=ошибки]
Тип события: Предупреждение
Источник события: MRxSmb
Категория события: Отсутствует
Код события: 3019
Дата: 27.06.2006
Время: 12:38:52
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
Перенаправитель не смог определить тип подключения.



Тип события: Ошибка
Источник события: System Error
Категория события: (102)
Код события: 1003
Дата: 27.06.2006
Время: 12:24:40
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
Код ошибки 1000007f, параметр1 00000008, параметр2 f7737fe0, параметр3 00000000, параметр4 00000000.



Тип события: Предупреждение
Источник события: USER32
Категория события: Отсутствует
Код события: 1076
Дата: 27.06.2006
Время: 12:24:26
Пользователь: HQ\gabzya
Компьютер: TBIH2
Описание:
Причина непредвиденного завершения работы данного компьютера, предоставленная пользователем HQ\gabzya: Отказ системы: Ошибка STOP
Код причины: 0x805000f
Код ошибки:
Строка проверки: 0x0000007f (0x00000008, 0xf7737fe0, 0x00000000, 0x00000000)
Комментарий: 0x0000007f (0x00000008, 0xf7737fe0, 0x00000000, 0x00000000)



Тип события: Ошибка
Источник события: NETLOGON
Категория события: Отсутствует
Код события: 5774
Дата: 27.06.2006
Время: 12:24:00
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
Ошибка при динамической регистрации записи DNS "_ldap._tcp.pdc._msdcs.hq.tbih-sb.com.ua. 600 IN SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua." на следующем DNS-сервере.

IP-адрес DNS-сервера: 80.78.35.1
Возвращенный код ответа (RCODE): 0
Возвращенный код состояния: 10065

Чтобы компьютеры и пользователи могли определять местоположение этого контроллера домена, необходимо зарегистрировать запись в DNS.

Действие пользователя
Определите, что могло стать причиной ошибки, устраните ее и инициируйте регистрацию записей DNS контроллером домена. Для определения возможной причины ошибки запустите программу DCDiag.exe. Ее можно найти на установочном компакт-диске Windows Server 2003 в файле Support\Tools\support.cab. Дополнительные сведения о программе DCDiag.exe см. в Центре справки и поддержки. Чтобы инициировать регистрацию записей DNS данным контроллером домена, запустите процедуру "nltest.exe /dsregdns" в командной строке контроллера домена или перезапустите службу сетевого входа в систему. Программа Nltest.exe имеется на компакт-диске "Комплект ресурсов Microsoft Windows Server".
Можно также вручную добавить эту запись в DNS, но это не рекомендуется.

Дополнительные сведения
Значение с ошибкой: Сделана попытка выполнить операцию на сокете для недоступного хоста.



Тип события: Ошибка
Источник события: DNS
Категория события: Отсутствует
Код события: 6702
Дата: 27.06.2006
Время: 12:23:22
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
DNS-сервер обновил свои записи узла (A). Чтобы убедиться, что с этими интегрированными в DS равноправными DNS-серверами можно провести репликацию с данным сервером, была произведена попытка их динамического обновления с новыми записями. При этом обновлении произошла ошибка. Данные записи содержат код ошибки.

Если этот DNS-сервер не имеет интегрированных в DS партнеров по репликации,
то это сообщение об ошибке можно пропустить.

Если партнеры репликации Active Directory этого DNS-cервера имеют неправильные IP-адреса этого сервера, то они не смогут проводить репликацию с ним.

Чтобы убедиться в правильном проведении репликации:
1) Найдите партнеров репликации Active Directory данного сервера, на которых запущен DNS-сервер .
2) Откройте "Диспетчер DNS" и подключитесь по очереди к каждому из партнеров по репликации.
3) На каждом сервере, проверьте регистрацию узла (запись типа A) для ЭТОГО сервера.
4) Удалите любые записи (A), которые НЕ связанны с IP-адресами этого сервера.
5) Если для этого сервера отсутствуют записи типа (A), добавьте как минимум одну запись (A), связанную с адресом этого сервера, с которой партнер по репликации может контактировать. (Другими словами, если для данного DNS-сервера существует несколько IP-адресов, добавьте по крайней мере один, который находится в той же сети, что и обновляемый Active Directory DNS-сервер.)
6) Отметьте, что не обязательно обновлять сведения КАЖДОГО партнера по репликации. Это необходимо только для тех, чьи записи исправляются, чтобы каждый сервер, реплицирующий данные этого сервера, получал после репликации новые данные.



Тип события: Предупреждение
Источник события: SceCli
Категория события: Отсутствует
Код события: 1202
Дата: 27.06.2006
Время: 12:29:09
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
Выполнено распространение политики безопасности с предупреждением. 0x5 : Отказано в доступе.

Справка по данному вопросу размещена на веб-узле http://support.microsoft.com. Запросите "troubleshooting 1202 events".


[/more]тоже непонятно
если поможите истолковать их смысл буду Оччень признателен
спс

Добавлено:
[more=со старого ошибки]Тип события: Предупреждение
Источник события: SceCli
Категория события: Отсутствует
Код события: 1202
Дата: 27.06.2006
Время: 14:02:20
Пользователь: Н/Д
Компьютер: TBI
Описание:
Выполнено распространение политики безопасности с предупреждением. 0x5 : Отказано в доступе.

Справка по данному вопросу размещена на веб-узле http://support.microsoft.com. Запросите "troubleshooting 1202 events".


Тип события: Ошибка
Источник события: Winlogon
Категория события: Отсутствует
Код события: 1219
Дата: 27.06.2006
Время: 14:04:04
Пользователь: Н/Д
Компьютер: TBI
Описание:
Отказано во входе в систему для HQ\gabzya. Не удалось получить конфигурацию пользователя сервера терминалов. Ошибка: Сервер RPC недоступен.




Тип события: Ошибка
Источник события: nssrvpm
Категория события: Отсутствует
Код события: 0
Дата: 27.06.2006
Время: 14:00:07
Пользователь: Н/Д
Компьютер: TBI
Описание:
Не найдено описание для события с кодом ( 0 ) в источнике ( nssrvpm ). Возможно, на локальном компьютере нет нужных данных в реестре или файлов DLL сообщений для отображения сообщений удаленного компьютера. Попробуйте использовать ключ /AUXSOURCE= для получения этого описания, - дополнительные сведения об этом содержатся в справке. В записи события содержится следующая информация: Service failed on start: List index out of bounds (0).



Тип события: Предупреждение
Источник события: MSDTC
Категория события: SVC
Код события: 53258
Дата: 27.06.2006
Время: 14:00:01
Пользователь: Н/Д
Компьютер: TBI
Описание:
MS DTC не удалось правильно обработать событие повышения или понижения уровня контроллера домена. MS DTC продолжит работу и будет использовать текущие настройки безопасности. Сведения об ошибке: %1




Тип события: Предупреждение
Источник события: MSDTC
Категория события: SVC
Код события: 53258
Дата: 27.06.2006
Время: 14:00:01
Пользователь: Н/Д
Компьютер: TBI
Описание:
MS DTC не удалось правильно обработать событие повышения или понижения уровня контроллера домена. MS DTC продолжит работу и будет использовать текущие настройки безопасности. Сведения об ошибке: d:\nt\com\complus\dtc\dtc\adme\uiname.cpp:9280, Pid: 1480
No Callstack,
CmdLine: C:\WINDOWS\system32\msdtc.exe
Данные:
0000: 05 00 07 80 ...&#128;




Тип события: Ошибка
Источник события: Userenv
Категория события: Отсутствует
Код события: 1053
Дата: 27.06.2006
Время: 13:51:30
Пользователь: NT AUTHORITY\SYSTEM
Компьютер: TBI
Описание:
Не удалось определить имя пользователя или компьютера. (Сервер RPC недоступен. ). Обработка групповой политики прекращена.





[/more]
похожи на те кот на новом
Автор: levkadub
Дата сообщения: 27.06.2006 14:24
подскажите как создать сайт в домне и назначить этому сайту контроллер домена?
если можно пошагово.....
Автор: Gabzya
Дата сообщения: 27.06.2006 15:45
похоже все ошибки из-за ДНС лезут, посотрел на контроллере визде где есть упоминание о серверах то присутствует запись и о старом серваке(в оснастке ДНС)
Может нужно почистить как-то? ручками поприбивать усе? или есть команда подчистки?
у юзверей похоже теперь тоже проблемы, прописал я в дефаулт политик контроллера ДНС новый, так теперь пришлось и прокси прописывать в ихнем IE, раньше не надо было, ДНС нормально настроен был и без настроек в IE все фурыкало и почта теперь ходит ООООчень медленно подозрение на ДНС
вот новые [more=dcdiag]
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x40000005
Time Generated: 06/27/2006 15:22:54
(Event String could not be retrieved)
......................... TBIH2 failed test systemlog

[/more] и [more=netdiag]
Testing DNS
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.79'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.



[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
TBI.HQ.TBIH-SB.<43> UNIQUE 192.168.1.11 112
GABZYA <00> UNIQUE 192.168.1.21 10




NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.





[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.79'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.







[/more]
G14 вроде только ошибки выбрал....
Автор: PRiM
Дата сообщения: 27.06.2006 16:20

Цитата:
подскажите как создать сайт в домне и назначить этому сайту контроллер домена?
если можно пошагово...

1 Пускаем АД сайты и службы
2 Создаем новый сайт. Связь берем по умолчанию
3 Создаем новую подсеть. И связываем с новым сайтом.
4 Нужный контроллер домена переносишь в нужный сайт. Смотри, чтобы ИП адреса подсети и КД соответствовали.
5 Новое подключение должно создасься автоматически через некоторое время (~15 мин)

Вроде все. Если я конечно тебя правильно понял и под словом "сайт" мы понимаем одно и то же!
Подробно это все описано в книге к экзамену 70-294 Планирование АД Русская редакция.
Автор: G14
Дата сообщения: 28.06.2006 06:05

Цитата:
Testing DNS
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.79'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.

1. смотрим наличие зоны _msdcs.your-domain.com в DNS
2. смотрим, чтобы на ней были разрешены динамические обновления
3. netdiag /fix
4. проверяемся dcdiag и netdiag /v
Автор: Gabzya
Дата сообщения: 28.06.2006 09:58

Цитата:

1. смотрим наличие зоны _msdcs.your-domain.com в DNS

есть

Цитата:
2. смотрим, чтобы на ней были разрешены динамические обновления

стоит-ТОлько безопасные
тут же сотрю и еще в некот местах на закладке серверы имен еще присутствует старый сервер... нужно его грохнуть?

Цитата:
3. netdiag /fix

[more=вот]
....................................

Computer Name: TBIH2
DNS Host Name: TBIH2.hq.tbih-sb.com.ua
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB898715
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB904942
KB905414
KB908519
KB909520
KB910437
KB911562
KB911567
KB911927
KB912812
KB912919
KB913446
Q147222


Netcard queries test . . . . . . . : Passed
GetStats failed for 'Прямой параллельный порт'. [ERROR_NOT_SUPPORTED]
GetStats failed for 'Минипорт WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
GetStats failed for 'Минипорт WAN (PPPoE)'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'Минипорт WAN (IP)' may not be working because it has not received any packets.
GetStats failed for 'Минипорт WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

Adapter : Подключение по локальной сети

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : TBIH2
IP Address . . . . . . . . : 192.168.1.79
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.1.79


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Failed

[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.79' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
[/more] вроде все ОК

Цитата:
4. проверяемся dcdiag и netdiag /v

[more=dcdiag]
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\TBIH2
Starting test: Connectivity
......................... TBIH2 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\TBIH2
Starting test: Replications
......................... TBIH2 passed test Replications
Starting test: NCSecDesc
......................... TBIH2 passed test NCSecDesc
Starting test: NetLogons
......................... TBIH2 passed test NetLogons
Starting test: Advertising
......................... TBIH2 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... TBIH2 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... TBIH2 passed test RidManager
Starting test: MachineAccount
......................... TBIH2 passed test MachineAccount
Starting test: Services
......................... TBIH2 passed test Services
Starting test: ObjectsReplicated
......................... TBIH2 passed test ObjectsReplicated
Starting test: frssysvol
......................... TBIH2 passed test frssysvol
Starting test: frsevent
......................... TBIH2 passed test frsevent
Starting test: kccevent
......................... TBIH2 passed test kccevent
Starting test: systemlog
......................... TBIH2 passed test systemlog
Starting test: VerifyReferences
......................... TBIH2 passed test VerifyReferences

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 : hq
Starting test: CrossRefValidation
......................... hq passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hq passed test CheckSDRefDom

Running enterprise tests on : hq.tbih-sb.com.ua
Starting test: Intersite
......................... hq.tbih-sb.com.ua passed test Intersite
Starting test: FsmoCheck
......................... hq.tbih-sb.com.ua passed test FsmoCheck
[/more] вроде тоже все ок [more=netdiag /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... Failed
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
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.79' and other DCs also have some of the names 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 'HQ'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain HQ ...
Gathering routing information
Gathering network statistics information.
Gathering configuration of bindings.
Gathering RAS connection information
Gathering Modem information
Gathering Netware information
Gathering IP Security information

Tests complete.


Computer Name: TBIH2
DNS Host Name: TBIH2.hq.tbih-sb.com.ua
DNS Domain Name: hq.tbih-sb.com.ua
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
Hotfixes :
Installed? Name
Yes KB890046
Yes KB893756
Yes KB896358
Yes KB896422
Yes KB896424
Yes KB896428
Yes KB898715
Yes KB899587
Yes KB899588
Yes KB899589
Yes KB899591
Yes KB900725
Yes KB901017
Yes KB901214
Yes KB902400
Yes KB904706
Yes KB904942
Yes KB905414
Yes KB908519
Yes KB909520
Yes KB910437
Yes KB911562
Yes KB911567
Yes KB911927
Yes KB912812
Yes KB912919
Yes KB913446
Yes Q147222


Netcard queries test . . . . . . . : Passed

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: Прямой параллельный порт
Device: \DEVICE\{82BAF363-CE31-4BF7-BA44-E2DAF1C7FE4B}
GetStats failed for 'Прямой параллельный порт'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Минипорт WAN (PPTP)
Device: \DEVICE\{1C7F08B6-2726-4CE3-8B66-00C05B8C04AC}
GetStats failed for 'Минипорт WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Минипорт WAN (PPPoE)
Device: \DEVICE\{0F6D569A-3C96-4B3F-B08C-127778B7FF50}
GetStats failed for 'Минипорт WAN (PPPoE)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Минипорт WAN (IP)
Device: \DEVICE\NDISWANIP

Media State: Connected

Device State: Connected
Connect Time: 21:34:36
Media Speed: 28 Kbps

Packets Sent: 0
Bytes Sent (Optional): 0

Packets Received: 0
Directed Pkts Recd (Optional): 0
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

[WARNING] The net card 'Минипорт WAN (IP)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: Минипорт WAN (L2TP)
Device: \DEVICE\{086A646B-DD01-48BE-8338-A8DD25C582CD}
GetStats failed for 'Минипорт WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: Intel(R) PRO/1000 MT Network Connection
Device: \DEVICE\{27516356-BB2F-47C6-A2C4-13C5D7D0688B}

Media State: Connected

Device State: Connected
Connect Time: 21:34:36
Media Speed: 100 Mbps

Packets Sent: 2559983
Bytes Sent (Optional): 0

Packets Received: 2373861
Directed Pkts Recd (Optional): 2303052
Bytes Received (Optional): 0
Directed Bytes Recd (Optional): 0

---------------------------------------------------------------------------
[PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

Adapter : Подключение по локальной сети
Adapter ID . . . . . . . . : {27516356-BB2F-47C6-A2C4-13C5D7D0688B}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : TBIH2
Description. . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address . . . . . : 00-30-48-77-85-02
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.1.79
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . : 192.168.1.79

IpConfig results . . . . . : Passed

AutoConfiguration results. . . . . . : Passed
AutoConfiguration is not in use.

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
TBIH2 <00> UNIQUE REGISTERED
HQ <00> GROUP REGISTERED
HQ <1C> GROUP REGISTERED
TBIH2 <20> UNIQUE REGISTERED
HQ <1B> UNIQUE REGISTERED
HQ <1E> GROUP REGISTERED
AladinHaspV01.2<30> UNIQUE REGISTERED
HQ <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

        Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
TBI <20> UNIQUE 192.168.1.11 585


WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
There are no WINS servers configured for this interface.
IPX test : IPX is not installed on this machine.


Global results:


IP General configuration
LMHOSTS Enabled. . . . . . . . : Yes
DNS for WINS resolution. . . . : Enabled
Node Type. . . . . . . . . . . : Broadcast
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : HQ
Dns domain name. . . . . . . . : hq.tbih-sb.com.ua
Dns forest name. . . . . . . . : hq.tbih-sb.com.ua
Domain Guid. . . . . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Sid . . . . . . . . . . : S-1-5-21-1481786424-387845897-614410136
Logon User . . . . . . . . . . : gabzya
Logon Domain . . . . . . . . . : HQ


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed
PASS - you have at least one non-autoconfigured IP address


IP loopback ping test. . . . . . . : Passed
PASS - pinging IP loopback address was successful.
Your IP stack is most probably OK.


Default gateway test . . . . . . . : Failed

[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.


NetBT name test. . . . . . . . . . : Passed
No NetBT scope defined
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 16
Description: MSAFD Tcpip [TCP/IP]
Provider Version :2
Max message size : Stream Oriented
Description: MSAFD Tcpip [UDP/IP]
Provider Version :2
Description: RSVP UDP Service Provider
Provider Version :6
Description: RSVP TCP Service Provider
Provider Version :6
Max message size : Stream Oriented
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{7E137140-5AA5-42A5-B0C5-C3F656B784F7}] SEQPACKET 5
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{7E137140-5AA5-42A5-B0C5-C3F656B784F7}] DATAGRAM 5
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E3603FF9-FD61-4006-BF7F-5ABCAF48A0B0}] SEQPACKET 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E3603FF9-FD61-4006-BF7F-5ABCAF48A0B0}] DATAGRAM 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{08DBE5B6-B4B9-43D2-85D5-7085EAEF130D}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{08DBE5B6-B4B9-43D2-85D5-7085EAEF130D}] DATAGRAM 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{BF8763F0-4306-45EB-8AEF-6B0318E6ED2E}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{BF8763F0-4306-45EB-8AEF-6B0318E6ED2E}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E79AF61E-813A-4159-8826-E4968E20BD19}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E79AF61E-813A-4159-8826-E4968E20BD19}] DATAGRAM 2
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {27516356-BB2F-47C6-A2C4-13C5D7D0688B}
DNS Domain:
DNS Servers: 192.168.1.79
IP Address: Expected registration with PDN (primary DNS domain name):
Hostname: TBIH2.hq.tbih-sb.com.ua.
Authoritative zone: hq.tbih-sb.com.ua.
Primary DNS server: TBIH2.hq.tbih-sb.com.ua 192.168.1.79
Authoritative NS:192.168.1.11 192.168.1.79
Check the DNS registration for DCs entries on DNS server '192.168.1.79'
The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.79 is:
DNS NAME = DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.11
A 192.168.1.79
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
A 192.168.1.79

The record on DNS server 192.168.1.79 is:
DNS NAME = ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
A 192.168.1.79
A 192.168.1.11
A 80.78.40.166
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is different on DNS server '192.168.1.79'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.168.1.79', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hq.tbih-sb.com.ua.
DNS DATA =
SRV 0 100 389 TBIH2.hq.tbih-sb.com.ua.

The record on DNS server 192.168.1.79 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.hq.tbih-sb.com.ua
DNS DATA =
SRV 0 100 389 tbih2.hq.tbih-sb.com.ua
SRV 0 100 389 tbi.hq.tbih-sb.com.ua
+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

The Record is correct on DNS server '192.168.1.79'.

PASS - All the DNS entries for DC are registered on DNS server '192.168.1.79' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
List of transports currently bound to the Redir
NetbiosSmb
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{27516356-BB2F-47C6-A2C4-13C5D7D0688B}
The browser is bound to 1 NetBt transport.
Mailslot test for HQ* passed.


DC discovery test. . . . . . . . . : Passed

Find DC in domain 'HQ':
Found this DC in domain 'HQ':
DC. . . . . . . . . . . : \\TBIH2.hq.tbih-sb.com.ua
Address . . . . . . . . : \\192.168.1.79
Domain Guid . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Name . . . . . . : hq.tbih-sb.com.ua
Forest Name . . . . . . : hq.tbih-sb.com.ua
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'HQ':
Found this PDC emulator in domain 'HQ':
DC. . . . . . . . . . . : \\TBIH2.hq.tbih-sb.com.ua
Address . . . . . . . . : \\192.168.1.79
Domain Guid . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Name . . . . . . : hq.tbih-sb.com.ua
Forest Name . . . . . . : hq.tbih-sb.com.ua
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find Windows 2000 DC in domain 'HQ':
Found this Windows 2000 DC in domain 'HQ':
DC. . . . . . . . . . . : \\TBIH2.hq.tbih-sb.com.ua
Address . . . . . . . . : \\192.168.1.79
Domain Guid . . . . . . : {772720F0-34AE-4C11-A892-D485DEA3EC84}
Domain Name . . . . . . : hq.tbih-sb.com.ua
Forest Name . . . . . . : hq.tbih-sb.com.ua
DC Site Name. . . . . . : Default-First-Site-Name
Our Site Name . . . . . : Default-First-Site-Name
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8


DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'HQ':
TBIH2.hq.tbih-sb.com.ua


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed
Cached Tickets:
Server: krbtgt/HQ.TBIH-SB.COM.UA
End Time: 6/28/2006 11:55:06
Renew Time: 7/4/2006 16:05:05
Server: krbtgt/HQ.TBIH-SB.COM.UA
End Time: 6/28/2006 11:55:06
Renew Time: 7/4/2006 16:05:05
Server: cifs/TBIH2.hq.tbih-sb.com.ua
End Time: 6/28/2006 11:55:06
Renew Time: 7/4/2006 16:05:05
Server: ldap/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
End Time: 6/28/2006 11:55:06
Renew Time: 7/4/2006 16:05:05
Server: cifs/TBI.hq.tbih-sb.com.ua
End Time: 6/28/2006 2:05:05
Renew Time: 7/4/2006 16:05:05
Server: host/tbih2.hq.tbih-sb.com.ua
End Time: 6/28/2006 2:02:55
Renew Time: 7/4/2006 16:02:55


LDAP test. . . . . . . . . . . . . : Passed

Do un-authenticated LDAP call to 'TBIH2.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060628065602.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 119 CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 102986
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 23 TBIH2.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 42 hq.tbih-sb.com.ua:tbih2$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 102 CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'TBIH2.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060628065602.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 119 CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 102986
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 23 TBIH2.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 42 hq.tbih-sb.com.ua:tbih2$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 102 CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'TBIH2.hq.tbih-sb.com.ua'.
Found 1 entries:
Attr: currentTime
Val: 17 20060628065602.0Z
Attr: subschemaSubentry
Val: 69 CN=Aggregate,CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: dsServiceName
Val: 119 CN=NTDS Settings,CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: namingContexts
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=DomainDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Val: 47 DC=ForestDnsZones,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: defaultNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: schemaNamingContext
Val: 56 CN=Schema,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: configurationNamingContext
Val: 46 CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: rootDomainNamingContext
Val: 29 DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 102986
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 23 TBIH2.hq.tbih-sb.com.ua
Attr: ldapServiceName
Val: 42 hq.tbih-sb.com.ua:tbih2$@HQ.TBIH-SB.COM.UA
Attr: serverName
Val: 102 CN=TBIH2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=hq,DC=tbih-sb,DC=com,DC=ua
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 0
Attr: forestFunctionality
Val: 1 0
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
ldap/TBIH2.hq.tbih-sb.com.ua/ForestDnsZones.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/DomainDnsZones.hq.tbih-sb.com.ua
DNS/TBIH2.hq.tbih-sb.com.ua
GC/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
HOST/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
HOST/TBIH2.hq.tbih-sb.com.ua/HQ
ldap/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2._msdcs.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/HQ
ldap/TBIH2
ldap/TBIH2.hq.tbih-sb.com.ua
ldap/TBIH2.hq.tbih-sb.com.ua/hq.tbih-sb.com.ua
E3514235-4B06-11D1-AB04-00C04FC2DCD2/a5c8ed3e-2f49-4298-b78b-6dd8a50801e2/hq.tbih-sb.com.ua
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/TBIH2.hq.tbih-sb.com.ua
HOST/TBIH2
HOST/TBIH2.hq.tbih-sb.com.ua


Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface Metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.79 192.168.1.79 10
192.168.1.79 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.1.255 255.255.255.255 192.168.1.79 192.168.1.79 10
224.0.0.0 240.0.0.0 192.168.1.79 192.168.1.79 10
255.255.255.255 255.255.255.255 192.168.1.79 192.168.1.79 1
No persistent route entries.


Netstat information test . . . . . : Passed


Interface Statistics

Received Sent
Unicast Packets 452502624 1414668743
Non-unicast packets 72030 1288
Discards 0 0
Errors 0 1
Unknown protocols 14 523820

Interface index = 1
Description = MS TCP Loopback interface
Type = 24
MTU = 1520
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 3982081261
Output Queue Length = 0


Interface index = 65539
Description = Intel(R) PRO/1000 MT Network Connection
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-30-48-77-85-02
Administrative Status = 1
Operational Status = 1
Last Changed = 3982081263
Output Queue Length = 0



Active Connections

Proto Local Address Foreign Address State
TCP TBIH2:domain TBIH2.hq.tbih-sb.com.ua:55516 LISTENING
TCP TBIH2:http TBIH2.hq.tbih-sb.com.ua:39022 LISTENING
TCP TBIH2:hosts2-ns TBIH2.hq.tbih-sb.com.ua:26878 LISTENING
TCP TBIH2:kerberos TBIH2.hq.tbih-sb.com.ua:32921 LISTENING
TCP TBIH2:epmap TBIH2.hq.tbih-sb.com.ua:59509 LISTENING
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:38958 LISTENING
TCP TBIH2:microsoft-ds TBIH2.hq.tbih-sb.com.ua:39048 LISTENING
TCP TBIH2:kpasswd TBIH2.hq.tbih-sb.com.ua:28838 LISTENING
TCP TBIH2:475 TBIH2.hq.tbih-sb.com.ua:2208 LISTENING
TCP TBIH2:http-rpc-epmap TBIH2.hq.tbih-sb.com.ua:18648 LISTENING
TCP TBIH2:ldaps TBIH2.hq.tbih-sb.com.ua:34902 LISTENING
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:57557 LISTENING
TCP TBIH2:1027 TBIH2.hq.tbih-sb.com.ua:47355 LISTENING
TCP TBIH2:1040 TBIH2.hq.tbih-sb.com.ua:6299 LISTENING
TCP TBIH2:1045 TBIH2.hq.tbih-sb.com.ua:45238 LISTENING
TCP TBIH2:1047 TBIH2.hq.tbih-sb.com.ua:53250 LISTENING
TCP TBIH2:1075 TBIH2.hq.tbih-sb.com.ua:2064 LISTENING
TCP TBIH2:2937 TBIH2.hq.tbih-sb.com.ua:39134 LISTENING
TCP TBIH2:msft-gc TBIH2.hq.tbih-sb.com.ua:6243 LISTENING
TCP TBIH2:msft-gc-ssl TBIH2.hq.tbih-sb.com.ua:53304 LISTENING
TCP TBIH2:ms-wbt-server TBIH2.hq.tbih-sb.com.ua:2224 LISTENING
TCP TBIH2:5900 TBIH2.hq.tbih-sb.com.ua:16470 LISTENING
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1037 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1038 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:1039 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:ms-olap4 ESTABLISHED
TCP TBIH2:1037 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:1038 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:1039 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:ms-olap4 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:3975 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:netbios-ssn TBIH2.hq.tbih-sb.com.ua:39096 LISTENING
TCP TBIH2:ldap TBI:3429 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:2384 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3552 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3557 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3558 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3600 TIME_WAIT
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3601 ESTABLISHED
TCP TBIH2:ldap TBIH2.hq.tbih-sb.com.ua:3602 TIME_WAIT
TCP TBIH2:microsoft-ds TBIH2.hq.tbih-sb.com.ua:3559 ESTABLISHED
TCP TBIH2:1025 TBI:1073 ESTABLISHED
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:1131 ESTABLISHED
TCP TBIH2:1025 TBIH2.hq.tbih-sb.com.ua:ms-sql-m ESTABLISHED
TCP TBIH2:1131 TBIH2.hq.tbih-sb.com.ua:1025 ESTABLISHED
TCP TBIH2:ms-sql-m TBIH2.hq.tbih-sb.com.ua:1025 ESTABLISHED
TCP TBIH2:2384 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:3232 TBIH2.hq.tbih-sb.com.ua:ldap CLOSE_WAIT
TCP TBIH2:ms-wbt-server gabzya.hq.tbih-sb.com.ua:1202 ESTABLISHED
TCP TBIH2:3510 TBIH2.hq.tbih-sb.com.ua:microsoft-ds TIME_WAIT
TCP TBIH2:3512 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:3513 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:3547 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:3548 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:3549 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:3551 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:3554 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:3555 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:3556 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:3559 TBIH2.hq.tbih-sb.com.ua:microsoft-ds ESTABLISHED
TCP TBIH2:3595 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:3596 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:3597 TBIH2.hq.tbih-sb.com.ua:netbios-ssn TIME_WAIT
TCP TBIH2:3599 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:3600 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:3601 TBIH2.hq.tbih-sb.com.ua:ldap ESTABLISHED
TCP TBIH2:3602 TBIH2.hq.tbih-sb.com.ua:ldap TIME_WAIT
TCP TBIH2:3603 TBIH2.hq.tbih-sb.com.ua:epmap TIME_WAIT
TCP TBIH2:3604 TBIH2.hq.tbih-sb.com.ua:1025 TIME_WAIT
TCP TBIH2:3993 TBIH2.hq.tbih-sb.com.ua:ldap CLOSE_WAIT
TCP TBIH2:4298 TBIH2.hq.tbih-sb.com.ua:ldap CLOSE_WAIT
TCP TBIH2:4330 TBIH2.hq.tbih-sb.com.ua:ldap CLOSE_WAIT
TCP TBIH2:4358 TBIH2.hq.tbih-sb.com.ua:ldap CLOSE_WAIT
TCP TBIH2:30583 TBIH2.hq.tbih-sb.com.ua:49239 LISTENING
UDP TBIH2:microsoft-ds *:*
UDP TBIH2:475 *:*
UDP TBIH2:isakmp *:*
UDP TBIH2:1029 *:*
UDP TBIH2:1030 *:*
UDP TBIH2:1035 *:*
UDP TBIH2:ipsec-msft *:*
UDP TBIH2:11000 *:*
UDP TBIH2:domain *:*
UDP TBIH2:ntp *:*
UDP TBIH2:1034 *:*
UDP TBIH2:1036 *:*
UDP TBIH2:1041 *:*
UDP TBIH2:1048 *:*
UDP TBIH2:1054 *:*
UDP TBIH2:1084 *:*
UDP TBIH2:1168 *:*
UDP TBIH2:1193 *:*
UDP TBIH2:1928 *:*
UDP TBIH2:2000 *:*
UDP TBIH2:3598 *:*
UDP TBIH2:3946 *:*
UDP TBIH2:3992 *:*
UDP TBIH2:4297 *:*
UDP TBIH2:4357 *:*
UDP TBIH2:domain *:*
UDP TBIH2:bootps *:*
UDP TBIH2:bootpc *:*
UDP TBIH2:kerberos *:*
UDP TBIH2:ntp *:*
UDP TBIH2:netbios-ns *:*
UDP TBIH2:netbios-dgm *:*
UDP TBIH2:389 *:*
UDP TBIH2:kpasswd *:*
UDP TBIH2:2535 *:*


IP Statistics

Packets Received = 2 576 108
Received Header Errors = 0
Received Address Errors = 56
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 0
Received Packets Delivered = 2 576 085
Output Requests = 2 130 285
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 46
Reassembly Successful = 23
Reassembly Failures = 0
Datagrams successfully fragmented = 23
Datagrams failing fragmentation = 0
Fragments Created = 46
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60


TCP Statistics

Active Opens = 4 472
Passive Opens = 10 450
Failed Connection Attempts = 22
Reset Connections = 193
Current Connections = 26
Received Segments = 2 515 195
Segment Sent = 2 098 743
Segment Retransmitted = 2 868
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 120 000
Maximum Number of Connections = -1


UDP Statistics

Datagrams Received = 50 397
No Ports = 4 831
Receive Errors = 0
Datagrams Sent = 18 658


ICMP Statistics

Received Sent
Messages 9 896 9 896
Errors 0 0
Destination Unreachable 14 14
Time Exceeded 0 0
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 0 0
Echos 6 203 6 203
Echo Replies 3 679 3 679
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0


Bindings test. . . . . . . . . . . : Passed
Component Name : NDIS-протокол ввода-вывода пользовательского режима
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : NDIS-протокол ввода-вывода пользовательского режима
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS-протокол ввода-вывода пользовательского режима
Lower Component: Intel(R) PRO/1000 MT Network Connection


Component Name : Протокол точка-точка по Ethernet
Bind Name: RasPppoe
Binding Paths:
Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Протокол точка-точка по Ethernet
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол точка-точка по Ethernet
Lower Component: Intel(R) PRO/1000 MT Network Connection


Component Name : Туннельный протокол точка-точка
Bind Name: mspptp
Binding Paths:

Component Name : Туннельный протокол уровня 2
Bind Name: msl2tp
Binding Paths:

Component Name : NDIS-драйвер WAN удаленного доступа
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Прямой параллельный порт

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Минипорт WAN (PPPoE)

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Минипорт WAN (PPTP)

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: Минипорт WAN (L2TP)

Owner of the binding path : NDIS-драйвер WAN удаленного доступа
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: NDIS-драйвер WAN удаленного доступа
Lower Component: RAS асинхронный адаптер


Component Name : Протокол сообщений TCP/IP (сеанс SMB)
Bind Name: NetbiosSmb
Binding Paths:

Component Name : Протокол клиента WINS (TCP/IP)
Bind Name: NetBT
Binding Paths:
Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Протокол клиента WINS (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Протокол Интернета (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Протокол Интернета (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (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: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Веб-клиент
Bind Name: WebClient
Binding Paths:

Component Name : DHCP-сервер
Bind Name: DHCPServer
Binding Paths:

Component Name : Беспроводная настройка
Bind Name: wzcsvc
Binding Paths:

Component Name : Балансировка нагрузки сети
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Балансировка нагрузки сети
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Балансировка нагрузки сети
Lower Component: Intel(R) PRO/1000 MT Network Connection


Component Name : Сервер маршрутизации и удаленного доступа
Bind Name: RemoteAccess
Binding Paths:

Component Name : Сервер удаленного доступа
Bind Name: msrassrv
Binding Paths:

Component Name : Диспетчер подключений удаленного доступа
Bind Name: RasMan
Binding Paths:

Component Name : Клиент удаленного доступа
Bind Name: msrascli
Binding Paths:

Component Name : Служба доступа к файлам и принтерам сетей Microsoft
Bind Name: LanmanServer
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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

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: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (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: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Интерфейс NetBIOS
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection #2

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndis5
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Intel(R) PRO/1000 MT Network Connection

Owner of the binding path : Интерфейс NetBIOS
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Интерфейс NetBIOS
Lower Component: Протокол клиента WINS (TCP/IP)
-Interface Name: tdi
Upper Component: Протокол клиента WINS (TCP/IP)
Lower Component: Протокол Интернета (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Протокол Интернета (TCP/IP)
Lower Component: Минипорт WAN (IP)


Component Name : Общий классификатор пакетов
Bind Name: Gpc
Binding Paths:

Component Name : Шлюз уровня приложения
Bind Name: ALG
Binding Paths:

Component Name : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2
Bind Name: {7E137140-5AA5-42A5-B0C5-C3F656B784F7}
Binding Paths:

Component Name : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
Bind Name: {E3603FF9-FD61-4006-BF7F-5ABCAF48A0B0}
Binding Paths:

Component Name : Intel(R) PRO/1000 MT Network Connection #2
Bind Name: {08DBE5B6-B4B9-43D2-85D5-7085EAEF130D}
Binding Paths:

Component Name : Intel(R) PRO/1000 MT Network Connection
Bind Name: {27516356-BB2F-47C6-A2C4-13C5D7D0688B}
Binding Paths:

Component Name : Минипорт WAN (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Прямой параллельный порт
Bind Name: {82BAF363-CE31-4BF7-BA44-E2DAF1C7FE4B}
Binding Paths:

Component Name : Минипорт WAN (PPPoE)
Bind Name: {0F6D569A-3C96-4B3F-B08C-127778B7FF50}
Binding Paths:

Component Name : Минипорт WAN (PPTP)
Bind Name: {1C7F08B6-2726-4CE3-8B66-00C05B8C04AC}
Binding Paths:

Component Name : Минипорт WAN (L2TP)
Bind Name: {086A646B-DD01-48BE-8338-A8DD25C582CD}
Binding Paths:

Component Name : RAS асинхронный адаптер
Bind Name: {3CB73B49-3F8E-4341-8CBA-E5F3123703B7}
Binding Paths:



WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
[/more] тут вроде тоже....
Автор: levkadub
Дата сообщения: 29.06.2006 13:53

Цитата:
1 Пускаем АД сайты и службы
2 Создаем новый сайт. Связь берем по умолчанию
3 Создаем новую подсеть. И связываем с новым сайтом.
4 Нужный контроллер домена переносишь в нужный сайт. Смотри, чтобы ИП адреса подсети и КД соответствовали.
5 Новое подключение должно создасься автоматически через некоторое время (~15 мин)

как перенести пользователей и компы на этот сайт?
Автор: G14
Дата сообщения: 29.06.2006 14:42
levkadub

Цитата:
как перенести пользователей и компы на этот сайт?

пользователей в сайт не переносят
САЙТ - это отражение физической структуры сети, в которой располагается домен AD. Для того, чтобы перенести контроллер в нужный сайт достаточно в AD S&S в контекстном меню этого сервера выбрать move и показать куда перенести (ну и конечно у этого DC должен быть ip из подсети сайта). Для клиентских машин принадлежности к сайту определяется ИХ ip-адресом. Достаточно дать клиенту правильный ip и он сам определит в каком он сайте исходя из своего ip.
Автор: Gabzya
Дата сообщения: 29.06.2006 15:17
G14
а как по поводу моего поста? нормальные показатели?

Цитата:
2. смотрим, чтобы на ней были разрешены динамические обновления

стоит-ТОлько безопасные
тут же сотрю и еще в некот местах на закладке серверы имен еще присутствует старый сервер... нужно его грохнуть?

вот это интересует тоже....
Автор: G14
Дата сообщения: 29.06.2006 17:41
Gabzya

Цитата:
нормальные показатели?

да, вполне.

Цитата:
нужно его грохнуть?

Если на нем больше нет DNS, то да.
Автор: Gabzya
Дата сообщения: 29.06.2006 19:39
G14
последнее, как проверить что все в порядке с ДНС?
Просто вроде все работает но не так....
например почта долго уходит....



Добавлено:
еще есть например на серваке консоль управления сервером антивирусной защиты, так он перестал получать инф о ПК....
может что-то с именами? nslookup может как-то проверить или еще что?

Добавлено:
nslookup вроде пашет
может это подскажет, на сервере каждые 5минут ошибка, в журнале приложений:

Цитата:
Тип события: Предупреждение
Источник события: SceCli
Категория события: Отсутствует
Код события: 1202
Дата: 29.06.2006
Время: 19:43:18
Пользователь: Н/Д
Компьютер: TBIH2
Описание:
Выполнено распространение политики безопасности с предупреждением. 0x5 : Отказано в доступе.

Справка по данному вопросу размещена на веб-узле http://support.microsoft.com. Запросите "troubleshooting 1202 events".

Дополнительные сведения можно найти в центре справки и поддержки, в "http://go.microsoft.com/fwlink/events.asp".

Автор: G14
Дата сообщения: 30.06.2006 09:30

Цитата:
Источник события: SceCli
Категория события: Отсутствует
Код события: 1202

А самостоятельно набрать "scecli 1202 Access denied" в поиске на microsoft.com ты не способен?

Цитата:
последнее, как проверить что все в порядке с ДНС?

http://search.microsoft.com/results.aspx?q=troubleshooting+dns&l=1&mkt=en-US&FORM=SSME
Автор: Gabzya
Дата сообщения: 30.06.2006 10:10

Цитата:
самостоятельно набрать

способен, только самостоятельно осилить инглиш неспособен, или ты думаешь, что все по умолчанию им владеют, конечно же я находил на мелкософте, но там на инглиш, а я с ним недружу, поэтому решил спросить на любимом форуме, а ты... футболишь...
Автор: G14
Дата сообщения: 30.06.2006 12:49
Gabzya

Цитата:
но там на инглиш, а я с ним недружу, поэтому решил спросить на любимом форуме, а ты... футболишь...

Для тех, кто не дружит:
Открывается первая же ссылка из приведенного мной поиска описания ошибки 1202 на MS-сайте. Справа есть выпадающий список языков. Выбираем тот с которым дружим и жмем кнопку со стрелкой. Что, это трудно было сделать ?
Конечно проще всего даже не пытаться помочь СЕБЕ, а просто ждать когда кто-то придет и все найдет и "разжует" . И публично страдать по поводу своей "несчастности".
Автор: Gabzya
Дата сообщения: 30.06.2006 14:47

Цитата:
Открывается первая же ссылка из приведенного мной поиска описания ошибки 1202 на MS-сайте. Справа есть выпадающий список языков. Выбираем тот с которым дружим и жмем кнопку со стрелкой. Что, это трудно было сделать ?
да нету этой статьи на руссс есть на френч, испан, и еще всякие там инако

Цитата:
Конечно проще всего даже не пытаться помочь СЕБЕ, а просто ждать когда кто-то придет и все найдет и "разжует" . И публично страдать по поводу своей "несчастности".

зря ты так

Добавлено:
ооо появилась и на русс
раньше небыло, вот собственно и она
ща попробую

Добавлено:
статья не помогла.... в ней пункт 3 результата не дает
есть еще варианты?
Автор: levkadub
Дата сообщения: 30.06.2006 18:34
создал сайт, поставил дополнительный контроллер домена, затем перенес его на этот сайт. создал подсеть для нового сайта 10,0,2,0 255,255,0,0
ip нового сервера - 10.0.2.2 255.255.0.0

делаю dcdiag и netdiag на основном и резервном контроллерах домена.

основной
[more]
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\PDC
Starting test: Connectivity
......................... PDC passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\PDC
Starting test: Replications
......................... PDC passed test Replications
Starting test: NCSecDesc
......................... PDC passed test NCSecDesc
Starting test: NetLogons
......................... PDC passed test NetLogons
Starting test: Advertising
......................... PDC passed test Advertising
Starting test: KnowsOfRoleHolders
......................... PDC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... PDC passed test RidManager
Starting test: MachineAccount
......................... PDC passed test MachineAccount
Starting test: Services
......................... PDC passed test Services
Starting test: ObjectsReplicated
......................... PDC passed test ObjectsReplicated
Starting test: frssysvol
......................... PDC passed test frssysvol
Starting test: frsevent
......................... PDC passed test frsevent
Starting test: kccevent
......................... PDC passed test kccevent
Starting test: systemlog
......................... PDC passed test systemlog
Starting test: VerifyReferences
......................... PDC passed test VerifyReferences

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 : energosib
Starting test: CrossRefValidation
......................... energosib passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... energosib passed test CheckSDRefDom

Running enterprise tests on : energosib.irk.ru
Starting test: Intersite
......................... energosib.irk.ru passed test Intersite
Starting test: FsmoCheck
......................... energosib.irk.ru passed test FsmoCheck

C:\Program Files\Support Tools>netdiag

....................................

Computer Name: PDC
DNS Host Name: pdc.energosib.irk.ru
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB896688
KB898715
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB904942
KB905414
KB905915
KB908519
KB908521
KB908531
KB910437
KB911562
KB911567
KB911927
KB912812
KB912919
KB913446
Q147222


Netcard queries test . . . . . . . : Passed
GetStats failed for '&#9575;Ё ьющ ярЁрыыхы№э&#8730;щ яюЁЄ'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card '&#9568;шэшяюЁЄ WAN (PPTP)' may not be working because it h
as not received any packets.
[WARNING] The net card '&#9568;шэшяюЁЄ WAN (PPPoE)' may not be working because it
has not received any packets.
[WARNING] The net card '&#9568;шэшяюЁЄ WAN (IP)' may not be working because it has
not received any packets.
GetStats failed for '&#9568;шэшяюЁЄ WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

Adapter : &#9575;юфъы&#9632;ўхэшх яю ыюъры№эющ ёхЄш

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : pdc
IP Address . . . . . . . . : 10.0.0.10
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . : 10.0.0.1
Dns Servers. . . . . . . . : 127.0.0.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{B5B4BCDC-40AC-47E9-B6F1-050C337E1D1D}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '127.0.0.1' a
nd other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{B5B4BCDC-40AC-47E9-B6F1-050C337E1D1D}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{B5B4BCDC-40AC-47E9-B6F1-050C337E1D1D}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully [/more]


дополнительный


[more] Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: vssep\BDC
Starting test: Connectivity
......................... BDC passed test Connectivity

Doing primary tests

Testing server: vssep\BDC
Starting test: Replications
......................... BDC passed test Replications
Starting test: NCSecDesc
......................... BDC passed test NCSecDesc
Starting test: NetLogons
......................... BDC passed test NetLogons
Starting test: Advertising
......................... BDC passed test Advertising
Starting test: KnowsOfRoleHolders
......................... BDC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BDC passed test RidManager
Starting test: MachineAccount
......................... BDC passed test MachineAccount
Starting test: Services
......................... BDC passed test Services
Starting test: ObjectsReplicated
......................... BDC passed test ObjectsReplicated
Starting test: frssysvol
......................... BDC passed test frssysvol
Starting test: frsevent
......................... BDC passed test frsevent
Starting test: kccevent
......................... BDC passed test kccevent
Starting test: systemlog
......................... BDC passed test systemlog
Starting test: VerifyReferences
......................... BDC passed test VerifyReferences

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 : energosib
Starting test: CrossRefValidation
......................... energosib passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... energosib passed test CheckSDRefDom

Running enterprise tests on : energosib.irk.ru
Starting test: Intersite
......................... energosib.irk.ru passed test Intersite
Starting test: FsmoCheck
......................... energosib.irk.ru passed test FsmoCheck

C:\Program Files\Support Tools>netdiag

....................................

Computer Name: BDC
DNS Host Name: bdc.energosib.irk.ru
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : x86 Family 15 Model 4 Stepping 1, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB898715
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB905414
KB905915
KB908519
KB908521
KB910437
KB911927
KB912919
KB913446
Q147222


Netcard queries test . . . . . . . : Passed
GetStats failed for '¦Ё ьющ ярЁрыыхы№эvщ яюЁЄ'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card '¦шэшяюЁЄ WAN (PPTP)' may not be working because it h
as not received any packets.
[WARNING] The net card '¦шэшяюЁЄ WAN (PPPoE)' may not be working because it
has not received any packets.
[WARNING] The net card '¦шэшяюЁЄ WAN (IP)' may not be working because it has
not received any packets.
GetStats failed for '¦шэшяюЁЄ WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

Adapter : lan

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : bdc
IP Address . . . . . . . . : 10.0.2.2
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . : 10.0.0.1
Dns Servers. . . . . . . . : 10.0.0.10


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{138A8083-3D69-4CC2-BEF8-2E8B2CBD1179}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '10.0.0.10' a
nd other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{138A8083-3D69-4CC2-BEF8-2E8B2CBD1179}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{138A8083-3D69-4CC2-BEF8-2E8B2CBD1179}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Passed
Secure channel for domain 'ENERGOSIB' is to '\\pdc.energosib.irk.ru'.


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
[/more]
по видимому надо было указать для сайта другую подсеть например 10,1,0,0
и соответственно назначить ip - BDC.
если я сейчас укажу другую подсеть в оснастке сайты и службы и назначу BDC ip из этой подсети будет ли все нормально работать? или смена ip может повлиять только на репликацию между контроллерами?
может проще с BDC удалить роль контроллера домена а потом все поменять?
как сделать правильно?

судя по тестам счас все ГУТ.
Автор: G14
Дата сообщения: 01.07.2006 06:31
levkadub

Цитата:
подсеть для нового сайта 10,0,2,0 255,255,0,0

Странная подсеть какая то..... Может 10.0.2.0 255.255.255.0 ?

Цитата:
ip нового сервера - 10.0.2.2 255.255.0.0

Значит все, что имеет адреса 10.0.* в одной подсети.

Цитата:
может проще

Проще всего (и правильнее) привести подсети в порядок. И физически и в AD S&S. И адреса хостов.
Gabzya

Цитата:
в ней пункт 3 результата не дает

если не можешь найти командой - скопируй winlogon.log куда нибудь и поищи в нем слово error , например far'ом.....или в блокноте открой...
Автор: levkadub
Дата сообщения: 01.07.2006 11:46

Цитата:
Странная подсеть какая то..... Может 10.0.2.0 255.255.255.0 ?

ничего странного просто в сети больше 300 компов вот и сделал такую -чтоб больше не вспоминать об этом.

привел все в порядок. но роль КД на bdc не удалял.... (правильно ли сделал?)
просто сменил айпи.
теперь второй КД на 2-м сайте имет айпи 10,2,2,2
ходит через шлюз 10,2,2,1 маска подсети 255,255,0,0
пинги и проч. ходят и туда и обратно.

но что-то очень много ошибок в ДНС и в службе каталогов.

Автор: G14
Дата сообщения: 01.07.2006 12:42
levkadub

Цитата:
но что-то очень много ошибок в ДНС и в службе каталогов.

не надо нам эти ошибки показывать, а то вдруг кто-то по ним поймет в чем твоя проблема и напишет как она решается....

Цитата:
теперь второй КД на 2-м сайте имет айпи 10,2,2,2

В AD S&S подсеть определяющую сайт поправил?
Автор: levkadub
Дата сообщения: 01.07.2006 13:13

Цитата:
В AD S&S подсеть определяющую сайт поправил?

поправил.

Цитата:
не надо нам эти ошибки показывать, а то вдруг кто-то по ним поймет в чем твоя проблема и напишет как она решается....

не надо посмеиватся - их там реально много - я exchange 2003 ставлю - forestprep и domainprep много чего меняют в АД. (комманды запускал на первом контроллере)
а остальным контроллерам это не очень нравится- начинают свои базы АД править.
особенно много ошибок у службы каталогов

вопрос если соединение с серверами создается автоматом (при переносе или создании сервера в другом сайте) то транспорт - RPC
я для BDC - руками сначала указал IP соответственно - RPC не создан.
получается такая ситуация с одним сервером у PDC соединение по IP а с другим по RPC. это нормально?

вот наиболее часто встречающаяся ошибка:
[more] Тип события:    Ошибка
Источник события:    NTDS Replication
Категория события:    DS RPC-клиент
Код события:    1411
Дата:        01.07.2006
Время:        17:23:25
Пользователь:        NT AUTHORITY\АНОНИМНЫЙ ВХОД
Компьютер:    PDC
Описание:
Active Directory не удалось собрать имя участника службы взаимной проверки подлинности для следующего контроллера домена.

Контроллер домена:
ab5631b1-4008-4db8-9cbe-44c6adbdd7cb._msdcs.energosib.irk.ru

Вызов отклонен. Возможно, это повлияет на связь с этим контроллером домена.

Дополнительные данные
Значение ошибки:
8589 Служба каталогов не может создать имя участника службы (SPN), с помощью которого будет выполняться взаимная проверка подлинности с сервером, так как у соответствующего объекта для сервера в локальной базе данных службы каталогов отсутствует атрибут serverReference.

Дополнительные сведения можно найти в центре справки и поддержки, в "http://go.microsoft.com/fwlink/events.asp".
[/more]


Автор: G14
Дата сообщения: 01.07.2006 14:17
levkadub

Цитата:
я exchange 2003 ставлю - forestprep и domainprep

Ох зряяя....В проблемном домене такие операции....Ну да впрочем дело твое.

Цитата:
ab5631b1-4008-4db8-9cbe-44c6adbdd7cb._msdcs.energosib.irk.ru

Кто это? Это живой контроллер или нет?
При таких ошибках dcdiag должен ругаться, в нем есть ошибки....?
По одной этой ошибке, не зная, что происходило в твоей сети последнее время, я могу только предположить, что некорректно удалялись контроллеры...возможно удалялись серверы или коннекшн-объекты руками из AD S&S....
Пока могу предложить почитать вот эти статьи, возможно ты найдешь в них описание своей ситуации....

Цитата:
получается такая ситуация с одним сервером у PDC соединение по IP а с другим по RPC. это нормально?

Сложно сказать не зная полной картины, я ведь не знаю, что ты имеешь в виду под " с одним сервером" и "с другим", где они, в одном сайте или нет.... У меня между сайтами IP, внутри есессно RPC.

PS. To ALL. Поймите, чем более полную картину происходящего вы описываете (со всеми ошибками, описанием что делали, описанием своих сетей и т.п.) тем больше у вас шансов, что кто-то разберется что у вас происходит и подскажет что вам делать.

Страницы: 1234567891011

Предыдущая тема: Публикация FTP-сервера через ISA на нестандартный порт


Форум Ru-Board.club — поднят 15-09-2016 числа. Цель - сохранить наследие старого Ru-Board, истории становления российского интернета. Сделано для людей.