Network Browsing Issue

[DNA]

This doesn't happen a lot, but from time to time it does occur. When my
customer is trying to merely browse his network everything appears to be
fine (i.e., he can see the network). However, when he tries to gain
access to another PC (which is shared correctly, etc.), sometimes he gets
this error:

\\Server is not accessable.

There are currently no logon servers available to service the logon
request.

Any ideas? I've tried just about everything I know to try.

Thanks SO MUCH for any/all help!

 

[Phillip Windell]

How is the DNS "plan" designed in the LAN?
Is WINS being used?

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

 

[DNA]

YES, they have the IP address of their router for internet access. Every
PC is setup that way. No WINS

 

[Phillip Windell]

That is not what I asked. How is the DNS plan designed for the LAN? Is it
an Active Directory Domain? What do the Client machines on the LAN use for
DNS?

 

[DNA]

The broadband router has an IP address of 128.1.10.5. This is the address
they all have keyed for their primary and secondary DNS entries. As far
as an Active Directory Domain, I'm not totally sure, but I don't think so.
They authenticate through a Domain controller. This is the only server on
the premises. I hope I'm feeding you the info you're needing.

 

[DNA]

My bad! It's a 2000 Server with all 2000 Pro users, so YES, it is an
Active Directory Domain.

 

[Phillip Windell]

Your DNS is configured wrong.

1. ALL Clients *must* use the Active Directory DNS Server (the DC) as their
*only* DNS. It should *not* be entered twice,...leave the Secondary DNS
entry Blank.

2. The DNS Service running on the DC must be configured to use the ISP's DNS
as a "Forwarder". You can get the ISP's DNS IP# by looking into the config
of the broadband router.

3. Forget using the broadband router for the DNS.

4. Even if you don't bother to configure the ISP's DNS as a Forwarder, the
Active Directory DNS should still work for internet resolution because it
should automatically fall back to using Root Hints without any action on
your part.

5. I recommend still running WINS as well. Run it on the same DC that the
DNS is running on. Configure the WINS IP# in the Clients as well.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp