I was using the NoMachine 3.0 client and apparently it doesn't like the
new freenx's way of handling reconnects. I downgraded to 2.0 thanks to
archive.org and it works fine.
Eric H. wrote:
I connect the first time and don't seem to have any problems but if I
suspend the session and then reconnect it will frequently and randomly
timeout(I'm on a LAN so this isn't a possibility) causing me to have to
reconnect to the session and it happens all over again.
This only started happening when I upgraded to FC7 this past week.
Anyone else experiencing this or know of a solution?
I'm using the Windows NoMachine client if that helps.
Re: Terminal Server & reconnect from original client only Policy ... then the user1 will be asked wich session he want to ... So the system don't keeps an eye on it, of wich client the user comes. ... "allow only reconnection from original client"... the user if his session will be disconnected, could do a reconnect from ... (microsoft.public.windows.terminal_services)
Re: $100 reward for socket disconnection help ... > I'm running Java 1.4.1 as an applet on the client side, under Windows 98, ... > with a DSL connection through a Linksys Wireless-B Router. ... > disconnects at the same time my application does ("AOL Instant Messenger ... > still trying to reconnect, IM is always able to immediately reconnect, and ... (comp.lang.java.programmer)
Re: communication error when test fail over ... When the user closes the app adn then re-opens it, ... Doesn't that in a way show the need for teh client to reconnect?... How do I prove it is client app issue not sql cluster issue? ... (microsoft.public.sqlserver.clustering)
Re: 1041Autoreconnect failed to reconnect user to session because authentication failed ... What is the exact problem you are experiencing? ... Are you referring to system log entries like this: ... these entries typically occur when the original session has ended and therefore reconnect is not possible. ... (microsoft.public.windows.terminal_services)
