Is there any less laggy than VNC?

[PushHands]

I'm using WinVNC for the first time on a 100mb network and it's quite neat. But has anyone experience others that are less laggy?

 

[Nothinman]

TightVNC has better compression than normal VNC.

 

[MichaelD]

Originally posted by: Nothinman
TightVNC has better compression than normal VNC.

I second this. I used Win VNC for a long time...never bothering to take advice and try Tight VNC. It is 10x better. And it's also FREE. Give it a shot, you'll like it. It sets up exactly the same as the old VNC...no learning curve involved.

 

[PushHands]

AWESOME! Thank you guys!! Now I realistically do what I wanted to, which was to have one station as my dedicated research station and the other as every day use. I have this set up for a reason

 

[MichaelD]

Cool. We're glad that it is doing what you need it to do for you. Happy to help.

 

[PushHands]

up one more time for those who don't know about this. very tight software *pun intended*

 

[gaidin123]

TightVNC is great, but if you are using Windows 2000 server or WinXP Pro you can use terminal services/remote desktop and that is definitely the least laggy of all remote control software I've used. RDP specifically caches windows, bitmap images, etc. so that after the server sends the window data once, your client remembers to used the cached version the next time you open it (try it with the start menu in XP) as long as nothing's changed.

TightVNC is free and very quick and useful, but RDP is the least laggy but is Windows only for the most part.

Gaidin

 

[Nothinman]

TightVNC is free and very quick and useful, but RDP is the least laggy but is Windows only for the most part.

For the most part? The only non-Windows RDP client MS has released is for Mac OS and I'm surprised they released that. There's rdesktop for most unixes, but it's based on reverse engineered protocol specs and can have problems.

 

[PushHands]

Originally posted by: gaidin123
TightVNC is great, but if you are using Windows 2000 server or WinXP Pro you can use terminal services/remote desktop and that is definitely the least laggy of all remote control software I've used.

Gaidin

For clarity, in order to access compB from compA, would you need to run XP Pro on both machines or just one computer, and if so, which one? I had XP Pro running but due to all its features, I went back to win2k.

 

[Fuzznuts]

i tired tightVnc it compared to realVnc it suxed there was a noticeable difference between the two on my LAN i went staright back to RealVnc it may be worth you trying that one as well to see whcih performs better for you. This was on various linux boxes btw and each time realvnc was much snappier.

 

[tboneuls]

To use RDP you only need to have 2k or XP Pro on the Hosting computer. The client for this is available here - http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp. I think there is a client for Linux that uses the same protocol, but im not sure. RDP is definetly the best if the two computers are on the same network. Works alright over cable as well. It's really neat b/c it transmits everything (inlcuding sound, which suprised me at first).

 

[gaidin123]

For clarification, yes only the hosting computer needs XP Pro. The MS RDP client runs on at least Win98 and above. Also, when I said "for the most part" I was thinking about LTSP, or the linux terminal server project. I am not sure how interoperable it is with MS' RDP implementation but it does use RDP doesn't it? Also there is rdesktop for linux but Nothingman was right, it can have problems.

Gaidin

 

[PushHands]

At the suggestion of tboneuls, I visited Microsoft's website and guess what I found?

You DO NOT have to run 2k server or XP in order to use Remote Desktop Connection. You need the XP disk though, which is required so you can install the Remote Desktop program. According to this MS guide, you can run it on any Windows based OS. Woo hoo!

I'm accessing a XP box via a 2k box as we speak. Very smooth

 

[PushHands]

Quick update:

It seems I was mistaken in my last message. You can use any Windows OS to view other computers. But, as gaidin123 pointed out, I believe the machine you're trying to access must "terminal services/remote desktop", i.e. W2k Server or XP

Hope this clears things up.

 

[TJN23]

along these same lines, if i want to access my desktop at home, which is protected by a d-link 604+ router inside a lan with an ip address of 192.168.0.100, from another computer on the Internet, would I tell my router to forward port "5800" to my pc in the LAN? i've tried this and it doesnt work, the only way for me to access it is if i turn DMZ on, which I don't want to do.

edit: this is assuming i view my pc through a browser with the socket "http://myiphere:5800" and not the viewing program (.exe file)

 

[Smilin]

Hey I thought I'd throw this out there:

There is a commercial program available from funk software called "proxy". It's doesn't quite beat VNC for price but it's the best remote control software I've seen. Very low latency, very fast. Even though it's not free it's very reasonably price (especially compared to pc anywhere and whatnot)

 

[Smilin]

One more thing to throw out there:

If you use terminal services, goto microsoft and get the terminal services advanced client. It let's you do terminal services from within a web browser. I've got a web page running on my pc here at work that I just browse to whenever I need to remote into a domain controller or something. It's nice to be "at the server" and "at someone's desk" at the same time.