VNC vs. Remote Desktop

[willgill]

Originally Posted by salsbst

For servers, the built-in Remote Desktop is the way to go. You *want* a separate session.

For headless client devices like an HTPC, VNC is preferable because it allows you to access the local session.

Different needs, different tools.

Sure, RDP and Terminal Services are great for running thin clients, supporting remote clients etc. That's a server environment. I just want to make sure people don't confuse Sage "server" with a Windows server running Terminals Services/RDP.

I can't envision too many scenarios where RDP would be better than UltraVNC. I suppose one scenario would be manipulating files without disturbing a running Sage TV session.

I'm not even sure Sage TV installs correctly within a Terminal Services environment.

[willgill]

Originally Posted by owilsky

I had some problems with the hook driver: When I turn on my TV, wake my Sage machine from standby I had a black screen

You're describing a common issue with earlier versions of VNC. I recommend downloading the latest UltraVNC at http://www.ultravnc.com. Before you install it, uninstall your current version.

Also, when you install UltraVNC v1.0.1, make sure you check the option to clean registry keys.

[owilsky]

Originally Posted by willgill

You're describing a common issue with earlier versions of VNC. I recommend downloading the latest UltraVNC at http://www.ultravnc.com. Before you install it, uninstall your current version.

Also, when you install UltraVNC v1.0.1, make sure you check the option to clean registry keys.

I use the latest version (1.0.1), I did not know that this problem was resolved, so I did not install the hook driver.

Do you have further information whether that problem was resolved? Some kind of link?

[willgill]

I guess the "blank screen issue" shouldn't be classified as completely resolved. It has been fixed for most people. Checkout the forums at www.ultravnc.com and do a search for "blank screen". I can't remember the reason it occurs but if memory serves me right, it was a complex issue that occurs less often with each release.

[T3rry]

i use tightvnc, works as good as can be expected, and its a very simple interface.

[gplasky]

If you want to use Remote Desktop and have more than one session available try this:

Terminal Server Patch

From the website:

The beta 2005 release of XP PRO SP2 let you run two or more sessions (one local console and one or more remote desktop) concurrently. But this functionality was removed in the Final release. This patch will enable two or more concurrent sessions in Windows XP PRO Service Pack 2 (SP2) or later if you have FAST USER SWITCHING enabled, and your windows is NOT in a domain.

Works like a champ.

Gerry

[dvd_maniac]

Was wondering if anyone fimiliar with UltraVNC could give me a hand?

I have the latest 1.01 setup and can access it from my LAN but not through the internet. I am trying the Javaviewer way. I have forwarded the port 5800-5900 to the static IP address of the VNC server so I do not know what could be wrong...

[evilpenguin]

let's talk security too.

http://pigtail.net/LRP/vnc/

This page will show you how to tunnel a VNC connection over SSH. Very handy at work because my company has a brutal firewall, however, even they let me use port 22.

Couple that with a service like

https://www.dyndns.com/services/dns/dyndns/

And your in buisness pretty much 24/7 worldwide.

[willgill]

Originally Posted by dvd_maniac

Was wondering if anyone fimiliar with UltraVNC could give me a hand?

I have the latest 1.01 setup and can access it from my LAN but not through the internet. I am trying the Javaviewer way. I have forwarded the port 5800-5900 to the static IP address of the VNC server so I do not know what could be wrong...

I'd first try doing it via port 5900 and using the UltraVNC viewer. That will eliminate any Java issues. If that works, download the latest Java for desktop and try through port 5800. Don't forget to use http://yourhostname.dyndns.org:5800

You might also make sure the name is resolveable.
Click Start, Run, cmd Enter
Type nslookup yourhostname.dyndns.org

[dvd_maniac]

I already have tzo dynamic DNS but I guess that my works firewall is the culprit. I can logon from my friends house, just not at work.

I guess I will try playing around with the ports until I can get it working.

Thanx

[mikejaner]

In your case, then I would go with what evilpenguin is saying. I too have to work through a pretty tough firewall on my corporate network, so I have setup an SSH server at my home with a Squid proxy for surfing the web etc......

[DrBloodmoney]

my ISP (Comcast MD)has blocked port 5800 for whatever reason. So try another port. That's the only way mine works.

[nielm]

warning for UltraVNC users:

If using overlay renderer, the 'video hook driver' will break video playback in Sage if you start video playback while a VNC session is active... You will gext a 0x80040217 error, and you will need to restart Sage...

(this is probably because the video hook driver cannot support video playback)

[mkanet]

The below command is what you are looking for:

tscon.exe 0 /dest:console /password:xxxxxxx

I just created a desktop shortcut to that command and it disconnects my terminal session and puts the desktop the way it was before. Just double-click it when you're done using your terminal session. That simple! If it weren't for this command, I would have looked for an alternate method to remote control my desktop. But as you guys know remote desktop is the fastest, most reliable way to do that...

Originally Posted by owilsky

Hmm.. I do don't want to have multiple logins, I simply do not want my sage machine to lock after disconnection.

Well... UltraVNC works quite well...

[owilsky]

Originally Posted by mkanet

The below command is what you are looking for:

tscon.exe 0 /dest:console /password:xxxxxxx

I just created a desktop shortcut to that command and it disconnects my terminal session and puts the desktop the way it was before. Just double-click it when you're done using your terminal session. That simple! If it weren't for this command, I would have looked for an alternate method to remote control my desktop. But as you guys know remote desktop is the fastest, most reliable way to do that...

Hmmm... I tried this:
tscon.exe 0 /dest:console /server:192.168.1.2 /password:xxxxxxx

But that doesn't work.

But tscon /? gives you some help...

Any ideas?

[mkanet]

Oliver, there is a 100% chance you are doing it wrong. So, please be patient and try various ways to do it. You should first try it at the remote command line and only try one switch at a time. Make sure you specify your password correctly. The command I gave you is the correct way to do it. Good luck!

PS: Server switch isn't necessary.

[SkierHiker]

Just to clarify, the tscon command needs to be executed on the computer running SageTV, not the computer logging into it. And it works just fine. Nice tip.

[ben_95sl1]

I exclusively use the built in winxp remote desktop on 3 computers. The concurrent sessions modifications fix the problem and work great (I constantly work on my htpc/sagetv server remotely while my gf watches tv undisturbed). I don't like adding software unless necessary, even though I'm sure vnc is great.

[bcjenkins]

VNC is great for things like configuring audio and video properties of the sage server/client. RDP is much faster and easier for other items including installing and upgrading Sage.

M2C

B

[jominor]

Originally Posted by gplasky

If you want to use Remote Desktop and have more than one session available try this:

Terminal Server Patch

From the website:

The beta 2005 release of XP PRO SP2 let you run two or more sessions (one local console and one or more remote desktop) concurrently. But this functionality was removed in the Final release. This patch will enable two or more concurrent sessions in Windows XP PRO Service Pack 2 (SP2) or later if you have FAST USER SWITCHING enabled, and your windows is NOT in a domain.

Works like a champ.

Gerry

Thanks! I've been looking for that.