Top-Themen

AppleEntwicklungHardwareInternetLinuxMicrosoftMultimediaNetzwerkeOff TopicSicherheitSonstige SystemeVirtualisierungWeiterbildungZusammenarbeit

Aktuelle Themen

Administrator.de FeedbackApache ServerAppleAssemblerAudioAusbildungAuslandBackupBasicBatch & ShellBenchmarksBibliotheken & ToolkitsBlogsCloud-DiensteClusterCMSCPU, RAM, MainboardsCSSC und C++DatenbankenDatenschutzDebianDigitiales FernsehenDNSDrucker und ScannerDSL, VDSLE-BooksE-BusinessE-MailEntwicklungErkennung und -AbwehrExchange ServerFestplatten, SSD, RaidFirewallFlatratesGoogle AndroidGrafikGrafikkarten & MonitoreGroupwareHardwareHosting & HousingHTMLHumor (lol)Hyper-VIconsIDE & EditorenInformationsdiensteInstallationInstant MessagingInternetInternet DomäneniOSISDN & AnaloganschlüsseiTunesJavaJavaScriptKiXtartKVMLAN, WAN, WirelessLinuxLinux DesktopLinux NetzwerkLinux ToolsLinux UserverwaltungLizenzierungMac OS XMicrosoftMicrosoft OfficeMikroTik RouterOSMonitoringMultimediaMultimedia & ZubehörNetzwerkeNetzwerkgrundlagenNetzwerkmanagementNetzwerkprotokolleNotebook & ZubehörNovell NetwareOff TopicOpenOffice, LibreOfficeOutlook & MailPapierkorbPascal und DelphiPeripheriegerätePerlPHPPythonRechtliche FragenRedHat, CentOS, FedoraRouter & RoutingSambaSAN, NAS, DASSchriftartenSchulung & TrainingSEOServerServer-HardwareSicherheitSicherheits-ToolsSicherheitsgrundlagenSolarisSonstige SystemeSoziale NetzwerkeSpeicherkartenStudentenjobs & PraktikumSuche ProjektpartnerSuseSwitche und HubsTipps & TricksTK-Netze & GeräteUbuntuUMTS, EDGE & GPRSUtilitiesVB for ApplicationsVerschlüsselung & ZertifikateVideo & StreamingViren und TrojanerVirtualisierungVisual StudioVmwareVoice over IPWebbrowserWebentwicklungWeiterbildungWindows 7Windows 8Windows 10Windows InstallationWindows MobileWindows NetzwerkWindows ServerWindows SystemdateienWindows ToolsWindows UpdateWindows UserverwaltungWindows VistaWindows XPXenserverXMLZusammenarbeit

Ereigniskennung 13508 Fehler bei Replikation (Domänencontroller wechsel)

Frage Microsoft Windows Server

Mitglied: Nati1003

Nati1003 (Level 1) - Jetzt verbinden

11.02.2009, aktualisiert 12:49 Uhr, 6638 Aufrufe, 8 Kommentare

Hallo,

ich habe ein Problem mit meinem neuen Server. Und zwar steht in der Ereignissanzeige bei Dateireplikation immer folgender Fehler:

"Der Dateireplikationsdienst konnte die Replikation von \\server1.dom.local nach SERVER2 für c:\windows\sysvol\domain mit DNS-Namen \\server1.dom.local nicht aktivieren. Es wird ein neuer Versuch gestartet. "

So wie ich das bei meiner bisherigen Recherche rausfinden konnte soll das Problem wohl irgendwie bei den DNS Einträgen zu suchen sein. Allerdings finde ich dort keinen fehler.

Ausgangssituation ist, dass es einen alten DC (server1) mit w2k3 und einen neuen DC (server2) mit w2k3, der erstmal paralell laufen soll und später nur noch alleine. (Der alte Server soll entfernt werden.)

dcdiag /fic gibt noch folgendes zurück:

01.
Performing initial setup: 
02.
   Done gathering initial info. 
03.
 
04.
Doing initial required tests 
05.
 
06.
   Testing server: Standardname-des-ersten-Standorts\SERVER2 
07.
      Starting test: Connectivity 
08.
         ......................... SERVER2 passed test Connectivity 
09.
 
10.
Doing primary tests 
11.
 
12.
   Testing server: Standardname-des-ersten-Standorts\SERVER2 
13.
      Starting test: Replications 
14.
         [server1] DsBindWithSpnEx() failed with error 1722, 
15.
         Der RPC-Server ist nicht verfügbar.. 
16.
         ......................... SERVER2 passed test Replications 
17.
      Starting test: NCSecDesc 
18.
         ......................... SERVER2 passed test NCSecDesc 
19.
      Starting test: NetLogons 
20.
         Unable to connect to the NETLOGON share! (\\SERVER2\netlogon) 
21.
         [SERVER2] An net use or LsaPolicy operation failed with error 1203, D 
