Experiencing slowness after NT4 > 2K3 migration

Experiencing slowness after NT4 > 2K3 migration

Post by iva » Sat, 30 Apr 2005 00:28:44


Hey folks,

Last night I finished migrating one of my sites from having NT4 servers
to w2k3. This morning, users are complaining that logons are slow,
applications are slow etc. Here's a little background.

Original site setup.
3 NT4 servers, 2 member servers, 1 BDC

Over the last week, I wiped one of the servers (the BDC), did a fresh
install of w2k3 and added it to our new AD domain. I prepped a fresh
install of 2k3 in AD on the other server and last night I moved the
remaining data and printers to that server and shut off the NT4 member
server.

Today, our client support people have been able to resolve the speed
issues on an individual basis by renaming the user's profiles on their
XP workstations. Just for a hoot, I powered up the NT4 box and like
magic, things seemed better site-wide.

I've killed all but the default shares on the NT4 box, but we're still
seeing connections through IPC$ on that machine. Unfortunately, it's
not feasible for us to keep this server up indefinitely (nor should we
have to, I would think) and it's not feasible to go around manually
renaming all users profiles. This was a site of only 200 people - the
next one slated is 600.

My question basically is why would turning back on an NT4 member server
impact XP clients connecting to w2k3 servers? Deleting printers is
another thing that seems to help, but again, we have far too many
clients for this to be feasible.

Well, that's my sad tale. If anyone has any insight on this, I'd really
appreciate hearing it! If you need more info, by all means just let me
know.

Thanks!

-Ivan.
 
 
 

Experiencing slowness after NT4 > 2K3 migration

Post by Danny Sand » Sat, 30 Apr 2005 01:25:32

No where in your post did you mention DNS.
AD absolutely must have a DNS server to support the AD domain. If not you
will see long log in times, group policy wont' work, problems adding
computers to the domain, it causes all sorts of problems.
See:
Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://www.yqcomputer.com/ ;en-us;825036



Setting Up the Domain Name System for Active Directory

http://www.yqcomputer.com/ ;en-us;237675



How to configure DNS for Internet access in Windows Server 2003

http://www.yqcomputer.com/ ;en-us;323380





hth

DDS W 2k MVP MCSE

 
 
 

Experiencing slowness after NT4 > 2K3 migration

Post by iva » Sat, 30 Apr 2005 01:55:15

Hey Danny,

Thanks very much for the reply. As far as I'm aware, DNS for AD was one
of the first things that was tackled for this migration. We had some
consultants come in and preconfigure this for us, so presumably this
has been addressed. The sticking point, at least as far as I can see
it, is why having the old NT server turned on should make any
difference - all it was in the old setup was a file and print server.
If there's something specific for us to look for in DNS, let me know
and I'll see what I can find out.

Thanks!

-I.
 
 
 

Experiencing slowness after NT4 > 2K3 migration

Post by Danny Sand » Sat, 30 Apr 2005 02:16:32

in your first post you mentioned "long log in times" this is a DNS issue.
Especially if it is happening to all clients.

You can peruse the "old NT server" issue if you want, but save yourself some
time and check the DNS set up.


Don't assume they did it right.
How are your clients getting their DNS settings? Did they set up DHCP to
give out this info? If so is DHCP giving out the correct info?


Check to make sure your DNS server set up for the AD domain points to itself
for DNS (in the properties of TCP/IP) this will allow it to register the SRV
records your clients are looking for when they log on. If they can't find
them, it takes a long time to log on (sound familiar?)
See:
How to verify that SRV DNS records have been created for a domain controller

http://www.yqcomputer.com/ ;en-us;816587

Make sure your AD client point to the same DNS server set up for the AD
domain ONLY.
For internet access your AD DNS server should be set up to forward requests
(or use root hints) and list your ISP's DNS server as the forwarder.

This is the only place your ISP's DNS servers should be listed.

hth
DDS W 2k MVP MCSE
 
 
 

Experiencing slowness after NT4 > 2K3 migration

Post by R » Wed, 04 May 2005 03:31:16

The reason for slow logon time is the fact that users are still nt4
users and use bdc's to authenticate. If no bdc is available at the
site, they will find the nearest bdc to login.

R


issue.
yourself some
this
to
itself
the SRV
find
controller
AD
requests


one
some
this
see
server.
know
 
 
 

Experiencing slowness after NT4 > 2K3 migration

Post by Danny Sand » Wed, 04 May 2005 03:46:20

> The reason for slow logon time is the fact that users are still nt4


The original poster said the clients were XP.
See:

Slow log in times for XP clients on an AD domain. Sounds like DNS to me.

DDS
 
 
 

Experiencing slowness after NT4 > 2K3 migration

Post by iva » Thu, 12 May 2005 02:30:18

atest update:

The NT4 member server has been back on for about a week now. Today, I
ran NETSTAT -a 5 and dumped it to a text file for about an hour and a
half. Over that time, there were about a dozen workstations (and our
PDC) making sporadic, repeated connections to the server. For example:

TCP ottaf33:nbsession ncdec633565:2681 ESTABLISHED
TCP ottaf33:nbsession NCDEC641444:1322 ESTABLISHED
TCP ottaf33:2596 OTTAF4:nbsession ESTABLISHED

Does this make sense to anyone? I just can't see why these connections
are being made... old printers mapped incorrectly? persistent network
shares? As always, insight would be greatly appreciated.

Thanks!

-I.



Danny Sanders wrote:
server
me.
DHCP
to
register
can't
the
forwarder.
was