Can't access Computers fr Domain Controller

The Situation
1 I have a Active Directory (DC) Domain Controller [Server03/SP2] with 10 (jC) joined Computers [XPWin/SP2-3]

2 At the DC the jCs are all shown in the Domain on the Network and also within the Computer tab of (ADU&C) AD Users & Computers dialog.

3 All jC can access the shared directories in the DC and among themselves.

The Problem
1 From the DC, 3 of the jC CAN'T be accessed by clicking the NetWork, message a) \\jC1 is not accessible, b) you may have no permission to use this network resource c) currently no logon servers availiable to servie the logon request. LogOn Service are started for all these "problem" jCs.

2 Also from the DC, using ADU&C > Manage, a red cross is shown for Local Users and Group for eg jC1, message "Unable to access the computer \\jC1, the err is Access is denied.

3 Pinging from DC to these 3 Jc are fine.

4 All "working" and "problem" jC have similar Users and i really can't see any difference between them.


CRY FOR HELP
This had been my most sticky problem for a long while. I am exhausted to find the reason and the solution. PLEASE HELP.

 

I'd start by seeing if this is a NetBIOS issue. \\jC1 is a NetBIOS address.

So first, try \\JC1.domain.local replacing domain.local with your AD's local domain name. If that works, try:

• going into the TCP/IP settings for the active network connection on JC1
• Go into advanced and select the WINS tab
• Select "Enable NetBIOS over TCP/IP" in the NetBIOS setting

I'd also check that the JC1 computer has the 2003 AD server's IP address as its primary DNS server. If not you can get all sorts of strange behaviour.

After that I think you need to be looking at you firewall settings on the PC.

 

Still lost

Thanks again for your constant help; this is not the 1st time you help on this sticky problem.

Your suggestions:
1 Where do i "try \\JC1.domain.local replacing domain.local with your AD's local domain name "
2 Enabling NetBIOS over TCP/IP don't work; in some of working jC this is unabled.
3 The jC1 primary DNS server IP address was the ISP IP addresses, replacing them with the AD's IP address eg 192.168.111 results in being unable to access the web as expected. I then followed your earlier suggestion placed the ISP DNS address as forwarders within the Domain controller via its DNS management; but still unable to access the web.
4 No effect even if firewall setting is unenabled. In the working jC no effect whether it is abled or not.

Some funny findings:
1 In the troubled jC, login as a Domain User, user have limited rights to manage the devices.

Very puzzled!!!

 

More tinkering & bad news

As a follow up on this long time sticky problem, i did the following to tinker on
1 from jC1, jC1 was removed from the Domain DC0 and joined a workgroup.
2 In the AD User & Computer manager > Computer tab, jC1 was next deleted.
3 rename the jC1 to another bios name and restart both jC1 & DC0.
4 next try to join jC1 to DC0, after typing in a newly registered DC0\username and its password but it keeps failing to do so.

Hope the above will manifest whats the issue, your continued help much appreciated.

 

Were you able to access local shared directories while primary DNS was set to point at the AD's IP address? That is, did it fix the problem but introduce a different problem (loss of internet) or did you have both problems (failure to access shares AND loss of internet)?

 

Thanks mate
No i still cannot login to jC1 from DC ie the problem is not resolved & i have a new problem at the jC1 being unable to access the web.

One question: The address i assign to the DC is 192.168.1.111 & is not really the Domain address as the Domain is not registered in the web. How's that to do with all these?