AD and client

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

I have about 45 windows 2000 pro computers. All client
connected to windows 2000 server AD. I notice that when
first time they connect it is slow. My question is what i
need to do to make faster. FYI, i have DHCP on the server
and on server scope i have 003( router),005(Name servers),
oo6(DNS Servers), 015( DNS domain name), 044 (WINS/NBNS
servers and 046 (WINS/NBT Node Type). Did i miss something
here?
 
-----Original Message-----
I have about 45 windows 2000 pro computers. All client
connected to windows 2000 server AD. I notice that when
first time they connect it is slow. My question is what i
need to do to make faster. FYI, i have DHCP on the server
and on server scope i have 003( router),005(Name servers),
oo6(DNS Servers), 015( DNS domain name), 044 (WINS/NBNS
servers and 046 (WINS/NBT Node Type). Did i miss something
here?



.
Tom,

I think that it is usually 001 ( Gateway ), 006 ( DNS
Server ), 015 ( DNS Domain Name ), 044 ( WINS/NBNS ) and
046 ( WINS/NBT ). I do not see the Gateway in your DHCP
Server Options. Also, what did you make 046? Should not
really affect your WIN2000 clients, though.

I assume that the information ( read: IP Addresses ) are
correct? Sorry, have to ask.

Also, are we talking about one Site? or multiple Sites?
Not that this necessarily has any affect, but do you have
a Global Catalog Server - that is available?

Look in your DNS MMC and make sure that all the entries
are there in the Forward Lookup Zone. You should have
four subfolders: _msdcs, _sites, _tcp and _udp. have you
als set up a Reverse Lookup Zone? You might consider it.

I would suggest that you install the Support Tools on all
of your WIN2000 Servers, which are located in two places:
on the WIN2000 Server CD in the Support | Tools folder or
on the WIN2000 Service Pack CD in the Support | Tools
folder.

Run netdiag /fix from the command prompt as this
will 'fix' a bunch of finor things ( usually ) and then
run both netdiag /v and dcdiag /v. You might want to
redirect the output to a text file.

It *might* also be that some application ( app, spyware,
virus, whatever ) is contributing to this.

Also, for your general information, take a look at the
following two MSKB Articles:

For WIN2000 Clients:
http://support.microsoft.com/default.aspx?scid=KB;en-
us;247811

For WINXP Clients:
http://support.microsoft.com/default.aspx?scid=kb;
[LN];314861

HTH,

Cary
 
Back
Top