Terminal Services

Very slow Connection Remoting into a Terminal Server.  It takes about 20 minutes for the profile to load.  This issue only started today.  

We recieved an error earlier
Winlogon 1219
Userenv 1053 and 1054

We added the registry key and no longer recieve that error, however it takes a long time to log on now.  Any help is appreciated.
Matthew GalianoCTOAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

KorbusCommented:
What registry key did you add?  
Try logging in with a local computer account, rather than a domain account.  If faster, I would troublshoot the winlogon errors you were getting.
0
Matthew GalianoCTOAuthor Commented:
I added
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
On the Edit menu, point to New, and then click DWORD Value.
In the New Value #1 box, type IgnoreRegUserConfigErrors, and then press ENTER.
Right-click IgnoreRegUserConfigErrors, and then click Modify.
In the Value data box, type 1 (one), click Decimal, and then click OK.

I can logon locally to the domain Terminal Services takes forever.  
0
KorbusCommented:
"I can logon locally to the domain Terminal Services takes forever."
I meant, try logon with a TS session(or locally), using TSERV\username (rather than DOMAIN\username).
This will help determine if the problem is domain authentication.

I suggest you change the ignore error reg setting back to 0, and see what userConfigErrors get logged.

Once a user is on, how does the system perform? Could it be disk issues? (RAID degraded, chkdsk, defrag, etc..)
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Matthew GalianoCTOAuthor Commented:
It logs in fine locally, right away.  I still see those errors.

Winlogon 1219
Userenv 1053 and 1054
0
Matthew GalianoCTOAuthor Commented:
I still get those errors when I login with the domain.
0
KorbusCommented:
ok, so when you log on with a local computer account(which does not authenticate with active directory), it's fast; but when trying to use the domain controller to authenticate, it's slow. (probably times-out, then uses cashed info)
So your Terminal Server is having trouble communicating with the domain controller.  Once logged on, can you ping the domain controller from the terminal server?  Can you ping it by netbios name? Can you ping by It's FQDN  (DCserver.domain.local)?



0
Matthew GalianoCTOAuthor Commented:
weird, when I ping the FQ of the DC it does to another IP like a 66.56.88.96, not even an internal IP scheme.

Ping dc1.hq.local
0
KorbusCommented:
Are you sure the DNS for your TS nic is pointing to your DC (which I assume is also your internal DNS)?
0
Matthew GalianoCTOAuthor Commented:
I flushed the DNS and now I can ping the DC.  It has the correct IP address.

However its still slow logging in.
0
KorbusCommented:
Can you access the shares on the DC, how about the SYSVOL share, from the TS? (you will need to login as domain admin for SYSVOL)

Shot in th dark: Have you tried rebooting the DC yet?
0
Matthew GalianoCTOAuthor Commented:
I rebooted the DC and now everything is slow logging in, anything over the VPN takes 5 - 20 minutes to login.  Logging in locally as administrator logs right in.
0
KorbusCommented:
Any errors showing up in the DC's sys and app logs?  It sounds like the DC is the problem box, not the terminal server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Matthew GalianoCTOAuthor Commented:
After all that, it was the router.  As soon as I swapped it out, everything was working.
0
KorbusCommented:
Glad you got it working TJ.  Thanks for the points, even though I didn't get it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.