I was testing the File Transfer feature and it works fine on smaller files. However, it seems to crash the server on the larger files I've tried. I tested with zip files ranging from >300kb to 2.5mb. Crash occurs on those files over 1mb.
Symptoms of crash.
1. File Transfer stalls
2. If you kill the Viewer and try to reconnect you cannot ( Thinks Viewer still connected to server, I think)
3. Restarting the server app or service will allow reconnection.
My Setup
XP in VM acting as support customer running as app or installed as service.
Repeater on FreeBSD8 installed from ports. - not certain what version, how to tell?
Viewer running on 7 lappy or XP desktop.
Does anyone have ideas where this issue may be?
I apologize if this issue has been noted before but I couldn't find it by searching this forum.
After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-05: Celebrating the 23th anniversary of the UltraVNC (26th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38130
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128
There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-05: Celebrating the 23th anniversary of the UltraVNC (26th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38130
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128
There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
File Transfer issue
Re: File Transfer issue
Nope, but I would try to simplify the test if at all possible.
Using the same ChunkVNC software, install the viewer AND the provided UltraVNC server on one "real" nonvirtual machine and the Chunk server on a second real machine.
See if you still have the file transfer problem.
Then gradually add back in the more unusual bits, starting with the VMWare imaged "customer". Then the BSD repeater.
It's usually not the repeater at issue, but who knows.
On a personal note, I cringe when someone writes "lappy". Luckily I haven't heard it spoken yet.
Using the same ChunkVNC software, install the viewer AND the provided UltraVNC server on one "real" nonvirtual machine and the Chunk server on a second real machine.
See if you still have the file transfer problem.
Then gradually add back in the more unusual bits, starting with the VMWare imaged "customer". Then the BSD repeater.
It's usually not the repeater at issue, but who knows.
On a personal note, I cringe when someone writes "lappy". Luckily I haven't heard it spoken yet.
Re: File Transfer issue
I forgot I did test from physical machine to physical machine.
Windows 7 "laptop"
(viewer) to my work XP desktop (server)
I guess that only leaves the repeater. I will try the supplied repeater and the Perl version I found around this forum somewheres.
Thanks for the help.
Windows 7 "laptop"
(viewer) to my work XP desktop (server)I guess that only leaves the repeater. I will try the supplied repeater and the Perl version I found around this forum somewheres.
Thanks for the help.
Re: File Transfer issue
The repeater was the issue. I switched to the Perl script version and File transfers are reliable now.
FYI repeater from FreeBSD ports = BAD.
FYI repeater from FreeBSD ports = BAD.
Re: File Transfer issue
It's at http://www.freebsd.org/cgi/cvsweb.cgi/p ... /repeater/
It appears to be maintained, but I can't tell how old the repeater version he's using is. 5 Years? Looks like the actual files are using 0.14.
Thanks for the warning.
It appears to be maintained, but I can't tell how old the repeater version he's using is. 5 Years? Looks like the actual files are using 0.14.
Thanks for the warning.