- R
- Rajiv Saxena
- Contact options for registered users
In a nutshell, the key difference between the two approaches, VNC and Remote Desktop, is as follows:
a] VNC connects to [a live] desktop session and simply captures the screen on the Master machine and forwards it to you on the listener machine.
b] The remote desktop software in Windows creates a new session of its own on the Master machine and is *completely* different from any sessions running on the same machine. All resources of your desktop [master machine] are shared across the two sessions.
I have seen VNC used extensively for connecting to a live session but it has a few issues. One critical issue is that to be able to connect you must know the IP address of the [Master] machine you are connecting to. In addition, if this machine is behind a firewall, you would need to set up an arrangement so this [Master] machine is visible from the [listener] machine you want to connect from.
If both machines are behind the *same* firewall [for instance, when using a VPN solution], then all you need to know is the IP address of the Master machine, and plug it in the VNC viewer software on the listener machine.
Another issue, with VNC, as pointed out by another poster is that of performance when working with graphics intensive applications such as SolidWorks.
Hope this helps. - Rajiv _____________________ Conferencing and Collaboration for the Knowledge Worker //www.pdmoffice.com
Quoted Text Here
a] VNC connects to [a live] desktop session and simply captures the screen on the Master machine and forwards it to you on the listener machine.
b] The remote desktop software in Windows creates a new session of its own on the Master machine and is *completely* different from any sessions running on the same machine. All resources of your desktop [master machine] are shared across the two sessions.
I have seen VNC used extensively for connecting to a live session but it has a few issues. One critical issue is that to be able to connect you must know the IP address of the [Master] machine you are connecting to. In addition, if this machine is behind a firewall, you would need to set up an arrangement so this [Master] machine is visible from the [listener] machine you want to connect from.
If both machines are behind the *same* firewall [for instance, when using a VPN solution], then all you need to know is the IP address of the Master machine, and plug it in the VNC viewer software on the listener machine.
Another issue, with VNC, as pointed out by another poster is that of performance when working with graphics intensive applications such as SolidWorks.
Hope this helps. - Rajiv _____________________ Conferencing and Collaboration for the Knowledge Worker //www.pdmoffice.com
Quoted Text Here
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- K
- Krister L
- Contact options for registered users
Thanks Raijiv
That helped a lot
Krister L
Quoted Text Here
That helped a lot
Krister L
Quoted Text Here
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- M
- Markku Lehtola
- Contact options for registered users
Quoted Text Here
You should try freeware called Ultr@VNC or similar, but I have a feeling that it's still going to be too slow
You should try freeware called Ultr@VNC or similar, but I have a feeling that it's still going to be too slow
--
regards
Markku
regards
Markku
Click to see the full signature.
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- J
- Jim
- Contact options for registered users
On Thu, 30 Sep 2004 15:35:07 GMT, "Richard Charney"
Quoted Text Here
We are running VNC Viewer 4 with favorable results. I am located in Southwest Michigan and able to work in Solidworks on a PC that is located in Amsterdam. Parts and small assembly speeds are tolerable and this allows me to trouble shoot VB programs that I send over there. Amsterdam is a fun town but after awhile flying over there can be a hassle and I would just as soon do the work from my own office.
Jim
Quoted Text Here
We are running VNC Viewer 4 with favorable results. I am located in Southwest Michigan and able to work in Solidworks on a PC that is located in Amsterdam. Parts and small assembly speeds are tolerable and this allows me to trouble shoot VB programs that I send over there. Amsterdam is a fun town but after awhile flying over there can be a hassle and I would just as soon do the work from my own office.
Jim
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- B
- Bo Clawson
- Contact options for registered users
wrote in message wrote:
Quoted Text Here
Very intriguing.
Hadn't considered it before, but that means I could fire up WinXP on my Mac in Virtual PC [yeah, I know it is slow] and try running my work PC remotely on my PowerBook. I may try it when I get some time.
Bo
Quoted Text Here
Very intriguing.
Hadn't considered it before, but that means I could fire up WinXP on my Mac in Virtual PC [yeah, I know it is slow] and try running my work PC remotely on my PowerBook. I may try it when I get some time.
Bo
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- C
- conj
- Contact options for registered users
There's an installable version for Linux and source code for UNIX. You could probably find an installable version for OS-X. Start at www.realvnc.com
wrote:
Quoted Text Here
Remote
then
wrote:
Quoted Text Here
Remote
then
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- E
- Evan T. Basalik
- Contact options for registered users
I have used SW successfully over both VNC and RDC. It is just like using it locally, although you do miss a screen refresh once in a while.
Remember, RDC comes free if you have a Windows XP machine.
Quoted Text Here
Remember, RDC comes free if you have a Windows XP machine.
Quoted Text Here
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- R
- Richard Charney
- Contact options for registered users
RDC......I'm assuming you mean Remote Desktop Connection. Do you use that with VNC or VPN?
Evan T. Basalik wrote:
Quoted Text Here
Evan T. Basalik wrote:
Quoted Text Here
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- E
- Evan T. Basalik
- Contact options for registered users
I have used it for both.
To make it even more confusing... You can use either VNC or a VPN or RDC to get into your machine from outside your firewall. Then, you use either VNC or RDC to get to another machine on your network.
Are you confused yet?
Quoted Text Here
Remote
then
To make it even more confusing... You can use either VNC or a VPN or RDC to get into your machine from outside your firewall. Then, you use either VNC or RDC to get to another machine on your network.
Are you confused yet?
Quoted Text Here
Remote
then
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply
- R
- rahul
- Contact options for registered users
On Thursday, September 30, 2004 at 9:05:07 PM UTC+5:30, Richard Charney wrote:
Quoted Text Here
can anyone help in setting up VPM connection for PDM client login, I've already set up but there comes an error PDM doesn't connects with archive server & archive socket port please help me out in establishing this connection
Rahul
Quoted Text Here
can anyone help in setting up VPM connection for PDM client login, I've already set up but there comes an error PDM doesn't connects with archive server & archive socket port please help me out in establishing this connection
Rahul
Add pictures here
Add image file
Upload
Bold Italic Underline
Upload Image
Add reply
Notify me about replies to my post Reply