Re: Slow to open shares

From: Josh Hatten (jdhatten_at_xsthe.net)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 09:13:10 -0500

Thanks for the reply Ron.

1. I thought DNS was supposed to replace WINS????

2. All my clients point to 2 of my domain controllers for DNS. Resolution
is snappy, it's just this browsing issue that drives me nuts (and my users).
The delay occurrs no matter how many files in the share. I like the
authentication idea as well, b/c it only happens on the first share. But
that poses two questions:
    a. Why is it happening after the share list is built?? Shouldnt I
authenticate before seeing the share list??
    b. Why wouldnt my domain authentication be passed over?

Also, this happens on all subnets.

Thanks again!

Josh

"Ron Stewart (MCSE: Messaging)" <rstewart@no.spam.syscom-consulting.com>
wrote in message news:e5u2bbQTEHA.3420@TK2MSFTNGP12.phx.gbl...
> Problem 1 sounds like it's a name resolution issue, especially since
> you've indicated some of your clients are not using WINS, which is kind
> of strange. The browse list relies heavily on broadcasts and NetBIOS
> name resolution, which presents problems in a routed network like yours.
> The way around this is to implement WINS and to ensure that EVERY SINGLE
> MACHINE THAT CAN BE A WINS CLIENT IS ONE. Otherwise you get the problems
> you're describing. WINS Proxy Agents might be a solution for subnets
> with clients that can't use WINS.
>
> Problem 2 is kind of strange. Authentication should be occurring when
> you first connect to the server. Nonetheless, the server will have to
> check local NTFS and share permissions when access to a specific share
> is requested. Odd that the delay only occurs the first time. I take it
> the delay occurs regardless of the number of files in the share? If so,
> it points to some form of authentication problem as the likely culprit.
> Hmmm... What's your DNS configuration like?
>
> Josh Hatten wrote:
>
> > We have been fighting this issue for some time. Hoping someone can help
> >
> >
> > We have a Windows network with 5 Windows (4 are 2000, 1 is 2003) domain
> > controllers. The network is comprised of 5 Class C subnets, all running
on
> > the same physical backbone. All the servers reside in subnet A. All
> > machines are members of the domain, and are configured for DNS servers
.4
> > and .19, which are two of my DC's. Also, I am running WINS on both
servers.
> >
> > Now, the problems:
> >
> > 1. When a user is not using WINS, they normally see a browse list in My
> > Network Places, that is incomplete. Normally, it contains 1 server, but
> > sometimes none.
> > 2. In situations where a users is trying to browse a server, there is a
> > significant delay. The delay happens when accessing the first share.
For
> > instance. I can click on my domain (in My Network places view) and that
> > returns a computer list, almost instantly. Next, I double click my
server,
> > which returns a share list, almost instantly. However, when I double
click
> > a share, I get about a 15 second delay before it returns the contents of
the
> > share. Once you have done this with one share, all other shares on the
> > machine return their contents almost instantly. This makes me think it
may
> > be an authentication issue, but I have had no trouble hunting it down.
> >
> >
> > I would like to fix the lag time when browsing resources on servers, as
well
> > as try to provide a consistent list of resources to browsers of the
network
> > neighborhood. It seems like you can sit down at any machine on my
network,
> > and each one has a different list of workstations and servers in the
browse
> > list. Also, I am unsure why non-WINS clients see different (or no)
servers
> > in their browse lists.
> >
> > Any help is greatly appreciated.
> >
> > Thank you,
> > Josh
> >
> >

Relevant Pages

  • Re: Computer Browsing Service - anyone want to contribute for a good conversation?
    ... Do you have all client machines and servers ... Browse lists are built and exchanged by the computer browser service. ... It doesn't matter which subnet your clients are in. ... The most common cause of master browser failures is multihomed ...
    (microsoft.public.windows.server.networking)
  • Re: Questions on putting up a new DNS server.
    ... > Root domain AD-zone info. ... There are no other servers or clients in the Root domain. ... own DNS servers -- integrate them into AD. ...
    (microsoft.public.win2000.dns)
  • Major Issues After NT4 --> 2003 Upgrade
    ... For some reason, the servers are joining the DNS domain name, instead of the ... Our NT4 domain we'll call "NBIOS" and the DNS domain name that we assigned ... finding that the clients started thinking they were joined to the DNS.com ...
    (microsoft.public.windows.server.migration)
  • Re: DCs to use their own DNS/Domain name, while clients use another
    ... > -All client/member servers configured to use DNS servers that host the ... members should be in that domain for DNS as well. ... Pretty silly since the domain clients are using the BIND set. ...
    (microsoft.public.win2000.dns)
  • Re: AD circuitous route to DNS
    ... I had not even enabled forwarders to the campus DNS for Internet ... The campus DNS administrator is simply forwarding back to my AD DNS ... server from his non-AD name servers after my clients look to his servers for ... clients only since we have our own subnet. ...
    (microsoft.public.windows.server.dns)