This has nothing to do with DNS. The list in My Network Places comes
from the computer browser service, which is an NT legacy application and
uses Netbios names, not DNS names.
First off, make sure that Netbios over TCP/IP is enabled on the server.
Look under the WINS tab in the advanced TCP/IP settings of the NIC
properties.
Have you made any changes to the DC lately? Enabling remote access on a
DC can upset the browser service.
andreask wrote:
> thanks for the quick response,
> no again the clients that have problem to access them with
> \\fileserver i can not access them with fqdn as well. By the way our
> domain controller is windows 2000 server.
>
> "Spenceation" wrote:
>
>> Can you access the clients when you use the fqdn? Such as,
>> \\fileserver.domain.com
>> When you try \\fileserver you are using the NetBIOS name, which is
>> the reason that some are working and others are not. Unless WINS is
>> running, (which is unlikely due to 2003) you will only be able to
>> access computers within your broadcast domain.
>>
>> "andreask" wrote:
>>
>>> Hi everyone,
>>> This issue appeared in our primary domain controller server. When I
>>> try to open my network places clients are not shown (on domain
>>> Controller). However, some clients are accessible if I use a
>>> network path (eg. \\fileserver) but not all clients are accessible.
>>> I thought that the problem was due to incorrect DNS server. i
>>> checked it and I was correct. DNS Server was incorrect. I corrected
>>> DNS, restart Domain Controller but the problem is not resolved. Can
>>> anyone suggest anything to solve this problem?
|
Similar Threads
Linear Mode
