Try using nslookup from the computer where net use x: \\forexample.com\C$
failed to see if it can resolve the fully qualified domain for the target
server and check that the IP addresses reported are correct. Also look in
Event Viewer for any pertinent clues and run the support tool netdiag on the
client computer trying to connect to \\forexample.com\C$ and on the server
it is trying to connect to. It will run a battery of network connectivity,
name resolution, and domain membership tests to see if everything is up to
snuff or not. Then run dcdiag on the Granite dc. If the problem server has
more than one network adapter, that can also cause problems with name
resolution if not configured correctly. One thing to check on computers with
multiple network adapters is that the adapter used for the internal lan is
at the top of the priority list in networking connections/advanced/advanced
settings. Sometimes a simple reboot can resolve networking problems on a
problem computer. --- Steve
http://support.microsoft.com/default...b;en-us;321708 -- netdiag
and how to install support tools.
"Davey Nauth" <Davey
(E-Mail Removed)> wrote in message
news:9E24BC34-406D-4748-B3DA-(E-Mail Removed)...
>I find there is no duplication of IP address or name in the network. What
> else I can find out?
>
> Davey
>
> "Steven L Umbach" wrote:
>
>> Check the dns zone for the domain to make sure that there are not
>> multiple
>> IP addresses for the problem server registered and use nslookup from the
>> backup server to see if it can resolve the name for granite server and
>> what
>> IP addresses it reports. --- Steve
>>
>>
>> "Nauth" <(E-Mail Removed)> wrote in message
>> news:60022DD7-8FDA-49FB-A7A9-(E-Mail Removed)...
>> >I have two domain controllers, three servers and a DMZ, The GRANITE DC
>> >server
>> > is the problem. Any server or itself cannot map a drive and give an
>> > error.
>> >
>> > The domain is forexample.com
>> >
>> > From any computer, I issue the following commands:
>> >
>> > C:\>ping forexample.com
>> >
>> > Pinging forexample.com [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: \\forexample.com\C$
>> > 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\C$
>> > The command completed successfully.
>> >
>> >
>> > C:\>dir x:
>> > Volume in drive X has no label.
>> > Volume Serial Number is A46A-40A4
>> >
>> > Directory of X:\
>> >
>> > 07/19/2003 11:15 AM <DIR> .
>> > 07/19/2003 11:15 AM <DIR> ..
>> > 07/10/2003 05:17 PM 0 New Text Document.txt
>> > 07/19/2003 11:17 AM <DIR> schuttsm
>> > 1 File(s) 0 bytes
>> > 3 Dir(s) 3,060,744,192 bytes free
>> >
>> > C:\>
>> >
>> > 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 have other server which is backup server, that cannot backup GRANITE
>> > DC
>> > server, because of DNS name problems!
>> >
>> > I would appreciate to have your help thanks.
>>
>>
>>