Headless Secondary Monitor in XP
Posted 08 May 2007 - 10:32 PM
Posted 09 May 2007 - 08:28 AM
Posted 09 May 2007 - 08:35 AM
VNC will simply act as if its one huge desktop, so you have to madly scroll from one end to the other.
RemotelyAnywhere sees it as 2 independent monitors, at will, (you can swap between the both), or make it act as if its a big one, just like VNC.
As for the actual issue at hand, maybe someone else has a tip for it.
Posted 09 May 2007 - 08:44 AM
Posted 09 May 2007 - 10:43 AM
I have been working with the OP on this issue. It's a tough one!
RealVNC is connecting just fine, but will not display anything larger than 1920x1200. We've tried scaling to 3840x1200 on the VNC viewer, and all that does is stretch the current one-monitor resolution. OP has her two 24" monitors here, so she has a local resolution of 3840x1200. Windows display properties settings won't allow us to extend the server's desktop onto a 2nd monitor without any monitors plugged into it. After hitting "apply", the settings take for about 2 seconds, but then revert back to a greyed out 2nd monitor.
Windows Remote Desktop has a setting that will do what we're looking for. It will set your host's resolution to match your local resolution. I believe that particular function is called "server side scaling." The problem with Windows Remote Desktop is that it either moves at a crawl or freezes up when dealing with any applications that are even slightly CPU intensive. RealVNC is able to handle them perfectly. We've tried adjusting color and quality settings to see if the speed difference between WRD and VNC was related to that, and it wasn't. WRD is definitely too slow to handle the applications we're running.
So basically, in order to get remote access to the point where it's bearable, our choices are:
1) "Trick" Windows into thinking there are two monitors connected to the host PC.
2) Find a way to get RealVNC to display full screen at the local machine's total resolution.
3) Accelerate the Windows Remote Desktop speed to match VNC's speed.
4) Try to locate a plugin that will allow VNC to use server side scaling like WRD does.
5) Find another remote access program - with server side scaling - that is greater than or equal to RealVNC in terms of security, accessibility, functionality, and speed.
Either of those 5 choices will solve the problem. We've been on this issue for a long time now, and any help would be GREATLY appreciated.
Posted 09 May 2007 - 11:06 AM
It does everything I ever need it to.
Posted 09 May 2007 - 12:48 PM
If I read this incorrectly and that part of the issue has been solved, sorry.
Posted 09 May 2007 - 01:33 PM
We shut off ZoneAlarm to complete the RA installation (I know, dumb idea on my part :/ ), and *poof* no more remote connection. We're locked out of VNC and locked out of Windows Remote Desktop! Sigh.
The IP address of the host PC is still able to be ping'd, but I don't know what else to do. The remote host is 400 miles away from here.
Edited by Our House, 09 May 2007 - 01:34 PM.
Posted 09 May 2007 - 01:36 PM
might be able to save the day through there
Posted 09 May 2007 - 01:37 PM
Posted 09 May 2007 - 01:37 PM
I don't think so. Is there any way to find out?
got a telnet server running on the machine?
Posted 09 May 2007 - 01:41 PM
telnet <YOUR MACHINE'S IP ADDRESS HERE>
if it works, it'll ask you for a logon name-password.
if it isnt on, the connection will be refused.
Posted 09 May 2007 - 01:44 PM
...or something along those lines.
What's weird is how shutting ZoneAlarm off would lock us out. I know a firewall that's running can block ports and programs, but a firewall that's not running?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users