Configuration information could not be read from the domain controller

  • Thread starter Thread starter vineet
  • Start date Start date
V

vineet

hi

I have recently installed Windows Server 2003 as a domain controller.
It is the first (and only) DC in the forest. I'm logging into one of
my client computers (Windows XP Pro) and trying to map a drive to a
share on the domain controller. The client computer has successfully
joined the domain and I have logged into the domain.

The domain is affordable
From the client computer, I issue the following commands:
Click to expand...

C:\>ping affordable

Pinging affordable [192.168.0.200] with 32 bytes of data:

Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
C:\>net use x: \\affordable\common
System error 1351 has occurred.

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


C:\>net use x: \\192.168.0.200\common
The command completed successfully.



What is going on? Why can I map a network drive using the IP address,
but not the DNS name? Yes, DNS resolution is working (see the ping
command).

I am getting same msg in while I tries

\\affordable\netlogon

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


Plz help me to resolve the problem asap

Thanks
vineet
 
vineet said:
hi

I have recently installed Windows Server 2003 as a domain controller.
It is the first (and only) DC in the forest. I'm logging into one of
my client computers (Windows XP Pro) and trying to map a drive to a
share on the domain controller. The client computer has successfully
joined the domain and I have logged into the domain.

The domain is affordable
From the client computer, I issue the following commands:
Click to expand...

C:\>ping affordable

Pinging affordable [192.168.0.200] with 32 bytes of data:

Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
C:\>net use x: \\affordable\common
System error 1351 has occurred.

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


C:\>net use x: \\192.168.0.200\common
The command completed successfully.
Click to expand...

Are you usuing MULTIPLE NAMES for 192.168.0.200,
such as CNAMES?

That doesn't work -- by default.

Obviously you can resolve "affordable" to the IP, and
you can connect to a share by IP.

Search Microsoft site for details on the following keys:

HKLM\System\CurrenControlSet\Services\LanmanServer\Parameters

add String value "OptionalNames" the value must be your 2nd netbios

name (Alias)

HKLM\System\CurrenControlSet\Services\LanmanServer\Parameters

add Dword value "DisableStrictNameChecking" the value must be

REG_DWORD=1


Google:

[ OptionalNames DisableStrictNameChecking site:microsoft.com ]
What is going on? Why can I map a network drive using the IP address,
but not the DNS name? Yes, DNS resolution is working (see the ping
command).

I am getting same msg in while I tries

\\affordable\netlogon

Configuration information could not be read from the domain controller,
either
because the machine is unavailable, or access has been denied.
Click to expand...
 
No, ping doesn't prove that DNS is working; at least not the ping you used.
Try pinging the FQDN of the server and see what you get.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


vineet said:
hi

I have recently installed Windows Server 2003 as a domain controller.
It is the first (and only) DC in the forest. I'm logging into one of
my client computers (Windows XP Pro) and trying to map a drive to a
share on the domain controller. The client computer has successfully
joined the domain and I have logged into the domain.

The domain is affordable
From the client computer, I issue the following commands:
Click to expand...

C:\>ping affordable

Pinging affordable [192.168.0.200] with 32 bytes of data:

Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
C:\>net use x: \\affordable\common
System error 1351 has occurred.

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


C:\>net use x: \\192.168.0.200\common
The command completed successfully.



What is going on? Why can I map a network drive using the IP address,
but not the DNS name? Yes, DNS resolution is working (see the ping
command).

I am getting same msg in while I tries

\\affordable\netlogon

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


Plz help me to resolve the problem asap

Thanks
vineet
Click to expand...
 
C:\>ping affordable
Pinging affordable [192.168.0.200] with 32 bytes of data:

Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Click to expand...
Click to expand...

Richard G. Harper said:
No, ping doesn't prove that DNS is working; at least not the ping you
used. Try pinging the FQDN of the server and see what you get.
Click to expand...

While technically correct that this ping doesn't prove
DNS works, it does prove that the name resolves to
the (expected?) address 192.168.0.200.

In some ways it's more relevant to the next test which
fails:

But since this one works:

It seems likely that he is trying to use multiple names
for an SMB resource.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


vineet said:
hi

I have recently installed Windows Server 2003 as a domain controller.
It is the first (and only) DC in the forest. I'm logging into one of
my client computers (Windows XP Pro) and trying to map a drive to a
share on the domain controller. The client computer has successfully
joined the domain and I have logged into the domain.

The domain is affordable
From the client computer, I issue the following commands:
Click to expand...

C:\>ping affordable

Pinging affordable [192.168.0.200] with 32 bytes of data:

Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128
Reply from 192.168.0.200: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>
C:\>net use x: \\affordable\common
System error 1351 has occurred.

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


C:\>net use x: \\192.168.0.200\common
The command completed successfully.



What is going on? Why can I map a network drive using the IP address,
but not the DNS name? Yes, DNS resolution is working (see the ping
command).

I am getting same msg in while I tries

\\affordable\netlogon

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


Plz help me to resolve the problem asap

Thanks
vineet
Click to expand...
Click to expand...
 
Back
Top