Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Insufficient Memory message when connect

Post Reply
BrentBergin
8
8
Posts: 13
Joined: 2005-07-01 16:30

Insufficient Memory message when connect

Post by BrentBergin »

Having just installed 1.0.9.6 on a windows XP machine, like I have done before many times, I get "Insufficient Memory to allocate network buffer" when I connect to this one. Anybody know what is going on? Is it a settings problem? I am using the DSM plugin, selecting AES 128 in the server. DSM is also selected in vncviewer. I have 7 other machines where this installation worked first time.
Brent 972-489-6807 bbergin@cisco.com
Brent Bergin at Cisco Optical Training
User avatar
supercoe
400
400
Posts: 1732
Joined: 2009-07-20 21:27
Location: Walker, MN
Contact:

Re: Insufficient Memory message when connect

Post by supercoe »

Does any of this information help? http://forum.ultravnc.info/viewtopic.php?t=26872

Seems like deleting the SecureVNC keys fixed it.
http://www.chunkvnc.com - ChunkVNC - Free PC Remote control with the Open Source UltraVNC wrapper InstantSupport!
BrentBergin
8
8
Posts: 13
Joined: 2005-07-01 16:30

Re: Insufficient Memory message when connect

Post by BrentBergin »

Thanks for reminding me, I did fix this by accident. When you remove the old VNC (1.0 in my case) the remove program leaves the directory in with one file, ultravnc.ini. If you install the new program over this .ini file, you get the problem I described. I deleted the whole directory, installed 1.96 and everything works fine. Apparently when the new program attempts to load parameters into the old .ini file things get mixed up.
Brent Bergin at Cisco Optical Training
Post Reply