Hi forum mates Situation 1 An Active Directory (AD) has numerous Registered Users to the Domain (DM) using msServer 03 SP2. 2 Numerous wsPC running XPWin SP2 joined the Domain and appears as PCs in the AD User / Computer dialog at the Server. 3 The Server have static address eg 192.168.1.11 while all other wsPCs have similar static address ie 192.168.1.xxx 4 Pinging with the TCP/IP address among all the PCs and server in both in/out has no problems at all. Issue After some weeks without any undue events, DM's Administrator or any DM's Registered User, logged in at the Server, suddenly failed to access 2 particular wsPCs. The error message is: \\1-Pc is not accessible. U might not have permission to use this network resource. Contact Admin of this server if u have access rights. There are currently no logon servers availiable to serve this logon request. Note: 1 All wsPCs in the Domain appears in the network on the Server. 2 Any other users login at the various wsPCs within the Domain, can access each other including the 2 problem wsPCs eg \\1-PC. 3 DM Registered User, login at Server, are able login to other non problem wsPCs showed on the Server. Thanks in Advance. Mountain turtle

review the event viewer logs on these workstations for errors as well as confirming all basic networking services are started and running. Example of Oxymoron: Person who is pro life and anti sex education. Education is key to prevention. Prevent conception you prevent abortion. Abstinence training clearly isn't working.

Thanks wanderer 1 I have a look a system event log on the problem wkstation when i try to login to it from server, there is not error message log. When i login from another wkstn, login ok and again no error message. 2 I am not sure which service to look at, they all seem to working fine when i did the above loginS. Can you please give me more hints. Thanks again. Mountain turtle

compare the services running on a working machine to a nonworking machine. review all three event logs not just system. You should see security events related to remote logon failure... if you are getting that far into the system. confirm rdp is working. see if you can mmc remote desktop to it from the server. Example of Oxymoron: Person who is pro life and anti sex education. Education is key to prevention. Prevent conception you prevent abortion. Abstinence training clearly isn't working.

Thanks Wanderer 1 The errors in the event log are in the Application and System (none in Internet & Security) The Errors as follows: (Information excluded) APPLICATION Type Date Time Source Category Event User Computer Error 05-12-08 1:40:32 PM Userenv None 1053 SYSTEM DESK-PC Error 05-12-08 1:38:57 PM AutoEnrollment None 15 N/A DESK-PC Error 05-12-08 1:37:42 PM Userenv None 1054 SYSTEM DESK-PC Warning 05-12-08 1:36:21 PM Userenv None 1517 SYSTEM DESK-PC SYSTEM Error 05-12-08 2:22:57 PM W32Time None 29 N/A DESK-PC Warning 05-12-08 2:22:57 PM W32Time None 14 N/A DESK-PC Error 05-12-08 1:52:57 PM W32Time None 29 N/A DESK-PC Warning 05-12-08 1:52:57 PM W32Time None 14 N/A DESK-PC Warning 05-12-08 1:40:33 PM LsaSrv SPNEGO (Negotiator) 40961 N/A DESK-PC Warning 05-12-08 1:40:33 PM LsaSrv SPNEGO (Negotiator) 40960 N/A DESK-PC Warning 05-12-08 1:39:07 PM Print None 3 SYSTEM DESK-PC Warning 05-12-08 1:38:54 PM LsaSrv SPNEGO (Negotiator) 40961 N/A DESK-PC Warning 05-12-08 1:38:54 PM LsaSrv SPNEGO (Negotiator) 40960 N/A DESK-PC Warning 05-12-08 1:38:19 PM LsaSrv SPNEGO (Negotiator) 40961 N/A DESK-PC Warning 05-12-08 1:38:19 PM LsaSrv SPNEGO (Negotiator) 40960 N/A DESK-PC Error 05-12-08 1:37:46 PM W32Time None 29 N/A DESK-PC Warning 05-12-08 1:37:46 PM W32Time None 14 N/A DESK-PC Error 05-12-08 1:37:31 PM W32Time None 29 N/A DESK-PC Warning 05-12-08 1:37:31 PM W32Time None 14 N/A DESK-PC Error 05-12-08 1:37:27 PM Netlogon None 5719 N/A DESK-PC 2 Remote access from Server to problem wsPc working fine. 3 Yet to compare services with working wsPC. Any views based on the above symptoms, wandering doc!! Mountain turtle

Hi Wanderer I suspect that the System NetLogon evt error is the culprit but still tinkering. Meanwhile for yr info, details of the error is No Domain Controller is available for domain CJH-DM due to the following: There are currently no logon servers available to service the logon request. . Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator. Regards Mountain turtle