No mouse or KB input in Windows 7 x64

[drindianajones]

I have about 20 Windows 7 x64 boxes that all manifest this issue: I can connect to the box, but no mouse or KB input.
I do have dual LCDs on these machines, but I've tried this fix:
[post=67485][/post]
to no avail.

I've checked the hookdll and the mirror driver. I've added and removed the mirror driver. I've uninstalled, and reinstalled the whole program. I've tried removing wallpaper and disabling Aero. I've tried enabling Capture Alpha-blending and disabling it.

I'm fresh out of ideas...let me give you an exact rundown of the config.

Two 22" LCDs, with most users running the left screen as the default.
Windows 7 x64
UAC is enabled, but prompts are disabled for administrators...and these users are all local administrators.
Firewall is off for internal connections.
All hardware is identical, so I figure if we fix one we fix them all.

I've tried connecting from other boxes, XP, Vista & 7 (32/64)...same issue....so its not the connecting PC.

Any thoughts or suggestions?

[B]

It's a "no mouse or KB" problem but the one thing you DIDN'T specify was the mouse or keyboard in use. Perhaps try alternative devices and drivers?

Unlikely, I suppose...

Tried issuing Ctrl-Alt-Del? Tried reverse connections? Tried different versions?

[drindianajones]

Generic Dell-branded KBs & mice. I can't try PS/2, as the PC doesn't have 'em...so the default Windows 7 x64 drivers are in use...nothing special is loaded.

I've tried issuing both the CAD and Win key from the bar, no joy.

Tried 1.0.6.x...same problem.

Reverse connections?

[redge]

did you try cleanup the folder %temp%
did you try to clean default.vnc
did you try to direct connect to remote without template.vnc

[B]

redge is the expert here, so go with his advice first.

To answer your question, reverse connections are very typical and easy with VNC, but for some crazy reason I wasn't able to Google up a simple explanation for you.

You just run your vncviewer first in "listen" mode (I launch from the command line with vncviewer.exe -listen") and then, at the WinVNC server end, you right-click the VNC icon in the system tray, choose "Add client", and enter the name or IP address of the waiting viewer.

Just something else to test, but listen to redge first.

[redge]

drindianajones

do you really update your winvnc with the build of december 12 ?
check about the winvnc where is really ultravnc is installed.

sometime, users and myself include believe their have update but not.
double check your winvnc of december 7 is really the fix of 12 december

check there no duplicate of ultravnc.ini search including hidden and system folders.

[redge]

redge is the expert here,

no at all, i'm just experienced user.

the only expert are the developers of the software who know everything about software and can modify/solve/find bug and solve everything like Rudi De Vos, pgmoney, krunge, scovel, adzm, and some more like marscha (mslogon), lizard, who left

[drindianajones]

redge, thanks for the suggestions. I'm going to give it a shot when I get a chance...been crazy busy these last couple of days and I haven't had a chance to deal with this like I had hoped. I'll let you know how it goes.