File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby RonnieM » 2017-05-03 10:21

Hi

We have three recently built Windows 2008 R2 servers in different locations, with uVNC v1.2.1.2 64 bit server installed as a service.

Everything seems to work well with the exception of transferring a file from a client to these servers, although ironically file transfer from the server to the client works perfectly well.

What happens is :
Source and destination directories selected.
File to "Send" selected.
Click on the "Send" button
Progress bar appears.
File Transfer Window disappears.
Main uVNC window unresponsive, but stays on screen.

Main uVNC window closed by user.
New uVNC session initiated.
A zero byte "!UCNPFT-" file is present in the destination directory.


This is making it impossible to transfer files to these servers, and is a major problem.

Can anyone suggest what the source of this problem might be, and any solution ?

Thanks,

Ronnie
RonnieM
 
Posts: 3
Joined: 2017-05-03 09:54

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby Rudi De Vos » 2017-05-05 15:37

Perhaps some fast check, you never know.
Check if destination folder is writable for the current desktop user.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5324
Joined: 2004-04-23 10:21

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby RonnieM » 2017-06-16 13:58

Rudi De Vos wrote:Perhaps some fast check, you never know.
Check if destination folder is writable for the current desktop user.

The servers are logged on to as Administrator in all cases, so this is not the problem.

In any event if it was a rights issue, the creation of a zero byte file in the destination directory, as reported, would not occur.

Are we any further forward in identifying or fixing this issue, which is plaguing us on these file servers, to the point that we are considering going back to an earlier version.
RonnieM
 
Posts: 3
Joined: 2017-05-03 09:54

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby Rudi De Vos » 2017-06-16 14:38

Pehaps related to this issue
viewtopic.php?f=71&t=32713

If possible try to test the latest 1215 winvnc.exe.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5324
Joined: 2004-04-23 10:21

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby ddbivens » 2017-06-18 20:03

Testing with 1.2.1.5 on both ends...
I can't be for certain but I think File Transfer may be broken. For two days, 2-3 time disconnecting and reconnecting each day, I have tried to transfer three files to my work PC, that have failed. The failure has been in one of two ways. One way is when the File Transfer window just closes. The VNCViewer window will not respond in any way. Most of the time I can't get it to minimize or close. If it minimized, it immediately reports "VNCViewer is not responding". I usually get this message twice. If I can't get it to minimize, I use my Show Desktop button. Usually I can't get VNCViewer to do anything when I click on the icon minimized on the taskbar. Usually in a few seconds, I get the VNCViewer is not responding message. I have not been able to get a successful file transfer. The other way is for the File Transfer window to freeze. I only noticed a couple of times, but the byte count was about 22240, and for a retry after reconnecting the count was 44440. I don't know if that is significant or not.
For some reason, when I reboot a remote PC using the Windows Update "Reboot (or Restart) Now" button, it seems to cause the viewer to lock up with "Not Responding" most every time. Even after the PC has completed rebooted (I connect with another Viewer session), the one reporting "Not Responding" never comes back. I use the "X" and Close button to close that viewer. On the rarest of occasions, I have had to taskkill (via a batch file) to close the VNCViewer.exe program.
On a positive note, I have got great connections at home to a home PC, at home to my work PCs and at work to work PCs. For the the initial screen, which normally does not draw on initial connection, I usually wait 1-3 seconds after the connection, then I click the screen refresh button, which usually does well redrawing the initial connection screen, and redrawing throughout a connection usually works well. I have been able to leave connections open for very long periods and I have had very few unexpected disconnects / reconnects. The connectivity and screen refresh (not counting the first screen) and general responsiveness has been the best it has been since about version 1.1.9.3.
Thanks for listening.
ddbivens
20
20
 
Posts: 35
Joined: 2015-12-26 14:53

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby sfhub » 2017-06-18 22:20

ddbivens wrote:The failure has been in one of two ways. One way is when the File Transfer window just closes. The VNCViewer window will not respond in any way. Most of the time I can't get it to minimize or close. If it minimized, it immediately reports "VNCViewer is not responding". I usually get this message twice. If I can't get it to minimize, I use my Show Desktop button. Usually I can't get VNCViewer to do anything when I click on the icon minimized on the taskbar. Usually in a few seconds, I get the VNCViewer is not responding message. I have not been able to get a successful file transfer. The other way is for the File Transfer window to freeze. I only noticed a couple of times, but the byte count was about 22240, and for a retry after reconnecting the count was 44440. I don't know if that is significant or not.

I can concur on transfer problems on slower VPN connections. On fast LAN the transfers work ok.

What I am currently doing is using the 1.2.1.2 vncviewer.exe with the server running 1.2.1.5 winvnc.exe. This combination works pretty well. I need the 1.2.1.5 server because it fixes the stuck/freeze/slow transfer problem when winvnc is running as a service.
sfhub
20
20
 
Posts: 44
Joined: 2010-05-02 19:59

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby ddbivens » 2017-06-20 10:54

I tried that combination and it works for me also. When I need to do file transfers, I launch the 1.2.1.2 viewer. When I just want to remote control, I launch the 1.2.1.5 viewer, where I seem to get a little better response and screen refresh. Thank you for the info.
ddbivens
20
20
 
Posts: 35
Joined: 2015-12-26 14:53

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby Chris » 2017-06-22 08:21

We have file transfer Issues too in V1.2.1.5, only on slow (Wan) connections.
Chris
8
8
 
Posts: 16
Joined: 2012-10-31 11:59

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby Rudi De Vos » 2017-06-23 20:33

I will take a look again.
Slow network and FT
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5324
Joined: 2004-04-23 10:21

Re: File Transfer problem with W2K8 R2 and v1.2.1.2 64 bit

Postby RonnieM » 2017-06-26 18:08

Rudi De Vos wrote:I will take a look again.
Slow network and FT

It might help to know that we are doing this over a Satellite broadband service.

Speed down to client (viewer) is 20Mbps
Speed up to server is 6Mbps
Latency on every request circa 800ms


Just to re-iterate . . . . .

File transfer from the server to the local client (viewer) works fine.

File transfer from the local client viewer to the server often fails with a zero byte file created in the destination directory.

Bizarrely, our work around is to remote control the remote server from a local machine, and then initiate a connection back out to another local machine, and that way we can pull in the file rather than "pushing it" !!

So it really is only one direction that is the problem for us.

. . . . . . And we have been doing this for many years quite happily with older versions of uVNC (eg. v1.0.1) on much slower satellite connections than we now have !!!

Any help on this would be much appreciated.

Thanks,

Ronnie
RonnieM
 
Posts: 3
Joined: 2017-05-03 09:54


Return to 1.2.1.x

Who is online

Users browsing this forum: Google [Bot], Kirck and 2 guests