loading user profile takes too long

  • Thread starter Thread starter Saygin
  • Start date Start date
S

Saygin

Hello,

I have a quick question regarding active directory. I
recently setup active directory running on Windows2000
server. Unfortunately, whenever a user tries to logon to
server his/her profile takes too much time to load. Any
suggestion to fix this problem would be very appreciated.
Thank you

O.Saygin
 
Good morning!

I would take a look at DNS first. You need to make sure that the clients
( assuming WIN2000 Pro or WINXP Pro ) TCP/IP configuration is correct (
meaning that in the DNS part it is pointing to your internal DNS Server and
NOT to the ISP's!!!!! ). That is client side.

I would also take a look on the Server and make sure that everything is okay
with DNS there. Do you have the four subfolders in the FLZ ( the _msdcs,
_sites, _tcp and _udp )? Is it set to at least 'yes' on Allow Dynamic
Updates?

Just some basics: can you reach the Server via ping and IP Address? via
NetBIOS Name? via DNS Name? What does nslookup yourdomain.com give you?

I would ass/u/me that DHCP is in play here? Is it WIN2000 DHCP or is your
Firewall handling this? Either way, is DHCP giving out the other
information with the IP Address lease ( default gateway, DNS Server(s),
domain name, etc. )? Make sure that this is correct there....

HTH,

Cary
 
Cary said:
Good morning!

I would take a look at DNS first. You need to make sure that the clients
( assuming WIN2000 Pro or WINXP Pro ) TCP/IP configuration is correct (
meaning that in the DNS part it is pointing to your internal DNS Server and
NOT to the ISP's!!!!! ). That is client side.
Click to expand...
(...)
Or maybe look on the user profiles size - are this roaming profiles?
From Your post I presume that users don't have a problem withh logging
but their profiles are being loading for long time. So if all DNS
related things (described in Cary post) are Ok chec profiles size and
consider using folder redirection functionality for speeding up user
profile loading process.
 
Excellent suggestion. Guess that I need to cover everything...or hope that
someone catches it. Thank you for adding this, Tomasz!

Cary
 
It's not just profile byte size that can slow down
roaming profile loading either. The number of files can
make a big difference. I redirect users cookie folder to
their home folder for this reason. Small files but (often)
lots of them. And of course temp internet files should
never be part of a roaming profile.

Mark.
 
Well folks, I would truly think about what Cary offers as advice, we
should probably stick to the responses from the actual MCSE's and not
the people who look through these posts and crack a book to answer
questions. Checking up on this guy, there is no MCSE he's just a lonely
guy with a computer and a few books. So judge his responses
accordingly.
Cary said:
*Good morning!

I would take a look at DNS first. You need to make sure that the
clients
( assuming WIN2000 Pro or WINXP Pro ) TCP/IP configuration is correct
(
meaning that in the DNS part it is pointing to your internal DNS
Server and
NOT to the ISP's!!!!! ). That is client side.

I would also take a look on the Server and make sure that everything
is okay
with DNS there. Do you have the four subfolders in the FLZ ( the
_msdcs,
_sites, _tcp and _udp )? Is it set to at least 'yes' on Allow
Dynamic
Updates?

Just some basics: can you reach the Server via ping and IP Address?
via
NetBIOS Name? via DNS Name? What does nslookup yourdomain.com give
you?

I would XXX/u/me that DHCP is in play here? Is it WIN2000 DHCP or is
your
Firewall handling this? Either way, is DHCP giving out the other
information with the IP Address lease ( default gateway, DNS
Server(s),
domain name, etc. )? Make sure that this is correct there....

HTH,

Cary
Click to expand...


Peter
 
Sorry that you feel this way, Peter!

Was I not able to help you with a question that you posted? I am very
happily married ( not that this is any of your concern ) with a full time
job in the IT Field ( not that I need to defend myself ).

Cary
 
Cary gives good advice. Not only on this occasion.

Slow logins can definitely be caused by DSN problems. That's from my
own experience. In fact many, many, AD problems can be traced back to
DNS. That's from my own experience.

I'd be interested to know the size of the profiles. In one case I came
across the guy had a 1.2GB file in his "My Documents" folder!

Cheers,

Cliff
 
Thank you, Enkidu.

Cary

Enkidu said:
Cary gives good advice. Not only on this occasion.

Slow logins can definitely be caused by DSN problems. That's from my
own experience. In fact many, many, AD problems can be traced back to
DNS. That's from my own experience.

I'd be interested to know the size of the profiles. In one case I came
across the guy had a 1.2GB file in his "My Documents" folder!

Cheers,

Cliff
Click to expand...
 
Back
Top