Configuration information could not be read from the domain contro

[Elyo Ravuna]

The name of our domain controller is MyDC. The fully qualified name is
mydc.mycompany.com. I can ping both MyDC and mydc.mycompany.com.

I can access \\mydc.mycompany.com\AnyShare without any problem (using a
fully qualified name), however when I try to access \\MyDc\AnyShare (using
just the computer name), I get the following error message on some clients --
including on the domain controller itself:

""""
\\MyDc\AnyShare is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if you
have access permissions.

Configuration information could not be read from the domain controller,
either because the machine is unavailable, or access has been denied.
""""

The problem is not specific to the user, it is specific to the workstation.
I tried to find what is different between the workstation where it works and
the workstation where it fails. However the DNS and WINS settings are the
same, I haven't been able to find a relevant difference.

Please note that KB#839499 didn't help.

How can I solve this problem?

Best regards.
Elyo Ravuna

[Jeremy]

Have you been through the Security Options under Local Policies in the local
GPO of each computer? Generally when you use the FQDN it doesn't use
NetBIOS, but when you just use the computer name it uses NetBIOS. Do you
have a misconfigured DNS suffix on the non working computer? Either the
primary suffix or the connection specific suffix. Can you post the output
of IPconfig /all?
Tried removing it from the domain and re-adding it? (worth a shot)
Is there a physical difference between this workstation and another working
one? Do they have the same NIC and driver version? Is there a newer driver
for the malfunctioning workstation. If you have two identical workstatons,
one working and one not you could try swapping the hard disks between the
machines to rule out hardware...

Let me know how you go. If all else fails rebuild the dodgy workstation.
Problems like this are why people use SOEs. Spend 15 minutes
troubleshooting it and if you can't fix it, rebuild. Then if it still fails
it must be hardware or upstream.

Cheers,
Jeremy.

Post by Elyo Ravuna
The name of our domain controller is MyDC. The fully qualified name is
mydc.mycompany.com. I can ping both MyDC and mydc.mycompany.com.
I can access \\mydc.mycompany.com\AnyShare without any problem (using a
fully qualified name), however when I try to access \\MyDc\AnyShare (using
just the computer name), I get the following error message on some clients --
""""
\\MyDc\AnyShare is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if you
have access permissions.
Configuration information could not be read from the domain controller,
either because the machine is unavailable, or access has been denied.
""""
The problem is not specific to the user, it is specific to the
workstation.
I tried to find what is different between the workstation where it works and
the workstation where it fails. However the DNS and WINS settings are the
same, I haven't been able to find a relevant difference.
Please note that KB#839499 didn't help.
How can I solve this problem?
Best regards.
Elyo Ravuna