Printing ok now, next important issue...

  • Thread starter Thread starter mauricedorris
  • Start date Start date
M

mauricedorris

the latest build has solved the printing issues. I only wish that the 275 build was an official upgrade that is triggered automatically. I think its the only way to get the universal printer to work consistently. I now have faith in 2x again.

My next problem that is most important is with the connections. I use 2x to have external clients connect to the server via the internet. If there is any sort of connection problem or loss of signal, the 2x client kicks you out really quickly.

If I were in the MS remote desktop windows, I think it gives me at least 60 seconds for the connection to automatically re-establish itself. When the connection is interrupted, it will sit there frozen for about 10 seconds, but then it will pick up where it left off.

Is it possible to configure the 2x client to be more tolerant of connection issues. This is mainly a problem because my users are running applications remotely across the internet. Because of this connection issue, I have to have certain users continue to use the remote desktop connection window.

Thanks for any advice.
 
Hi there,

The 2X Client tries to reconnect when ever the tcp/ip session gets lost similar to the MS TCS.

Nixu
 
I agree. The 2x client does try to connect. However, it closes all published applications while it tries to reconnect. the MS TSC window stays open and freezes. If the connection reestablishes, then the session continues.

with 2x, it is very quick to close the application. Is there anyway to increase the time that the 2x client will wait before closing the published applications?

thanks
 
:)

If the session is disconnected, there is no point in keeping the applications visible.

Nixu
 
nixu said:
:)

If the session is disconnected, there is no point in keeping the applications visible.

Nixu
Click to expand...

Nixu, thanks for your response. But you are not understanding my real problem. You are being too technical and not thinking about what the users sees.

Try this, open up the microsoft remote desktop windows to a terminal server and start any application. Then, physically remove the network cable from the computer. The remote desktop window will stay visible. Wait 20-30 seconds and plug the network cable back in. you will see that the session eventually picks up where it left off. Try this with the 2x published application and you are kicked out quickly.

I publish applications across the internet and would like for the 2x client to be more forgiving for bad network connections. I know that the network should not temporarily drop, but it does and it affects the users. I have no control over that and neither does the users.

Can the 2x client wait a little longer before disconnecting the session?
 
I could see how this would be tricky for 2X to design. There would have to be some client side programing that would have to give some visible feedback to the user, like the RDP client does(Fade), that tells them the connection has gone down. This is important so that the application vendor can show the user it is a bad connection vs. a their bad application. If it didn't show some sort of feedback, the user would just see the screen as unresponsive. 20-30 seconds of unresponsiveness is quite a while when trying to type things. I think it needs to be paired with some education by the user about how to reconnect to their session as well if they see a connection problem.
 
Yes, it could be tricky to design. I am just trying to point out a real world issue.

I had trained my user to simply wait. But waiting worn't work with the 2x client that i just installed.

So here is my situation

1. I want all users using the 2x client because of the look of application publishing. So I installed it everywhere.
2. I had major printing issues but build 275 seems to have made the printing more reliable (thanks 2x!)
3. our business is internet hosted applications, so we have to deal with the connection issue. We were at a somewhat acceptable level of tolerance with remote desktop, but I don't have that with 2x.
4. The IT departments for my customers are not helpful. The idea of remote applications is that we don't need anything from them. They will not care if our application works. If their users can browse the web then they say there is no problem. Web surfing is stateless and can tolerate the occasional network hiccup.
 
Hi, I just found this post and was wondering if a solution was found that allowed 2X to be more forgiving of faulty connections. We have a client that is experiencing this as well, his published applications randomly closing. It doesn't happen to everyone in the office, just one person primarily and then it happened twice to another user.

They have a relatively good internet connection and have never complained of "drops" before.

They are running build 829 (Version 8.0) and our 2X server is running build 727. Are there any tweaks we can make to the computers themselves, the router here or at the client site, or the server to prevent this from happening.
 
I recommend you to contact support and add a feature request.
The client is set up to detect network failure quicker thatn normal rdp this is by design but can be changed.
The more people who require it the more possibility it has to be added.
 
You must log in or register to reply here.
Back
Top