Chirurgia endoscopică a hipofizei
"Standardul de aur" în chirurgia hipofizară îl reprezintă endoscopia transnazală transsfenoidală. Echipa NeuroHope este antrenată în unul din cele mai mari centre de chirurgie a hipofizei din Europa, Spitalul Foch din Paris, centrul în care a fost introdus pentru prima dată endoscopul în chirurgia transnazală a hipofizei, de către neurochirurgul francez Guiot. Pe lângă tumorile cu origine hipofizară, prin tehnicile endoscopice transnazale pot fi abordate numeroase alte patologii neurochirurgicale. www.neurohope.ro |
Probleme Domain Controller,AD Windows 2003 Server
Last Updated: Mar 12 2005 23:54, Started by
muntos
, Mar 04 2005 10:44
·
0
#1
Posted 04 March 2005 - 10:44
De dau 2 domain controllere (primary domain controller si aditional domain controller) ambele pe Windows 2003 Server.
Am urmatoarele probleme legate de AD si DC (sper ca nu si DNS) 1.ISA nu mai poate sa faca authentificarea la nivel de user.Internetul merge dar doar daca las regulile pt acces anonim. 2.Nu ma mai pot loga pe al 2-lea DC remote: The system cannot log you on due the following error. Access is denied 3.Imi apar o groaza de erori pe ambele DC-uri Pe Primary DC: SERVER: System Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40961 Date: 3/4/2005 Time: 7:25:52 AM User: N/A Computer: SERVER Description: The Security System could not establish a secured connection with the server . No authentication protocol was available. For more information, see Help and Support Center at Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40960 Date: 3/4/2005 Time: 7:25:52 AM User: N/A Computer: SERVER Description: The Security System detected an authentication error for the server . The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40961 Date: 3/4/2005 Time: 7:25:44 AM User: N/A Computer: SERVER Description: The Security System could not establish a secured connection with the server ldap/server.B18.local. No authentication protocol was available. For more information, see Help Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40960 Date: 3/4/2005 Time: 7:25:44 AM User: N/A Computer: SERVER Description: The Security System detected an authentication error for the server ldap/server.B18.local. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40961 Date: 3/4/2005 Time: 7:25:12 AM User: N/A Computer: SERVER Description: The Security System could not establish a secured connection with the server LDAP/Localhost. No authentication protocol was available Event Type: Warning Event Source: LSASRV Event Category: SPNEGO (Negotiator) Event ID: 40960 Date: 3/4/2005 Time: 7:25:12 AM User: N/A Computer: SERVER Description: The Security System detected an authentication error for the server LDAP/Localhost. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request. Directory Service Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1308 Date: 3/4/2005 Time: 7:29:37 AM User: NT AUTHORITY\ANONYMOUS LOGON Computer: SERVER Description: The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed. Attempts: 7 Domain controller: CN=NTDS Settings,CN=SERVER2,CN=Servers,CN=Default-First-Site,CN=Sites,CN=Configuration,DC=B18,DC=local Period of time (minutes): 383 The Connection object for this domain controller will be ignored, and a new temporary connection will be established to ensure that replication continues. Once replication with this domain controller resumes, the temporary connection will be removed. Additional Data Error value: 8524 The DSA operation is unable to proceed because of a DNS lookup failure. File Replication Service Event Type: Error Event Source: NtFrs Event Category: None Event ID: 13568 Date: 3/4/2005 Time: 7:26:30 AM User: N/A Computer: SERVER Description: The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Replica root path is : "d:\windows\sysvol\domain" Replica root volume is : "\\.\D:" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "\\.\D:" has been formatted. [2] The NTFS USN journal on volume "\\.\D:" has been deleted. [3] The NTFS USN journal on volume "\\.\D:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\D:". Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. To change this registry parameter, run regedit. Click on Start, Run and type regedit. Expand HKEY_LOCAL_MACHINE. Click down the key path: "System\CurrentControlSet\Services\NtFrs\Parameters" Double click on the value name "Enable Journal Wrap Automatic Restore" and update the value. If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above. Pe aditional DC: Managing the network session with server.B18.local failed "Logon Failure: The target account name is incorrect." Appplication Event Type: Error Event Source: Userenv Event Category: None Event ID: 1053 Date: 3/4/2005 Time: 8:11:49 AM User: NT AUTHORITY\SYSTEM Computer: SERVER2 Description: Windows cannot determine the user or computer name. (The target principal name is incorrect. ). Group Policy processing aborted. For more information, see Help and Support Center at http://go.microsoft....link/events.asp. Event Type: Error Event Source: Winlogon Event Category: None Event ID: 1219 Date: 3/4/2005 Time: 8:01:49 AM User: N/A Computer: SERVER2 Description: Logon rejected for B18\administrator. Unable to obtain Terminal Server User Configuration. Error: Access is denied. Event Type: Error Event Source: Userenv Event Category: None Event ID: 1054 Date: 3/4/2005 Time: 7:53:09 AM User: NT AUTHORITY\SYSTEM Computer: SERVER2 Description: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. System: Event Type: Error Event Source: Kerberos Event Category: None Event ID: 4 Date: 3/4/2005 Time: 8:13:51 AM User: N/A Computer: SERVER2 Description: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/server.b18.local. The target name used was ldap/server.B18.local/[email protected]. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (B18.LOCAL), and the client realm. Please contact your system administrator. For more information, see Help and Support Center at http://go.microsoft....link/events.asp. Event Type: Error Event Source: Kerberos Event Category: None Event ID: 4 Date: 3/4/2005 Time: 8:12:55 AM User: N/A Computer: SERVER2 Description: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/server.b18.local. The target name used was cifs/Server. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (B18.LOCAL), and the client realm. Please contact your system administrator. For more information, see Help and Support Center at http://go.microsoft....link/events.asp. Event Type: Error Event Source: W32Time Event Category: None Event ID: 29 Date: 3/4/2005 Time: 7:44:28 AM User: N/A Computer: SERVER2 Description: The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time. For more information, see Help and Support Center at http://go.microsoft....link/events.asp. File replication Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13508 Date: 3/4/2005 Time: 8:01:43 AM User: N/A Computer: SERVER2 Description: The File Replication Service is having trouble enabling replication from SERVER to SERVER2 for c:\windows\sysvol\domain using the DNS name server.B18.local. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name server.B18.local from this computer. [2] FRS is not running on server.B18.local. [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established. For more information, see Help and Support Center at http://go.microsoft....link/events.asp. Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13565 Date: 3/4/2005 Time: 7:59:33 AM User: N/A Computer: SERVER2 Description: File Replication Service is initializing the system volume with data from another domain controller. Computer SERVER2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL. To check for the SYSVOL share, at the command prompt, type: net share When File Replication Service completes the initialization process, the SYSVOL share will appear. The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers. Mesajele sunt cam criptice pentru mine.Am cautat pe microsoft.com dar nu am reusit sa gasesc nimic care sa ma ajute. Pe mine nu ma intereseaza neaparat sa rezolv problemele cu replicarea sau tot ce tine de al 2-lea DC,as vrea macar sa curat TOT ce face referinta la al 2-lea DC de pe primul DC (adica ca si cum n-ar exista decat un DC) si sper ca asta sa rezolve problema cu ISA. Pls HEEELLPPPP :worthy: !!! |
#2
Posted 04 March 2005 - 11:54
dcdiag si netdiag ce spun?
pare sa ai 2 probleme in configuratia ta: 1. file system 2. DNS Ai incercat sa fortezi stergerea DC-ului secundar? Asta poate ajuta: http://support.micro...kb;en-us;332199 Ma mai uit mai pe seara ... deocamdata sunt intr-o fuga continua ... |
#3
Posted 04 March 2005 - 18:49
Rezultatul la dcdiag:
Domain Controller Diagnosis Performing initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site\SERVER Starting test: Connectivity ......................... SERVER passed test Connectivity Testing server: Default-First-Site\SERVER2 Starting test: Connectivity ......................... SERVER2 passed test Connectivity Doing primary tests Testing server: Default-First-Site\SERVER Starting test: Replications ......................... SERVER passed test Replications Starting test: NCSecDesc ......................... SERVER passed test NCSecDesc Starting test: NetLogons ......................... SERVER passed test NetLogons Starting test: Advertising ......................... SERVER passed test Advertising Starting test: KnowsOfRoleHolders ......................... SERVER passed test KnowsOfRoleHolders Starting test: RidManager ......................... SERVER passed test RidManager Starting test: MachineAccount ......................... SERVER passed test MachineAccount Starting test: Services ......................... SERVER passed test Services Starting test: ObjectsReplicated Authoritative attribute dBCSPwd on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609729 timeLastOriginatingChange = 2005-03-03 05:00:34 VersionLastOriginatingChange = 9 Out-of-date attribute dBCSPwd on SERVER (writeable) usnLocalChange = 1606671 LastOriginatingDsa = SERVER usnOriginatingChange = 1606671 timeLastOriginatingChange = 2005-02-23 16:52:32 VersionLastOriginatingChange = 9 Authoritative attribute lastLogonTimestamp on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609745 timeLastOriginatingChange = 2005-03-03 05:02:01 VersionLastOriginatingChange = 2 Out-of-date attribute lastLogonTimestamp on SERVER (writeable) usnLocalChange = 1634361 LastOriginatingDsa = SERVER usnOriginatingChange = 1634361 timeLastOriginatingChange = 2005-02-25 00:01:25 VersionLastOriginatingChange = 2 Authoritative attribute lmPwdHistory on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609729 timeLastOriginatingChange = 2005-03-03 05:00:34 VersionLastOriginatingChange = 9 Out-of-date attribute lmPwdHistory on SERVER (writeable) usnLocalChange = 1606671 LastOriginatingDsa = SERVER usnOriginatingChange = 1606671 timeLastOriginatingChange = 2005-02-23 16:52:32 VersionLastOriginatingChange = 9 Authoritative attribute ntPwdHistory on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609729 timeLastOriginatingChange = 2005-03-03 05:00:34 VersionLastOriginatingChange = 9 Out-of-date attribute ntPwdHistory on SERVER (writeable) usnLocalChange = 1606671 LastOriginatingDsa = SERVER usnOriginatingChange = 1606671 timeLastOriginatingChange = 2005-02-23 16:52:32 VersionLastOriginatingChange = 9 Authoritative attribute pwdLastSet on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609729 timeLastOriginatingChange = 2005-03-03 05:00:34 VersionLastOriginatingChange = 9 Out-of-date attribute pwdLastSet on SERVER (writeable) usnLocalChange = 1606671 LastOriginatingDsa = SERVER usnOriginatingChange = 1606671 timeLastOriginatingChange = 2005-02-23 16:52:32 VersionLastOriginatingChange = 9 Authoritative attribute supplementalCredentials on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609730 timeLastOriginatingChange = 2005-03-03 05:00:34 VersionLastOriginatingChange = 8 Out-of-date attribute supplementalCredentials on SERVER (writeable) usnLocalChange = 1606672 LastOriginatingDsa = SERVER usnOriginatingChange = 1606672 timeLastOriginatingChange = 2005-02-23 16:52:32 VersionLastOriginatingChange = 8 Authoritative attribute unicodePwd on SERVER2 (writeable) usnLocalChange = 82009 LastOriginatingDsa = SERVER usnOriginatingChange = 1609729 timeLastOriginatingChange = 2005-03-03 05:00:34 VersionLastOriginatingChange = 9 Out-of-date attribute unicodePwd on SERVER (writeable) usnLocalChange = 1606671 LastOriginatingDsa = SERVER usnOriginatingChange = 1606671 timeLastOriginatingChange = 2005-02-23 16:52:32 VersionLastOriginatingChange = 9 ......................... SERVER failed test ObjectsReplicated Starting test: frssysvol ......................... SERVER passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... SERVER failed test frsevent Starting test: kccevent ......................... SERVER passed test kccevent Starting test: systemlog ......................... SERVER passed test systemlog Starting test: VerifyReferences ......................... SERVER passed test VerifyReferences Testing server: Default-First-Site\SERVER2 Starting test: Replications [Replications Check,SERVER2] A recent replication attempt failed: From SERVER to SERVER2 Naming Context: CN=Configuration,DC=B18,DC=local The replication generated an error (-2146893022): The target principal name is incorrect. The failure occurred at 2005-03-04 18:30:00. The last success occurred at 2005-03-04 17:59:59. 1 failures have occurred since the last success. [Replications Check,SERVER2] A recent replication attempt failed: From SERVER to SERVER2 Naming Context: DC=B18,DC=local The replication generated an error (-2146893022): The target principal name is incorrect. The failure occurred at 2005-03-04 18:44:03. The last success occurred at 2005-03-04 18:00:02. 163 failures have occurred since the last success. ......................... SERVER2 passed test Replications Starting test: NCSecDesc ......................... SERVER2 passed test NCSecDesc Starting test: NetLogons ......................... SERVER2 passed test NetLogons Starting test: Advertising Warning: DsGetDcName returned information for \\server.B18.local, when we were trying to reach SERVER2. Server is not responding or is not considered suitable. ......................... SERVER2 failed test Advertising Starting test: KnowsOfRoleHolders ......................... SERVER2 passed test KnowsOfRoleHolders Starting test: RidManager ......................... SERVER2 passed test RidManager Starting test: MachineAccount ......................... SERVER2 passed test MachineAccount Starting test: Services ......................... SERVER2 passed test Services Starting test: ObjectsReplicated ......................... SERVER2 passed test ObjectsReplicated Starting test: frssysvol ......................... SERVER2 passed test frssysvol Starting test: frsevent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... SERVER2 failed test frsevent Starting test: kccevent ......................... SERVER2 passed test kccevent Starting test: systemlog An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 17:56:27 Event String: The kerberos client received a An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 17:59:17 Event String: The kerberos client received a An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 18:00:11 Event String: The kerberos client received a An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 18:00:14 Event String: The kerberos client received a An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 18:00:47 Event String: The kerberos client received a An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 18:01:27 Event String: The kerberos client received a An Error Event occured. EventID: 0x40000004 Time Generated: 03/04/2005 18:15:01 Event String: The kerberos client received a ......................... SERVER2 failed test systemlog Starting test: VerifyReferences ......................... SERVER2 passed test VerifyReferences Running partition tests on : TAPI3Directory Starting test: CrossRefValidation ......................... TAPI3Directory passed test CrossRefValidation Starting test: CheckSDRefDom ......................... TAPI3Directory passed test CheckSDRefDom Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation ......................... DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Running partition tests on : B18 Starting test: CrossRefValidation ......................... B18 passed test CrossRefValidation Starting test: CheckSDRefDom ......................... B18 passed test CheckSDRefDom Running enterprise tests on : B18.local Starting test: Intersite ......................... B18.local passed test Intersite Starting test: FsmoCheck ......................... B18.local passed test FsmoCheck |
#4
Posted 04 March 2005 - 18:54
Rezultatele la netdiag pe SERVER (primary DC)
Computer Name: SERVER DNS Host Name: server.B18.local System info : Windows 2000 Server (Build 3790) Processor : x86 Family 6 Model 8 Stepping 6, GenuineIntel List of installed hotfixes : KB819696 KB823182 KB823353 KB823559 KB824105 KB824141 KB825119 KB828035 KB828741 KB830352 KB832894 KB833987 KB834707 KB835732 KB837001 KB839643 KB839645 KB840315 KB840374 KB840987 KB841356 KB841533 KB842933 KB867460 KB867801 KB870763 KB871250 KB873339 KB873376 KB885835 KB885836 KB890175 KB891711 Q147222 Q828026 Netcard queries test . . . . . . . : Passed Per interface results: Adapter : LAN Netcard queries test . . . : Passed Host Name. . . . . . . . . : server IP Address . . . . . . . . : 10.1.1.240 Subnet Mask. . . . . . . . : 255.255.255.0 Default Gateway. . . . . . : Dns Servers. . . . . . . . : 10.1.1.240 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. WINS service test. . . . . : Skipped There are no WINS servers configured for this interface. Adapter : Internet Netcard queries test . . . : Passed Host Name. . . . . . . . . : server IP Address . . . . . . . . : 195.7.6.248 Subnet Mask. . . . . . . . : 255.255.240.0 Default Gateway. . . . . . : 195.7.0.1 Dns Servers. . . . . . . . : 10.1.1.240 AutoConfiguration results. . . . . . : Passed Default gateway test . . . : Passed NetBT name test. . . . . . : Passed No 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_{1B407742-64FA-4B4E-B768-A8B2E45CC00A} 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 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 '10.1.1.240' 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_{1B407742-64FA-4B4E-B768-A8B2E45CC00A} The redir is bound to 1 NetBt transport. List of NetBt transports currently bound to the browser NetBT_Tcpip_{1B407742-64FA-4B4E-B768-A8B2E45CC00A} 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 |
#5
Posted 04 March 2005 - 19:46
Netdiag pe al 2-lea domain controller
Computer Name: SERVER2 DNS Host Name: server2.B18.local System info : Windows 2000 Server (Build 3790) Processor : x86 Family 6 Model 8 Stepping 6, GenuineIntel List of installed hotfixes : Q147222 Netcard queries test . . . . . . . : Passed Per interface results: Adapter : Local Area Connection Netcard queries test . . . : Passed Host Name. . . . . . . . . : server2 IP Address . . . . . . . . : 10.1.1.239 Subnet Mask. . . . . . . . : 255.255.255.0 Default Gateway. . . . . . : 10.1.1.240 Dns Servers. . . . . . . . : 10.1.1.240 AutoConfiguration results. . . . . . : Passed Default gateway test . . . : Passed NetBT name test. . . . . . : Passed [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing. WINS service test. . . . . : Skipped There are no WINS servers configured for this interface. Global results: 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. NetBT transports test. . . . . . . : Passed List of NetBt transports currently configured: NetBT_Tcpip_{3B7CA88B-0B15-4995-921F-2F6B4EFF8898} 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 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 '10.1.1.240' 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_{3B7CA88B-0B15-4995-921F-2F6B4EFF8898} The redir is bound to 1 NetBt transport. List of NetBt transports currently bound to the browser NetBT_Tcpip_{3B7CA88B-0B15-4995-921F-2F6B4EFF8898} The browser is bound to 1 NetBt transport. DC discovery test. . . . . . . . . : Passed DC list test . . . . . . . . . . . : Failed [WARNING] Cannot call DsBind to server.B18.local (10.1.1.240). [SEC_E_WRONG_PRINCIPAL] Trust relationship test. . . . . . : Passed [WARNING] Don't have access to test your domain sid for domain 'B18'. [Test skipped] Secure channel for domain 'B18' is to '\\server.B18.local'. Kerberos test. . . . . . . . . . . : Passed LDAP test. . . . . . . . . . . . . : Passed [WARNING] Failed to query SPN registration on DC 'server.B18.local'. 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 |
#7
Posted 12 March 2005 - 01:29
man, am uitat complet de postul asta ... acum am vazut raspunsurile ... :( sorry ..
daca tot rezolvasi, macar spune-ne si noua ce era de fapt si cum ai scapat ... poate mai ajuta pe vreunul! Thx! |
#8
Posted 12 March 2005 - 23:54
Pai nu pot sa zic ca le-am rezolvat mai degraba s-au rezolvat :) .
Eu doar am sters manual al 2-lea domain controller,am curatat si eu cum am putut mai bine iar problema cu ISA,nu stiu,pur si simplu de la un moment dat (cam 1 zi dupa operatiunea de mai sus ) s-a rezolvat si ea. |
Anunturi
▶ 0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users