Joseph Bishay
2014-10-28 16:05:19 UTC
Good day,
I hope everyone is doing well.
I would like to set up my thin clients so that they will run rdesktop on
another shell. I am able to successfully use lts.conf to run the rdesktop
application on another shell, but the computer doesn't actually connect to
the server. It activates a graphical interface and I get a mouse cursor I
can move around. It shows up in the logs also as working so I believe the
issue is that the thin client can't reach the Windows server.
My set up is:
thin client -> switch -> LTSP server NIC 1 ?? LTSP server NIC 2 ->
switch -> Windows Server.
I put question marks between the LTSP server NIC 1 and NIC 2 because I
can't ping the windows server from the thin client root shell BUT I can
successfully RDP from the thin client if I log into the server as a regular
user.
So I feel the issue is the server is stopping the connection. Is that the
case? And how can I allow it through? The remote desktop port is 3389
Thank you
Joseph
I hope everyone is doing well.
I would like to set up my thin clients so that they will run rdesktop on
another shell. I am able to successfully use lts.conf to run the rdesktop
application on another shell, but the computer doesn't actually connect to
the server. It activates a graphical interface and I get a mouse cursor I
can move around. It shows up in the logs also as working so I believe the
issue is that the thin client can't reach the Windows server.
My set up is:
thin client -> switch -> LTSP server NIC 1 ?? LTSP server NIC 2 ->
switch -> Windows Server.
I put question marks between the LTSP server NIC 1 and NIC 2 because I
can't ping the windows server from the thin client root shell BUT I can
successfully RDP from the thin client if I log into the server as a regular
user.
So I feel the issue is the server is stopping the connection. Is that the
case? And how can I allow it through? The remote desktop port is 3389
Thank you
Joseph