by onatam » Tue Aug 20, 2019 10:54 pm
As the title states, I cannot set WTWare to connect directly to our terminal server gateway, so I have to point them to a terminal server directly and then at login it will get load balanced to a server in the pool.
A quick overview of the environment:
We have 1 gateway
15 host servers (gateway not included)
I try to set the Pi's to connect to different hosts in the network to start the connection. The problem is they are always attaching to the terminal, so its takes up processes and causes issues. Is there a way to either have the Pi connect to the gateway to initiate the login, or at least have WTWare not bind to a server until login credentials are entered and then passed through?
As the title states, I cannot set WTWare to connect directly to our terminal server gateway, so I have to point them to a terminal server directly and then at login it will get load balanced to a server in the pool.
A quick overview of the environment:
We have 1 gateway
15 host servers (gateway not included)
I try to set the Pi's to connect to different hosts in the network to start the connection. The problem is they are always attaching to the terminal, so its takes up processes and causes issues. Is there a way to either have the Pi connect to the gateway to initiate the login, or at least have WTWare not bind to a server until login credentials are entered and then passed through?