Why can everyone access my DC, but my DC cannot see anyone

[margie]

I have a DC that everyone accesses without a problem,
my problem is that I can "see" all the other computers
out there, but I cannot access them. I get a
network error. All the computers can access each other
and the DC. I wondered if it was DNS or a network
setting... Any suggestions?
Thanks

 

[Herb Martin]

I have a DC that everyone accesses without a problem,

my problem is that I can "see" all the other computers
out there, but I cannot access them. I get a
network error. All the computers can access each other
and the DC. I wondered if it was DNS or a network
setting... Any suggestions?

Suggestion: Be much more explicit in your problem report...

What do you mean by "I cannot access"? Access how?
From where to where? What happens? What doesn't
happen?

Have you tried using the IP address versus using the NAME
(since you suspect a DNS problem this is an especially important
step but also a good diagnostic when first working such problems.)

What network error?

 

[Kevin D. Goodknecht]

In

I have a DC that everyone accesses without a problem,
my problem is that I can "see" all the other computers
out there, but I cannot access them. I get a
network error. All the computers can access each other
and the DC. I wondered if it was DNS or a network
setting... Any suggestions?
Thanks

Just a wild guess, is your DC using its own address for DNS?
It should be using only its own private address for DNS, the same goes for
the clients they should only use the DC for DNS.

 

[Ace Fekay [MVP]]

In

In

Just a wild guess, is your DC using its own address for DNS?
It should be using only its own private address for DNS, the same
goes for the clients they should only use the DC for DNS.

I have a feeling he probably means network neighborhood.

If so, bet either NetBIOS is turned off, Zone Alarm or something to that
effect, or if trying to access XP pc's, doesn't have file sharing enabled,
or ICF, etc, could be any number of issues. With such little info, hard to
guess.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[margie]

Let me clarify...
All clients can access the DC no problem...
when the DC tries to access clients through network
neighborhood, it gets this error:

cannot access //client_name not accessible, network path
not found

 

[Guest]

What do you mean by "I cannot access"? Access how?
From where to where? What happens? What doesn't
happen?

In network neighborhood, I see all the clients, but when
I try to access one of them, I get the error:
cannot access //client_name not accessible, network path
not found

Have you tried using the IP address versus using the NAME

Yes. This does work, which is why I thought it was a DNS
problem.

 

[Herb Martin]

In network neighborhood, I see all the clients, but when
I try to access one of them, I get the error:
cannot access //client_name not accessible, network path
not found

Ok, that helps and please excuse that I am going to continue to
be picky -- usually getting an explicit diagnoses all but solves these
problems.

So, "access" means "by clicking on them in Net Neighborhood", right?

Yes. This does work, which is why I thought it was a DNS
problem.

That is quite possible but since Net Neighborhood uses NetBIOS names
primarily you are more likely to have a NetBIOS name problem.

Do you have multiple subnets? NetBIOS normally uses broadcasts locally,
and needs WINS server to work across routers (multiple subnets.)

 

[Ace Fekay [MVP]]

Have you tried accessing it this way:
\\clientname.domain.com\sharename
And if so, does this work?

If accessing it this way:
\\clientname\sharename and can't do it, but accessing it by:
\\IPaddress\sharename does work, then I would say that this is NOT a DNS
problem. This would imply a NetBIOS issue. This would also be indicative of
why it does not work in Network Neighborhood.

Are the clients you are trying to access on the same subnet or a different
subnet, such as a different or a remote location?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================



In

 

[Ace Fekay [MVP]]

In

Let me clarify...
All clients can access the DC no problem...
when the DC tries to access clients through network
neighborhood, it gets this error:

cannot access //client_name not accessible, network path
not found

Obviously this is a re-post. Did you see my new response in your previous
thread?
Also, while we're here:

What type of clients are they?
Are they on the same subnet?

If XP Pro, is file sharing enabled and ICF turned off?
Can you access them by:

\\ipaddress\sharename
or just
\\ipaddress ?

How about:
\\clientname.domainname.com\sharename
or
\\clientname.domainname.com
?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Michael Johnston [MSFT]]

At a command prompt, try pinging one of these machines by host name. Does this resolve? If not, try by FQDN. Does this resolve? If not, verify all the clients
and servers point at only the internal DNS. Verify that all machines have the correct primary DNS suffix and are properly registering in DNS. You will then want
to verify that the DNS server has the proper forward lookup zone and this zone allows dynamic updates. Lastly, verify that none of the machines involved have
a firewall enabled.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.