Remote Desktop and TightVNC

[Mickwish]

Firstly, this isn't a "what is better" thread. I use both of these for different things.

For my internal LAN I use TightVNC to access my DC boxes (no monitor/keyboard/mouse attached). Works great, no problems. Except for one weird thing...

I've started to use M$'s Remote Desktop to access my home LAN from work. Forwarded the appropriate port through my firewall box, and it works great. Good connection speed, much better security of connection that VNC.

I've noticed something weird though. If I access through Remote Desktop to my main PC, then disconnect and then go to try to access my FAD queue server (on another box) with VNC over the 'net, I can't then access my main PC via VNC. It lets me connect, but I just get a blank screen! Won't let me send any commands at all.

I assume this is because Remote Desktop disconnects my login, but I know the progs are still all running happily. Anyone have any ideas how this might be fixed, if at all? Anyone ever run into it?

It's not a big deal, as I now don't wanna use VNC over the 'net, but it's just weird.

Thanks
Mick

[implexant]

I'm assuming this is with XP?

If it is I think it's just one of them things. Because XP logs out the user when starting a new TS session, and then logs in for the TS session, and then logs back out after the TS session. Just make sure VNC is running as a service.

I generally use VNC for client's workstations and TS for the servers. XP's TS just doesn't cut it for me.

-Chris

[Mickwish]

Yep, the main PC is XP. I connect through win2k at work.

VNC ALWAYS runs as a service on all of my boxes.

Like I said, VCN still connects to the box, it just doesn't show anything.

I might try using diff screen numbers (like computername:1), but I doubt that will help.

I think you're right, Just one of them weird things.

Cheers
Mick

[implexant]

Well IMO, VNC doesn't run correctly when a user is not logged in. I've noticed a few odd problems somewhat related to your's when connecting to different machines that were on, yet logged off.

The general rule for my clients is: leave the computer on, keep it logged in. When away from the computer, lock the workstation.

This solves both my VNC problem, and the security issue. Plus, they can keep their programs running.

-Chris

[Mickwish]

Actually, VNC runs fine before a user is logged in. My queue server has winNT server on it, and I can connect through VNC on startup and login fine.

It's just weird that VNC is happliy running but you can't get a screen after disconnecting Remote Desktop. VNC works perfectly whilst Remote Desktop is logged in, just not after it disconnects.

Plus, they can keep their programs running.

...including the DC's, eh?

Thanks
Mick

[implexant]

Originally posted by Mickwish

...including the DC's, eh?

Actually, that's truer that you might think I have asked several of my clients if I can run ECC2 on their machines, 90% have agreed, lending to my 24Ghz of power

What I was trying to say, was that XP's TS probably has a flaw in which it doesn't log off properly. Therefore, after logging off a TS session, you are stuck with VNC not functioning properly.

At least, that's my thought and experience.

Whatever the case, I experience the same deal. That's why I have pulled the plug on using XP's TS.

I'd just plain use VNC across everything unless you are willing to get Win2k Server on your main machine.

VNC is of course slower, but it really isn't for me. I have all my clients on Speakeasy ISDL/T1/ADSL/SDSL connections, so my Speakeasy 1.5/768 ADSL connection is practically LAN speed with VNC due to everyone using the same ISP.

You might look into a SSH tunnel for your main windows machine, that'd give you some security with your whole VNC session.

-Chris