22.
er angegebene Netzwerkpfad wurde von keinem Netzwerkdienstanbieter angenommen.. 
23.
         ......................... SERVER2 failed test NetLogons 
24.
      Starting test: Advertising 
25.
         Warning: DsGetDcName returned information for \\server1.RTLasertechni 
26.
k.local, when we were trying to reach SERVER2. 
27.
         Server is not responding or is not considered suitable. 
28.
         [server1] LDAP search failed with error 58, 
29.
         Der angegebene Server kann den angeforderten Vorgang nicht ausführen.. 
30.
         Server SERVER2 is advertising as a global catalog, but 
31.
         it could not be verified that the server thought it was a GC. 
32.
         ......................... SERVER2 failed test Advertising 
33.
      Starting test: KnowsOfRoleHolders 
34.
         ......................... SERVER2 passed test KnowsOfRoleHolders 
35.
      Starting test: RidManager 
36.
         ......................... SERVER2 passed test RidManager 
37.
      Starting test: MachineAccount 
38.
         ......................... SERVER2 passed test MachineAccount 
39.
      Starting test: Services 
40.
         ......................... SERVER2 passed test Services 
41.
      Starting test: ObjectsReplicated 
42.
         ......................... SERVER2 passed test ObjectsReplicated 
43.
      Starting test: frssysvol 
44.
         ......................... SERVER2 passed test frssysvol 
45.
      Starting test: frsevent 
46.
         There are warning or error events within the last 24 hours after the 
47.
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause 
48.
         Group Policy problems. 
49.
         ......................... SERVER2 failed test frsevent 
50.
      Starting test: kccevent 
51.
         ......................... SERVER2 passed test kccevent 
52.
      Starting test: systemlog 
53.
         An Error Event occured.  EventID: 0x00000416 
54.
            Time Generated: 02/11/2009   11:44:29 
55.
            (Event String could not be retrieved) 
56.
         ......................... SERVER2 failed test systemlog 
57.
      Starting test: VerifyReferences 
58.
         ......................... SERVER2 passed test VerifyReferences 
59.
 
60.
   Running partition tests on : ForestDnsZones 
61.
      Starting test: CrossRefValidation 
62.
         ......................... ForestDnsZones passed test CrossRefValidation 
63.
 
64.
      Starting test: CheckSDRefDom 
65.
         ......................... ForestDnsZones passed test CheckSDRefDom 
66.
 
67.
   Running partition tests on : DomainDnsZones 
68.
      Starting test: CrossRefValidation 
69.
         ......................... DomainDnsZones passed test CrossRefValidation 
70.
 
71.
      Starting test: CheckSDRefDom 
72.
         ......................... DomainDnsZones passed test CheckSDRefDom 
73.
 
74.
   Running partition tests on : Schema 
75.
      Starting test: CrossRefValidation 
76.
         ......................... Schema passed test CrossRefValidation 
77.
      Starting test: CheckSDRefDom 
78.
         ......................... Schema passed test CheckSDRefDom 
79.
 
80.
   Running partition tests on : Configuration 
81.
      Starting test: CrossRefValidation 
82.
         ......................... Configuration passed test CrossRefValidation 
83.
      Starting test: CheckSDRefDom 
84.
         ......................... Configuration passed test CheckSDRefDom 
85.
 
86.
   Running partition tests on : dom 
87.
      Starting test: CrossRefValidation 
88.
         ......................... dom passed test CrossRefValidation 
89.
 
90.
      Starting test: CheckSDRefDom 
91.
         ......................... dom passed test CheckSDRefDom 
92.
 
93.
   Running enterprise tests on : dom.local 
94.
      Starting test: Intersite 
95.
         ......................... dom.local passed test Intersite 
96.
      Starting test: FsmoCheck 
97.
         ......................... dom.local passed test FsmoCheck 
98.
 

netdiag /fix folgendes:

01.
C:\Dokumente und Einstellungen\Administrator.dom>netdiag /fix 
02.
 
03.
.................................... 
04.
 
05.
    Computer Name: server2 
06.
    DNS Host Name: server2.dom.local 
07.
    System info : Microsoft Windows Server 2003 R2 (Build 3790) 
08.
    Processor : x86 Family 6 Model 23 Stepping 10, GenuineIntel 
09.
    List of installed hotfixes : 
10.
        KB924667-v2 
11.
        KB925398_WMP64 
12.
        KB925902-v2 
13.
        KB926122 
14.
        KB927891 
15.
        KB929123 
16.
        KB930178 
17.
        KB932168 
18.
        KB933729 
19.
        KB933854 
20.
        KB935839 
21.
        KB935840 
22.
        KB936357 
23.
        KB936782 
24.
        KB938127 
25.
        KB938464 
26.
        KB941569 
27.
        KB943055 
28.
        KB943460 
29.
        KB943485 
30.
        KB944338-v2 
