Very Slow Respond.

[sihfmis]

I am not sure where the origins of the problem begin, so I will strat with TS
since that is where it seems to be. I am running a single 2003 TS server
(standard edt), so to have a second server, in a 2003 Enterprise domain.
When the remote clients log into the TS server, the response is very slow
(sometimes 5 to 10 minutes). it causes latency issues with applications and
drive mapping. Any suggestions where I should start looking? I am at a loss.

 

[Hank Arnold (MVP)]

Re: Very Slow Respond.

sihfmis wrote:
> I am not sure where the origins of the problem begin, so I will strat with TS
> since that is where it seems to be. I am running a single 2003 TS server
> (standard edt), so to have a second server, in a 2003 Enterprise domain.
> When the remote clients log into the TS server, the response is very slow
> (sometimes 5 to 10 minutes). it causes latency issues with applications and
> drive mapping. Any suggestions where I should start looking? I am at a loss.

First thing to look at is the DNS settings on the client and the
server(s). They should point only to internal DNS servers. If you have
DNS servers from an ISP, put then in the Forwarders section of the DNS
server.

Second thing to look at is the size of the profiles, especially if you
use roaming profiles. The larger the profile, the longer it takes to
load (and more susceptible to corruption).

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

 

[sihfmis]

Re: Very Slow Respond.

Looking at both suggestions. Everything looks good. Any other suggestions
or ideas. Thanks.

"Hank Arnold (MVP)" wrote:

> sihfmis wrote:
> > I am not sure where the origins of the problem begin, so I will strat with TS
> > since that is where it seems to be. I am running a single 2003 TS server
> > (standard edt), so to have a second server, in a 2003 Enterprise domain.
> > When the remote clients log into the TS server, the response is very slow
> > (sometimes 5 to 10 minutes). it causes latency issues with applications and
> > drive mapping. Any suggestions where I should start looking? I am at a loss.
>
> First thing to look at is the DNS settings on the client and the
> server(s). They should point only to internal DNS servers. If you have
> DNS servers from an ISP, put then in the Forwarders section of the DNS
> server.
>
> Second thing to look at is the size of the profiles, especially if you
> use roaming profiles. The larger the profile, the longer it takes to
> load (and more susceptible to corruption).
>
> --
>
> Regards,
> Hank Arnold
> Microsoft MVP
> Windows Server - Directory Services
>