WriteExact Error

[sabotage]

Hi all,
I've got a problem with the new 1.05 version of UltraVNC.
A PC of mine at home is a server behind a router who forwards the port 5900 TCP.
MSRC4Plugin-122 enabled.
I can connect on loopback, and with another client installed on another PC in the LAN.
From outside WAN, after negotiation, when i type my password in after accepted, it gives me this error:
WriteExact: Socket error while writing.
I tried the client on a Vista PC and a windows 2000 too both with the same error. I don't know how to proceed.
HELP ME!
Who closes the connection, the server or the client?

[jksmurf]

I also get EAXCTLY that error above, after putting in the password. "writeexact: socket error while writing"

Not sure how to troubleshoot?

k.

[Rudi De Vos]

General network error, can't send (writeexact) data to other site.
-Check firewalls

[redge]

not only firewall but the winvnc ... (I had windows firewall disabled on my Vista sp1 english)
update with this fix,
http://sc.uvnc.com/105/specialbuild/opt ... invnc2.zip


I don't understand why is fixed my issue over WLAN with no change settings of home network and computer,
but the essential, is work a lot of better (except keyboard unresponsive fews seconds (buffer) (no file transfer, no dsmplugin,


----- edit config test: ----------
local: WLAN 54Mbit/s 802.11g local quick option = lan, auto-scaling
remote: LAN 100 Mbit/s , capture alpha-blending enabled, no mirror drv, no dsmplugin.

vncviewer 1.0.5 built 30.08.2008 vista business sp1 french
winvnc 1.0.5 built 1.09.2008 vista business sp1 english (firewall disabled)
------------------

please, be cool for others users, come back with feedback.

[Rudi De Vos]

I also don't understand, the only thing changed is the %TEMP% path
used for making setting changes.
Same compiler, same compiler options....

[Carlundd]

Have had the same issue with VistaSp2 as server.

One thing I've found out is, if you lock the PC as you would when you leave it, and then try to connect , you get the WriteExact: Socket error. If you leave it unlocked it seems to connect fine?

[brehone]

Have had the same issue with VistaSp2 as server.

One thing I've found out is, if you lock the PC as you would when you leave it, and then try to connect , you get the WriteExact: Socket error. If you leave it unlocked it seems to connect fine?

I am running into the same issue...if the office system is locked, it will return this error. Does anyone have a way around this? I am running on Windows 2008 64 bit and have installed the patch from above (Sept 1st build) with the same result. Thanks! Brian