31.
        KB944653 
32.
        KB945553 
33.
        KB946026 
34.
        KB948496 
35.
        KB948745 
36.
        KB949014 
37.
        KB950762 
38.
        KB950974 
39.
        KB951066 
40.
        KB951698 
41.
        KB951746 
42.
        KB951748 
43.
        KB952069 
44.
        KB952954 
45.
        KB954211 
46.
        KB954600 
47.
        KB955069 
48.
        KB955839 
49.
        KB956391 
50.
        KB956802 
51.
        KB956803 
52.
        KB956841 
53.
        KB957097 
54.
        KB958215 
55.
        KB958644 
56.
        KB958687 
57.
        KB960714 
58.
        Q147222 
59.
 
60.
 
61.
Netcard queries test . . . . . . . : Passed 
62.
    GetStats failed for 'Parallelanschluss (direkt)'. [ERROR_NOT_SUPPORTED] 
63.
    [WARNING] The net card 'WAN-Miniport (PPTP)' may not be working because it h 
64.
as not received any packets. 
65.
    [WARNING] The net card 'WAN-Miniport (PPPOE)' may not be working because it 
66.
has not received any packets. 
67.
    [WARNING] The net card 'WAN-Miniport (IP)' may not be working because it has 
68.
 not received any packets. 
69.
    [WARNING] The net card 'WAN-Miniport (Netzwerkmonitor)' may not be working b 
70.
ecause it has not received any packets. 
71.
    GetStats failed for 'WAN-Miniport (L2TP)'. [ERROR_NOT_SUPPORTED] 
72.
 
73.
 
74.
 
75.
Per interface results: 
76.
 
77.
    Adapter : Team 1 
78.
 
79.
        Netcard queries test . . . : Passed 
80.
 
81.
        Host Name. . . . . . . . . : server2 
82.
        IP Address . . . . . . . . : 192.168.5.4 
83.
        Subnet Mask. . . . . . . . : 255.255.255.0 
84.
        Default Gateway. . . . . . : 192.168.5.254 
85.
        Dns Servers. . . . . . . . : 192.168.5.4 
86.
                                     192.168.5.1 
87.
 
88.
 
89.
        AutoConfiguration results. . . . . . : Passed 
90.
 
91.
        Default gateway test . . . : Passed 
92.
 
93.
        NetBT name test. . . . . . : Passed 
94.
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge 
95.
r Service', <20> 'WINS' names is missing. 
96.
 
97.
        WINS service test. . . . . : Skipped 
98.
            There are no WINS servers configured for this interface. 
99.
 
100.
 
101.
Global results: 
102.
 
103.
 
104.
Domain membership test . . . . . . : Failed 
105.
    [WARNING] Ths system volume has not been completely replicated to the local 
106.
machine. This machine is not working properly as a DC. 
107.
 
108.
 
109.
NetBT transports test. . . . . . . : Passed 
110.
    List of NetBt transports currently configured: 
111.
        NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E} 
112.
    1 NetBt transport currently configured. 
113.
 
114.
 
115.
Autonet address test . . . . . . . : Passed 
116.
 
117.
 
118.
IP loopback ping test. . . . . . . : Passed 
119.
 
120.
 
121.
Default gateway test . . . . . . . : Passed 
122.
 
123.
 
124.
NetBT name test. . . . . . . . . . : Passed 
125.
    [WARNING] You don't have a single interface with the <00> 'WorkStation Servi 
126.
ce', <03> 'Messenger Service', <20> 'WINS' names defined. 
127.
 
128.
 
129.
Winsock test . . . . . . . . . . . : Passed 
130.
 
131.
 
132.
DNS test . . . . . . . . . . . . . : Passed 
133.
    PASS - All the DNS entries for DC are registered on DNS server '192.168.5.4' 
134.
 and other DCs also have some of the names registered. 
135.
 
136.
 
137.
Redir and Browser test . . . . . . : Passed 
138.
    List of NetBt transports currently bound to the Redir 
139.
        NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E} 
140.
    The redir is bound to 1 NetBt transport. 
141.
 
142.
    List of NetBt transports currently bound to the browser 
143.
        NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E} 
144.
    The browser is bound to 1 NetBt transport. 
145.
 
146.
 
147.
DC discovery test. . . . . . . . . : Passed 
148.
 
149.
 
150.
DC list test . . . . . . . . . . . : Passed 
151.
 
152.
 
153.
Trust relationship test. . . . . . : Skipped 
154.
 
155.
 
156.
Kerberos test. . . . . . . . . . . : Passed 
157.
 
158.
 
159.
LDAP test. . . . . . . . . . . . . : Passed 
160.
 
161.
 
162.
Bindings test. . . . . . . . . . . : Passed 
163.
 
164.
 
165.
WAN configuration test . . . . . . : Skipped 
166.
    No active remote access connections. 
167.
 
168.
 
