Probleme mit einem Anmeldeserver der nicht vorhanden ist.

18/05/2009 - 17:05 von Jürgen Heidel | Report spam
Hallo,

ich habe mein Kunden folgendes Problem:
Der Anmelde vorgang dauert mehrere Minuten bis alle Laufwerke eingebunden
sind.

Die Infrastruktur sieht wie folgt aus:
2 Anmelde Server und als Storage Netapp Filer die im Cluster laufen.

Meiner Meinung nach liegt es an der Adresse .151 aber ich weis nicht wo
diese her kommt?


Habe folgende protokolle erstellt:
Filer:

-

srv02n> cifs domaininfo
NetBios Domain: Domaine-Name
Windows 2000 Domain Name: kunde.de
Type: Windows 2000
Filer AD Site: standardname-des-ersten-standorts

Current Connected DCs: \\SRV101
Total DC addresses found: 3
Preferred Addresses:
192.168.40.101 PDC
Favored Addresses:
192.168.40.150 SRV-AD-01 PDC
Other Addresses:
192.168.40.151 BDC

Connected AD LDAP Server: \\srv101.kunde.de
Preferred Addresses:
192.168.40.101
srv101.kunde.de
Favored Addresses:
192.168.40.150
srv-ad-01.kunde.de
Other Addresses:
None


srv02n> cifs testdc
Using Established configuration
Current Mode of NBT is H Mode

Netbios scope ""
Registered names...
SRV02 < 0> WINS Broadcast
SRV02 < 3> WINS Broadcast
SRV02 <20> WINS Broadcast
SHDOM < 0> WINS Broadcast

Testing all Primary Domain Controllers
found 2 unique addresses

found PDC SRV-AD-01 at 192.168.40.150
found PDC SRV101 at 192.168.40.101

Testing all Domain Controllers
found 3 unique addresses

found DC SRV-AD-01 at 192.168.40.150
found DC SRV101 at 192.168.40.101
Not able to communicate with DC 192.168.40.151
trying 192.168.40.151...ping: wrote 192.168.40.151 64 chars, error=Host is
down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
ping: wrote 192.168.40.151 64 chars, error=Host is down
no answer from 192.168.40.151
srv02n>

Windows:

-

C:\WINXP\system32>dcdiag /n:domain-name
The domain name is kunde.de.
The distinguished name of the domain is DC=kunde,DC=de.

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Standardname-des-ersten-Standorts\SRV101
Starting test: Connectivity
. SRV101 passed test Connectivity

Doing primary tests

Testing server: Standardname-des-ersten-Standorts\SRV101
Starting test: Replications
. SRV101 passed test Replications
Starting test: NCSecDesc
. SRV101 passed test NCSecDesc
Starting test: NetLogons
. SRV101 passed test NetLogons
Starting test: Advertising
. SRV101 passed test Advertising
Starting test: KnowsOfRoleHolders
. SRV101 passed test KnowsOfRoleHolders
Starting test: RidManager
. SRV101 passed test RidManager
Starting test: MachineAccount
. SRV101 passed test MachineAccount
Starting test: Services
. SRV101 passed test Services
Starting test: ObjectsReplicated
. SRV101 passed test ObjectsReplicated
Starting test: frssysvol
. SRV101 passed test frssysvol
Starting test: frsevent
. SRV101 passed test frsevent
Starting test: kccevent
. SRV101 passed test kccevent
Starting test: systemlog
. SRV101 passed test systemlog
Starting test: VerifyReferences
. SRV101 passed test VerifyReferences

Running partition tests on : kunde
Starting test: CrossRefValidation
. kunde passed test CrossRefValidati
on
Starting test: CheckSDRefDom
. kunde passed test CheckSDRefDom

Running enterprise tests on : kunde.de
Starting test: Intersite
. kunde.de passed test Intersite
Starting test: FsmoCheck
. kunde.de passed test FsmoCheck

Vielen Dank

Gruß
Jürgen
 

Lesen sie die antworten

#1 Winfried Sonntag [MVP]
19/05/2009 - 09:14 | Warnen spam
Jürgen Heidel schrieb:

ich habe mein Kunden folgendes Problem:
Der Anmelde vorgang dauert mehrere Minuten bis alle Laufwerke eingebunden
sind.



Nur zur Info für die Mitlesenden:
http://www.mcseboard.de/windows-for...51768.html

Servus
Winfried
Connect2WSUS: http://www.grurili.de/tools/Connect2WSUS.exe
GPO's: http://www.gruppenrichtlinien.de
Gruppenrichtlinien Mailingliste "gpupdate":
http://frickelsoft.net/cms/index.ph...ilingliste

Ähnliche fragen