All Answers. Collapse -. Possible Fix. Terminal Server ; not accepting connections. Good Troubleshooting Step:. Back to Networks Forum. Start or search. Start New Discussion. Create a new discussion If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Track this discussion and email me when there are updates. Reset Post Submit Post. Yes the reboot did the trick, but the KD didnt say anything about reboot.
Where is the licensing server installed? Typically, it is on another server like a DC, but could be located on this server. Check to see that the licensing service is running. To continue this discussion, please ask a new question. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.
Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Folks, i'm trying to change the listening port on one of the Windows Terminal server but for some reason is not working.
Best Answer. Solved, it was that computer that i was trying to connect from. View this "Best Answer" in the replies below ». George Aug 1, at UTC. I found that due to imaging the machines, my virtual adapters needed to be re-made. I hope this helps! I found a lot of KB articles from Microsoft that hinted about NIC issues and as you said all servers exhibited the same errors. I think that the problem is in your switches. If you have managed switch you must disable Spanning Tree or Enable faststart for Cisco.
For reference Cisco. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Learn more. Windows Terminal Server not responding after reboots Ask Question. Asked 9 years, 6 months ago. Active 9 years, 6 months ago. Viewed 2k times. All terminal servers show the following errors in the event log after reboots however not all of them arent responding, most work fine post reboot Event ID - Error - Netlogon - This computer was not able to set up a secure session with a domain controller in domain DOMAIN due to the following: There are no logon servers available.
Thanks for any assistance! Improve this question. Why are you rebooting every night? Unfortunately this is out of my control, I believe it is due to the belief that the servers run out of resources after continued use. Forces all users to disconnect and have all resources opened each business day.
You can go into the Computer Management and set timeout limits so that all of the users accounts are logged off automatically after a set amount of time. But DanBig is right in asking "Why are you rebooting every night" You should fix whatever is wrong, instead. I realize that we shouldnt be rebooting every night. Unfortunately as I mentioned this is out of my control. I think its reasonable to expect an OS to be able to reboot nightly without running into these issues as well.
I think its reasonable to expect an OS to be able to go witout rebooting every night :. But as you said it's out of your controll. My feeling is just that you should avoid these things because in larger networks the reconnecting and reesablishing of all links can be more troublesome. Maybe you should have a word with the people who are in charge of this.
To get back to the Problem: It seems like a problem with your Domain Controller. Show 6 more comments. Active Oldest Votes. First thing I'd do is set the TS services to delayed start up, in case it's an OS or machine boot issue.
0コメント