169.
Modem diagnostics test . . . . . . : Passed 
170.
 
171.
IP Security test . . . . . . . . . : Skipped 
172.
 
173.
    Note: run "netsh ipsec dynamic show /?" for more detailed information 
174.
 
175.
 
176.
The command completed successfully 
177.
 
178.
C:\Dokumente und Einstellungen\Administrator.dom>
Ich hoffe ihr könnt mir ein parr Anregungen geben! Weiß nicht mehr was ich noch machen soll...


Gruß Nati1003
Mitglied: farol50
11.02.2009 um 12:30 Uhr
@Nati
Bei mir war der Fehler weg, nachdem ich den Server bei Microsoft aktiviert hatte.

Gruß

farol
Bitte warten ..
Mitglied: Nati1003
11.02.2009 um 12:36 Uhr
Also habe die Änderungen zwar vor der Aktivierung gemacht, aber mittlerweile ist der Server aktiviert und der Fehler besteht immer noch!

Was mir ja komisch vorkommt ist folgener Satz:
"Der Dateireplikationsdienst konnte die Replikation von \\server1.dom.local nach SERVER2 für c:\windows\sysvol\domain mit DNS-Namen \\server1.dom.local nicht aktivieren. Es wird ein neuer Versuch gestartet. "

Müsste
"SERVER2 für c:\windows\sysvol\domain mit DNS-Namen \\server1.dom.local"

nicht eigentlich so lauten:
"SERVER2 für c:\windows\sysvol\domain mit DNS-Namen \\server2.dom.local"
Bitte warten ..
Mitglied: farol50
11.02.2009 um 12:52 Uhr
Wenn du in obiges dcdiag listing reinschaust, siehst du das problem in Zeile 14 "RPC-Server nicht verfügbar"
Das sieht dann doch eher nach einem dns-problem aus. das kann namensauflösung oder netbios sein.
es kann auch ein netzwerkproblem(mal versuchen netdiag /debug) sein. mal die firewall ausgeschaltet?

Dann vielleicht mal direkt mit repadmin forschen.

Gruß
farol
Bitte warten ..
Mitglied: Nati1003
11.02.2009 um 13:08 Uhr
Erstmal Danke für die Antworten!

Also netdiag /debug sagt mir so garnichts... vielleicht euch ja mehr...

<code>

Gathering IPX configuration information.
Opening \Device\NwlnkIpx failed
Querying status of the Netcard drivers... Passed
Testing Domain membership... Passed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Team 1
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.5.4' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server '192.168.5.1' 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 an Active Directory DC
Gathering the list of Domain Controllers for domain 'dom'
DC list for domain dom:
server1.dom.local [DS] Site: Standardname-des-ersten-Standorts
server2.dom.local [PDC emulator] [DS] Site: Standardname-des-ersten-Standorts
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain dom ...
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: server2
DNS Host Name: server2.dom.local
DNS Domain Name: dom.local
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 23 Stepping 10, GenuineIntel
Hotfixes :
Installed? Name
Yes KB924667-v2
Yes KB925398_WMP64
Yes KB925902-v2
Yes KB926122
Yes KB927891
Yes KB929123
Yes KB930178
Yes KB932168
Yes KB933729
Yes KB933854
Yes KB935839
Yes KB935840
Yes KB936357
Yes KB936782
Yes KB938127
Yes KB938464
Yes KB941569
Yes KB943055
Yes KB943460
Yes KB943485
Yes KB944338-v2
Yes KB944653
Yes KB945553
Yes KB946026
Yes KB948496
Yes KB948745
Yes KB949014
Yes KB950762
Yes KB950974
Yes KB951066
Yes KB951698
Yes KB951746
Yes KB951748
Yes KB952069
Yes KB952954
Yes KB953838-IE7
Yes KB954211
Yes KB954600
Yes KB955069
Yes KB955839
Yes KB956390-IE7
Yes KB956391
Yes KB956802
Yes KB956803
Yes KB956841
Yes KB957097
Yes KB958215
Yes KB958644
Yes KB958687
Yes KB960714
Yes KB961260-IE7
Yes Q147222
No ServicePackUninstall


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

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: Parallelanschluss (direkt)
Device: \DEVICE\{FE38608E-B1AB-43FD-9280-500743D284C5}
GetStats failed for 'Parallelanschluss (direkt)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: WAN-Miniport (PPTP)
Device: \DEVICE\{EE276E98-E5D3-44B7-B209-8767ADD42B19}

Media State: Connected

Device State: Connected
Connect Time: 00:00:00
Media Speed: 0 bps

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-Miniport (PPTP)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: WAN-Miniport (PPPOE)
Device: \DEVICE\{65109662-A6DC-4992-ACF0-222B4E0C14D6}

Media State: Connected

Device State: Connected
Connect Time: 00:00:00
Media Speed: 0 bps

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-Miniport (PPPOE)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: WAN-Miniport (IP)
Device: \DEVICE\NDISWANIP

