RDP clents getting disconnected from RDP server Constantly

We have users on a T1 Point to point tunneling WHo keep getting disconnected from the RDP server.
The RDP server is a server2008 R2 server.

I started looking at he event logs on the RDP server and found 2 error that keep comming up when the users are getting disconnected.

I attached a screenshot of the errors we are receiving.

I did some research on them and so far all I found was that one of the users has  a bad printer driver.
RDPevent.PNG
BBraytonAsked:
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.

unrealized92Commented:
Can you expand the license issue? you might not be licensed with enough CAL's.
0
BBraytonAuthor Commented:
They do have enough CAL's
it's not just one person that gets disconnected. its all the users in the office that get disconnected.
0
BBraytonAuthor Commented:
I just found an article for a fix!
Let me know what you think?

Hi,
1. Logon to your 2008 R2 DC as an administrator
2. Start--Run--adsiedit.msc
3. In the left pane, navigate to where the OU for your users is located
4. In the left pane, right-click on CN=<Your OU> and choose Properties
5. On the Security tab, click the Advanced button
6. Click the Add button, type Terminal Server License Servers and click OK
7. On the Properties tab, select Descendant User objects in the Apply onto box
8. In the Permissions box, select Allow for all of the following:
Read msTSExpireDate
Write msTSExpireDate
Read msTSLicenseVersion
Write msTSLicenseVersion
Read msTSManagingLS
Write msTSManagingLS
9. Click OK, and click OK again to save your changes
Please test by having a standard user logon to your RDS.  After the user has logged on, check the event logs of the server, there should not be a event id 4105 Warning for the user in the System log, and there should be a event id 4143 Information entry for the user under Microsoft-Windows-TerminalServices-Licensing/Admin log.
Thanks.
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

unrealized92Commented:
Yes! I was looking at that article as well, give it a shot, let me know if it improves anything :)

Are all of the users disconnecting at the same time? It could be a networking issue as well.
0
BBraytonAuthor Commented:
Terminal Server License Servers is already there in Advanced security permissions tab for one of the users. But the Permissions are not there. I will add the read/Write permissions and see what happens
0
davorinCommented:
Only users over VPN (one or multiple remote sites?) gets disconnected or also users who try to connect on the same site have the same problem? It could be that you have internet/VPN connectivity problems...
(Hope I have understood your problem correctly)
0
BBraytonAuthor Commented:
One site. Their routers are setup VPN Tunneling.
0
davorinCommented:
If it is just one remote site, I would say that is not terminal server problem, but connectivity problem. If other remote sites have no problem, then I would say it is problematic VPN connection or internet connection at that remote site.
0
BBraytonAuthor Commented:
OK thanks!!
0
BBraytonAuthor Commented:
Ended up calling Microsoft support and we ended up turning off IPV6 on all the clients and the terminal server. The problem has not came back since. its been over 1 month.
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
BBraytonAuthor Commented:
Ended up calling Microsoft support and we ended up turning off IPV6 on all the clients and the terminal server. The problem has not came back since. its been over 1 month.
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
Remote Access

From novice to tech pro — start learning today.