Jump to content

Recommended Posts

Posted
We're currently trialling AB Tutor v6 on our 2003 terminal servers - it works great until you put a policy on anyone. Once a policy has been put on (and taken off) the server hosting the user loses its domain controller connection and refuses to allow any more connections until rebooted. The sessions already on are fine. Has anyone else had any experience of this? :confused: (The policies are not the internet block policies that say they affect the whole server)
Posted
Paul, are you still experiencing the problems since you've applied the most recent update? One of my terminal servers has recently started disallowing users access to the internet but RDP connections and access to fileshares continue to work. We get the erorr in the event logs that no domain controllers can be contacted. I can't ping the terminal server, but the terminal server can ping other devices. The only policy I had applied to the TS was (all) System Logging.
Posted
So far 6.1.1 seems to have fixed it. The symptoms we were getting were that existing sessions carried on but any new attempts got a 'domain does not exist'. The server could be pinged and it could happily ping others. It appeared as if some ports/sockets got blocked. Usually a reboot fixed it, if it din't a deinstall and reinstall of the AB client worked.
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...