Media State: Connected

Device State: Connected
Connect Time: 01:19:52
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-Miniport (IP)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: WAN-Miniport (Netzwerkmonitor)
Device: \DEVICE\NDISWANBH

Media State: Connected

Device State: Connected
Connect Time: 01:19:52
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-Miniport (Netzwerkmonitor)' may not be working because it has not received any packets.
---------------------------------------------------------------------------
Description: WAN-Miniport (L2TP)
Device: \DEVICE\{EB8B84E4-6256-4E07-8048-0BC129724897}
GetStats failed for 'WAN-Miniport (L2TP)'. [ERROR_NOT_SUPPORTED]
---------------------------------------------------------------------------
Description: BASP Virtual Adapter
Device: \DEVICE\{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}

Media State: Connected

Device State: Connected
Connect Time: 01:19:53
Media Speed: 1 Gbps

Packets Sent: 110748
Bytes Sent (Optional): 31185906

Packets Received: 134028
Directed Pkts Recd (Optional): 119837
Bytes Received (Optional): 48550592
Directed Bytes Recd (Optional): 48550592

---------------------------------------------------------------------------
Description: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2
Device: \DEVICE\{85170DE1-196B-466D-B780-3F567767D8FC}

Media State: Connected

Device State: Connected
Connect Time: 01:19:56
Media Speed: 1 Gbps

Packets Sent: 81571
Bytes Sent (Optional): 26907389

Packets Received: 45423
Directed Pkts Recd (Optional): 38106
Bytes Received (Optional): 40268550
Directed Bytes Recd (Optional): 40268550

---------------------------------------------------------------------------
Description: Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client)
Device: \DEVICE\{E87367F5-6936-4534-B117-E066A4D939E3}

Media State: Connected

Device State: Connected
Connect Time: 01:19:56
Media Speed: 1 Gbps

Packets Sent: 29181
Bytes Sent (Optional): 4278517

Packets Received: 88605
Directed Pkts Recd (Optional): 81731
Bytes Received (Optional): 8282042
Directed Bytes Recd (Optional): 8282042

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



Per interface results:

Adapter : Team 1
Adapter ID . . . . . . . . : {D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : server2
Description. . . . . . . . : BASP Virtual Adapter
Physical Address . . . . . : 00-19-99-58-69-2D
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.5.4
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.5.254
Dns Servers. . . . . . . . : 192.168.5.4
192.168.5.1

IpConfig results . . . . . : Passed

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

Default gateway test . . . : Passed
Pinging gateway 192.168.5.254 - reachable
At least one gateway reachable for this adapter.

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}
server2 <00> UNIQUE REGISTERED
dom <00> GROUP REGISTERED
dom <1C> GROUP REGISTERED
server2 <20> UNIQUE REGISTERED
dom <1E> GROUP REGISTERED
dom <1B> UNIQUE REGISTERED
dom <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]
---------------------------------------------------------------
server1 <20> UNIQUE 192.168.5.1 370
dom <1C> GROUP 192.168.5.1 242
dom <1E> GROUP 192.168.5.1 225
server1.RTLAS<45> UNIQUE 192.168.5.1 472
T5000 <00> UNIQUE 192.168.5.22 15
T5000 <20> UNIQUE 192.168.5.22 370
L3050_5KW <20> UNIQUE 192.168.5.102 370
L5040 <20> UNIQUE 192.168.5.15 370


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. . . . . . . . . . . : Hybrid
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : dom
Dns domain name. . . . . . . . : dom.local
Dns forest name. . . . . . . . : dom.local
Domain Guid. . . . . . . . . . : {C1412520-ABDE-4B36-942E-3DD2205CCEB4}
Domain Sid . . . . . . . . . . : S-1-5-21-3500521571-1668920725-1622358806
Logon User . . . . . . . . . . : Administrator
Logon Domain . . . . . . . . . : dom


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}
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 . . . . . . . : Passed
PASS - you have at least one reachable 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 : 14
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_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}] SEQPACKET 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}] DATAGRAM 4
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E87367F5-6936-4534-B117-E066A4D939E3}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{E87367F5-6936-4534-B117-E066A4D939E3}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{85170DE1-196B-466D-B780-3F567767D8FC}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{85170DE1-196B-466D-B780-3F567767D8FC}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{90A21D73-4103-4A4B-A5E3-94B7B6E32A66}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{90A21D73-4103-4A4B-A5E3-94B7B6E32A66}] DATAGRAM 2
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{A5BA335F-273B-46D4-B9F1-97B12EBFA0D7}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{A5BA335F-273B-46D4-B9F1-97B12EBFA0D7}] DATAGRAM 3
Provider Version :2

Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
Interface {D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}
DNS Domain:
DNS Servers: 192.168.5.4 192.168.5.1
IP Address: Expected registration with PDN (primary DNS domain name):
Hostname: server2.dom.local.
Authoritative zone: dom.local.
Primary DNS server: server2.dom.local 192.168.5.4
Authoritative NS:192.168.5.1 192.168.5.4
Check the DNS registration for DCs entries on DNS server '192.168.5.4'

