If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Slow XP workstation response in a Win2K domain... HELP!
Hi,
I recently installed Windows 2K server onto our new Dell PowerEdge 2600 system. The installation appeared to go fine until I started adding workstations to my domain. Along with the new server I decided to upgrade many of our workstations to XP Professional so that we could take advantage of VPN and Remote Desktop connectivity. Now, nothing seems to work; or at least work fast!! When I join a computer to the domain the whole procedure works fine. I'm able to join, map network drives and access other domain workstations just fine. After a few hours, however, when I attempt to access other computers in the domain it takes a long period of time to connect. In fact, it appears as though my initial credentials aren't good anymore because it asks me for a username and password to access the domain machine. Does anyone know what's going on here? It's as though the domain controller loses each computers/users credentials. At this point I wonder wether Win2K Server is installed correctly. When I go to the domain controller and expand the system/Microsoft DNS folder I don't see entries for each of the computers in the domain (either in the "." folder or the "domain-name" folder). Is this the problem? If so, how do I fix it. I've tried dcDiag.exe and everything passes except that it complains that an error occurred during DNS host lookup. Maybe this is the problem. I would appreciate any help or suggestions from some of you experts on this. I've spent a bunch of time looking through Microsofts knowledge base and found good information. I've tried all the suggestions but to no avail. Please help!!!! (By the way I've attached the rest of the output from dcDiag in case there's some other useful information!) Thanks, Lou Piloco ************************* dcDiag log ********************** Performing initial setup: * Connecting to directory service on server svision. An error cocured during DNS host lookup * Collecting site info. * Identifying all servers. * Found 1 DC(s). Testing 1 of them. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\SVSERVER Starting test: Connectivity * Active Directory LDAP Services Check * Active Directory RPC Services Check ......................... SVSERVER passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\SVSERVER Starting test: Replications * Replications Check ......................... SVSERVER passed test Replications Test omitted by user request: Topology Test omitted by user request: CutoffServers Starting test: NCSecDesc * Security Permissions Check for CN=Schema,CN=Configuration,DC=svision * Security Permissions Check for CN=Configuration,DC=svision * Security Permissions Check for DC=svision ......................... SVSERVER passed test NCSecDesc Starting test: NetLogons * Network Logons Privileges Check ......................... SVSERVER passed test NetLogons Starting test: Advertising The DC SVSERVER is advertising itself as a DC and having a DS. The DC SVSERVER is advertising as an LDAP server The DC SVSERVER is advertising as having a writeable directory The DC SVSERVER is advertising as a Key Distribution Center The DC SVSERVER is advertising as a time server The DS SVSERVER is advertising as a GC. ......................... SVSERVER passed test Advertising Starting test: KnowsOfRoleHolders Role Schema Owner = CN=NTDS Settings,CN=SVSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi gurat n,DC=svision Role Domain Owner = CN=NTDS Settings,CN=SVSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi gurat n,DC=svision Role PDC Owner = CN=NTDS Settings,CN=SVSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi guration C=svision Role Rid Owner = CN=NTDS Settings,CN=SVSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi guration C=svision Role Infrastructure Update Owner = CN=NTDS Settings,CN=SVSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Site CN=Configuration,DC=svision ......................... SVSERVER passed test KnowsOfRoleHolders Starting test: RidManager * Available RID Pool for the Domain is 1602 to 1073741823 * svserver.svision is the RID Master * DsBind with RID Master was successful * rIDAllocationPool is 1102 to 1601 * rIDNextRID: 1160 * rIDPreviousAllocationPool is 1102 to 1601 ......................... SVSERVER passed test RidManager Starting test: MachineAccount * SPN found :LDAP/svserver.svision/svision * SPN found :LDAP/svserver.svision * SPN found :LDAP/SVSERVER * SPN found :LDAP/svserver.svision/SVISION * SPN found :LDAP/e104ff59-2bc8-458f-b420-0b6ab5596c15._msdcs.svision * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/e104ff59-2bc8-458f-b420-0b6ab5596c15/s vision * SPN found :HOST/svserver.svision/svision * SPN found :HOST/svserver.svision * SPN found :HOST/SVSERVER * SPN found :HOST/svserver.svision/SVISION * SPN found :GC/svserver.svision/svision ......................... SVSERVER passed test MachineAccount Starting test: Services * Checking Service: Dnscache * Checking Service: NtFrs * Checking Service: IsmServ * Checking Service: kdc * Checking Service: SamSs * Checking Service: LanmanServer * Checking Service: LanmanWorkstation * Checking Service: RpcSs * Checking Service: RPCLOCATOR * Checking Service: w32time * Checking Service: TrkWks * Checking Service: TrkSvr * Checking Service: NETLOGON ......................... SVSERVER passed test Services Test omitted by user request: OutboundSecureChannels Starting test: ObjectsReplicated SVSERVER is in domain DC=svision Checking for CN=SVSERVER,OU=Domain Controllers,DC=svision in domain DC=svision on 1 servers Object is up-to-date on all servers. Checking for CN=NTDS Settings,CN=SVSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi guration,DC= ision in domain CN=Configuration,DC=svision on 1 servers Object is up-to-date on all servers. ......................... SVSERVER passed test ObjectsReplicated Starting test: frssysvol * The File Replication Service Event log test The SYSVOL has been shared, and the AD is no longer prevented from starting by the File Replication Service. ......................... SVSERVER passed test frssysvol Starting test: kccevent * The KCC Event log test Found no KCC errors in Directory Service Event log in the last 15 minutes. ......................... SVSERVER passed test kccevent Starting test: systemlog * The System Event log test Found no errors in System Event log in the last 60 minutes. ......................... SVSERVER passed test systemlog Running enterprise tests on : svision Starting test: Intersite Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments provided. ......................... svision passed test Intersite Starting test: FsmoCheck GC Name: \\svserver.svision Locator Flags: 0xe00001fd PDC Name: \\svserver.svision Locator Flags: 0xe00001fd Time Server Name: \\svserver.svision Locator Flags: 0xe00001fd Preferred Time Server Name: \\svserver.svision Locator Flags: 0xe00001fd KDC Name: \\svserver.svision Locator Flags: 0xe00001fd ......................... svision passed test FsmoCheck and everything passes except Domain Controller Diagnosis |
Ads |
Thread Tools | |
Display Modes | |
|
|