* * * * *
  • CHECK NAME _ldap._tcp.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.c1412520-abde-4b36-942e-3dd2205cceb4.domains._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.c1412520-abde-4b36-942e-3dd2205cceb4.domains._msdcs.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.c1412520-abde-4b36-942e-3dd2205cceb4.domains._msdcs.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME 3659fe78-d126-409a-b16b-2b997b80fc0f._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is correct on DNS server '192.168.5.4'.


* * * * *
  • CHECK NAME _kerberos._tcp.dc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kerberos._tcp.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 88 server2.dom.local
SRV 0 100 88 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 88 server2.dom.local
SRV 0 100 88 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.dc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._tcp.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kerberos._tcp.dom.local
DNS DATA =
SRV 0 100 88 server2.dom.local
SRV 0 100 88 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dom.local
DNS DATA =
SRV 0 100 88 server2.dom.local
SRV 0 100 88 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._udp.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kerberos._udp.dom.local
DNS DATA =
SRV 0 100 88 server2.dom.local
SRV 0 100 88 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kpasswd._tcp.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.dom.local.
DNS DATA =
SRV 0 100 464 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kpasswd._tcp.dom.local
DNS DATA =
SRV 0 100 464 server2.dom.local
SRV 0 100 464 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kpasswd._udp.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.dom.local.
DNS DATA =
SRV 0 100 464 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _kpasswd._udp.dom.local
DNS DATA =
SRV 0 100 464 server2.dom.local
SRV 0 100 464 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.DomainDnsZones.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.DomainDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.DomainDnsZones.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.DomainDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.DomainDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.ForestDnsZones.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.ForestDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.ForestDnsZones.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.ForestDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.ForestDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.pdc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is correct on DNS server '192.168.5.4'.


* * * * *
  • CHECK NAME _ldap._tcp.gc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.gc._msdcs.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.gc._msdcs.dom.local
DNS DATA =
SRV 0 100 3268 server2.dom.local
SRV 0 100 3268 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.dom.local
DNS DATA =
SRV 0 100 3268 server1.dom.local
SRV 0 100 3268 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _gc._tcp.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _gc._tcp.dom.local
DNS DATA =
SRV 0 100 3268 server1.dom.local
SRV 0 100 3268 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _gc._tcp.Standardname-des-ersten-Standorts._sites.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.Standardname-des-ersten-Standorts._sites.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.4 is:
DNS NAME = _gc._tcp.Standardname-des-ersten-Standorts._sites.dom.local
DNS DATA =
SRV 0 100 3268 server2.dom.local
SRV 0 100 3268 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME dom.local. on DNS server 192.168.5.4
* * * * *

The Record is correct on DNS server '192.168.5.4'.


* * * * *
  • CHECK NAME gc._msdcs.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.dom.local.
DNS DATA =
A 192.168.5.4

The record on DNS server 192.168.5.4 is:
DNS NAME = gc._msdcs.dom.local
DNS DATA =
A 192.168.5.4
A 192.168.5.1
+------------------------------------------------------+


* * * * *
  • CHECK NAME DomainDnsZones.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is different on DNS server '192.168.5.4'.
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.5.4', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.dom.local.
DNS DATA =
A 192.168.5.4

The record on DNS server 192.168.5.4 is:
DNS NAME = DomainDnsZones.dom.local
DNS DATA =
A 192.168.5.4
A 192.168.120.254
+------------------------------------------------------+


* * * * *
  • CHECK NAME ForestDnsZones.dom.local. on DNS server 192.168.5.4
* * * * *

The Record is correct on DNS server '192.168.5.4'.


Check DC DNS NAME FINAL RESULT
PASS - All the DNS entries for DC are registered on DNS server '192.168.5.4' and other DCs also have some of the names registered.
Check the DNS registration for DCs entries on DNS server '192.168.5.1'

* * * * *
  • CHECK NAME _ldap._tcp.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.c1412520-abde-4b36-942e-3dd2205cceb4.domains._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.c1412520-abde-4b36-942e-3dd2205cceb4.domains._msdcs.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.c1412520-abde-4b36-942e-3dd2205cceb4.domains._msdcs.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME 3659fe78-d126-409a-b16b-2b997b80fc0f._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is correct on DNS server '192.168.5.1'.


* * * * *
  • CHECK NAME _kerberos._tcp.dc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kerberos._tcp.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 88 server1.dom.local
SRV 0 100 88 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 88 server2.dom.local
SRV 0 100 88 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.dc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.dc._msdcs.dom.local
DNS DATA =
SRV 0 100 389 server2.dom.local
SRV 0 100 389 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._tcp.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kerberos._tcp.dom.local
DNS DATA =
SRV 0 100 88 server1.dom.local
SRV 0 100 88 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kerberos._tcp.Standardname-des-ersten-Standorts._sites.dom.local
DNS DATA =
SRV 0 100 88 server1.dom.local
SRV 0 100 88 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kerberos._udp.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.dom.local.
DNS DATA =
SRV 0 100 88 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kerberos._udp.dom.local
DNS DATA =
SRV 0 100 88 server1.dom.local
SRV 0 100 88 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kpasswd._tcp.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.dom.local.
DNS DATA =
SRV 0 100 464 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kpasswd._tcp.dom.local
DNS DATA =
SRV 0 100 464 server1.dom.local
SRV 0 100 464 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _kpasswd._udp.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.dom.local.
DNS DATA =
SRV 0 100 464 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _kpasswd._udp.dom.local
DNS DATA =
SRV 0 100 464 server1.dom.local
SRV 0 100 464 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.DomainDnsZones.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.DomainDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.DomainDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.DomainDnsZones.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.DomainDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.DomainDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.ForestDnsZones.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ForestDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.ForestDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.ForestDnsZones.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.ForestDnsZones.dom.local.
DNS DATA =
SRV 0 100 389 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.ForestDnsZones.dom.local
DNS DATA =
SRV 0 100 389 server1.dom.local
SRV 0 100 389 server2.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.pdc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is correct on DNS server '192.168.5.1'.


* * * * *
  • CHECK NAME _ldap._tcp.gc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.gc._msdcs.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.gc._msdcs.dom.local
DNS DATA =
SRV 0 100 3268 server2.dom.local
SRV 0 100 3268 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _ldap._tcp.Standardname-des-ersten-Standorts._sites.gc._msdcs.dom.local
DNS DATA =
SRV 0 100 3268 server2.dom.local
SRV 0 100 3268 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _gc._tcp.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _gc._tcp.dom.local
DNS DATA =
SRV 0 100 3268 server2.dom.local
SRV 0 100 3268 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME _gc._tcp.Standardname-des-ersten-Standorts._sites.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.Standardname-des-ersten-Standorts._sites.dom.local.
DNS DATA =
SRV 0 100 3268 server2.dom.local.

The record on DNS server 192.168.5.1 is:
DNS NAME = _gc._tcp.Standardname-des-ersten-Standorts._sites.dom.local
DNS DATA =
SRV 0 100 3268 server2.dom.local
SRV 0 100 3268 server1.dom.local
+------------------------------------------------------+


* * * * *
  • CHECK NAME dom.local. on DNS server 192.168.5.1
* * * * *

The Record is correct on DNS server '192.168.5.1'.


* * * * *
  • CHECK NAME gc._msdcs.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.dom.local.
DNS DATA =
A 192.168.5.4

The record on DNS server 192.168.5.1 is:
DNS NAME = gc._msdcs.dom.local
DNS DATA =
A 192.168.5.4
A 192.168.5.1
+------------------------------------------------------+


* * * * *
  • CHECK NAME DomainDnsZones.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is different on DNS server '192.168.5.1'.
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.5.1', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.dom.local.
DNS DATA =
A 192.168.5.4

The record on DNS server 192.168.5.1 is:
DNS NAME = DomainDnsZones.dom.local
DNS DATA =
A 192.168.5.4
A 192.168.120.254
+------------------------------------------------------+


* * * * *
  • CHECK NAME ForestDnsZones.dom.local. on DNS server 192.168.5.1
* * * * *

The Record is correct on DNS server '192.168.5.1'.


Check DC DNS NAME FINAL RESULT
PASS - All the DNS entries for DC are registered on DNS server '192.168.5.1' 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_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{D9DA8E8B-59F9-48F4-AAEE-E5E1A03BE80E}
The browser is bound to 1 NetBt transport.
Mailslot test for dom* passed.


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

Find DC in domain 'dom':
Found this DC in domain 'dom':
DC. . . . . . . . . . . : \\server1.dom.local
Address . . . . . . . . : \\192.168.5.1
Domain Guid . . . . . . : {C1412520-ABDE-4B36-942E-3DD2205CCEB4}
Domain Name . . . . . . : dom.local
Forest Name . . . . . . : dom.local
DC Site Name. . . . . . : Standardname-des-ersten-Standorts
Our Site Name . . . . . : Standardname-des-ersten-Standorts
Flags . . . . . . . . . : GC DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'dom':
Found this PDC emulator in domain 'dom':
DC. . . . . . . . . . . : \\server2.dom.local
Address . . . . . . . . : \\192.168.5.4
Domain Guid . . . . . . : {C1412520-ABDE-4B36-942E-3DD2205CCEB4}
Domain Name . . . . . . : dom.local
Forest Name . . . . . . : dom.local
DC Site Name. . . . . . : Standardname-des-ersten-Standorts
Our Site Name . . . . . : Standardname-des-ersten-Standorts
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find Active Directory DC in domain 'dom':
Found this Active Directory DC in domain 'dom':
DC. . . . . . . . . . . : \\server1.dom.local
Address . . . . . . . . : \\192.168.5.1
Domain Guid . . . . . . : {C1412520-ABDE-4B36-942E-3DD2205CCEB4}
Domain Name . . . . . . : dom.local
Forest Name . . . . . . : dom.local
DC Site Name. . . . . . : Standardname-des-ersten-Standorts
Our Site Name . . . . . : Standardname-des-ersten-Standorts
Flags . . . . . . . . . : GC DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8


DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'dom':
server1.dom.local
server2.dom.local


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed
Cached Tickets:


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

Do un-authenticated LDAP call to 'server1.dom.local'.
Found 1 entries:
Attr: currentTime
Val: 17 20090211120330.0Z
Attr: subschemaSubentry
Val: 66 CN=Aggregate,CN=Schema,CN=Configuration,DC=dom,DC=local
Attr: dsServiceName
Val: 130 CN=NTDS Settings,CN=server1,CN=Servers,CN=Standardname-des-ersten-Standorts,CN=Sites,CN=Configuration,DC=dom,DC=local
Attr: namingContexts
Val: 26 DC=dom,DC=local
Val: 43 CN=Configuration,DC=dom,DC=local
Val: 53 CN=Schema,CN=Configuration,DC=dom,DC=local
Val: 44 DC=DomainDnsZones,DC=dom,DC=local
Val: 44 DC=ForestDnsZones,DC=dom,DC=local
Attr: defaultNamingContext
Val: 26 DC=dom,DC=local
Attr: schemaNamingContext
Val: 53 CN=Schema,CN=Configuration,DC=dom,DC=local
Attr: configurationNamingContext
Val: 43 CN=Configu
Bitte warten ..
Mitglied: Nati1003
11.02.2009 um 13:11 Uhr
Hmm, glaube der kommt mit der länge meiner Antwort nicht ganz klar! Ich hoffe die Informationen reichen.

Die Firewalls sind auf beiden Servern ausgeschaltet!

Was kann ich denn mit dem Tool repadmin machen? Kenn das nicht!

Gruß Nati1003
Bitte warten ..
Mitglied: farol50
11.02.2009 um 13:27 Uhr
Repadmin ist das kommandozeilentool für die ad replikation
repadmin /? sagt dir alles

das log sieht ja soweit gut aus. wie sieht es denn mit den uhrzeiten auf beiden rechnern aus?
hast du an den servern mehrere netzwerkschnittstellen?. mir ist beim dns schon mal auf die füsse gefallen, dass eine 2. schnittstelle mit ner lokalen adresse da war.
als letztes würde ich den neuen server noch einmal komplett als dc rausschmeissen und dann neu in die domäne bringen

gruß
farol
Bitte warten ..
Mitglied: Nati1003
12.02.2009 um 10:39 Uhr
Hallo,

erst noch einmal Danke für die ganze Hilfe!
Hab das Problem jetzt gelöst!

Und zwar mit folgendem Tutorial: http://blog.dikmenoglu.de/PermaLink,guid,ded25564-f4a9-4a4f-a331-56f8bc ...

Es lag an einem Fehler in den NTFS-Junction Points auf dem alten Server!

Gruß Nati1003
Bitte warten ..
Mitglied: farol50
12.02.2009 um 10:41 Uhr
diese Seite ist eine wahre Fundgrube.

Gruß
farol
Bitte warten ..
Neuester Wissensbeitrag
Windows 10

Powershell 5 BSOD

(8)

Tipp von agowa338 zum Thema Windows 10 ...

Ähnliche Inhalte
Windows Server
gelöst Nach Ausfall FSMO-Rollen "Seize" nun fehler bei SYSVOL Replikation DFS-R (17)

Frage von CengizPirasa zum Thema Windows Server ...

Windows Server
gelöst Zusätzlichen Windows Server 2012R2 Domänencontroller hinzufügen (5)

Frage von Mar-west zum Thema Windows Server ...

Windows Server
gelöst BackupExec 2016 Fehler beim Backup von Windows 2016 (1)

Frage von Looser27 zum Thema Windows Server ...

Heiß diskutierte Inhalte
Microsoft
Ordner mit LW-Buchstaben versehen und benennen (21)

Frage von Xaero1982 zum Thema Microsoft ...

Netzwerkmanagement
gelöst Anregungen, kleiner Betrieb, IT-Umgebung (18)

Frage von Unwichtig zum Thema Netzwerkmanagement ...

Windows Update
Treiberinstallation durch Windows Update läßt sich nicht verhindern (17)

Frage von liquidbase zum Thema Windows Update ...