eschamp
asked on
Simple Question about Setting Up VNC SC
1) I would like to build a customized version of the UltraVNC SC program that I can send to other people to use when they would like me to control their computers.
I know I have to edit helpdesk.txt and provide an IP address and a port number. I've been told to use the IP address that is reported by whatismyipaddress.com (71.245.221.xxx). I also discovered that VNC is a service known to my Westell gateway and uses port 5500 as the primary port, so I will use the following:
71.245.221.xxx:5500
Then all I have to do is create a ZIP file of helpdesk.txt and whatever else -- rc4.key and images -- I want to use, and then use the online creator.
I can send the result to anyone I like. When they want me to look at their computer, they call me to alert me and then run the program I sent them (the program does not have to be installed.)
Am I right so far?
2. If I want to place the Ultra VNC SC program on a computer that is connected to my LAN, the 71.245.221.xxx number is no good, right?
Can I just create a second program with the internal IP address (192.168.1.xxx) of the computer that will run VNC in listen mode in helpdesk.txt?
3. Is there an SC for Linux?
Thanks.
I know I have to edit helpdesk.txt and provide an IP address and a port number. I've been told to use the IP address that is reported by whatismyipaddress.com (71.245.221.xxx). I also discovered that VNC is a service known to my Westell gateway and uses port 5500 as the primary port, so I will use the following:
71.245.221.xxx:5500
Then all I have to do is create a ZIP file of helpdesk.txt and whatever else -- rc4.key and images -- I want to use, and then use the online creator.
I can send the result to anyone I like. When they want me to look at their computer, they call me to alert me and then run the program I sent them (the program does not have to be installed.)
Am I right so far?
2. If I want to place the Ultra VNC SC program on a computer that is connected to my LAN, the 71.245.221.xxx number is no good, right?
Can I just create a second program with the internal IP address (192.168.1.xxx) of the computer that will run VNC in listen mode in helpdesk.txt?
3. Is there an SC for Linux?
Thanks.
ASKER
There's no point in futzing around testing when there's someone out there who knows the answers!
You hope that helps? Yeah, right!
You hope that helps? Yeah, right!
1. Yes
2. You need to forward port 5500 from your router to the IP of the computer you wish to use for the SC VNC service
3. None that I am aware of.
2. You need to forward port 5500 from your router to the IP of the computer you wish to use for the SC VNC service
3. None that I am aware of.
ASKER
Thanks, RobWill.
About #2. My router/modem does not permit me to specify an IP address. It permits enabling VNC in port-forwarding mode, and I can specify the name of the host computer (the one I will run "listen" on). Is that sufficient?
I thought that if I opened 5500 for VNC, and VNC program calling that router would be passed on through.
About #2. My router/modem does not permit me to specify an IP address. It permits enabling VNC in port-forwarding mode, and I can specify the name of the host computer (the one I will run "listen" on). Is that sufficient?
I thought that if I opened 5500 for VNC, and VNC program calling that router would be passed on through.
#2 Simple answer: yes
Longer answer: The router needs to know to which computer to forward the 5500 traffic. You may for example have 20 computers behind that router so one has to be specified. With most routers you use "port forwarding" or enable a "virtual server" service that allows you to specify the port (sometimes both external and internal), and the IP of the PC to which you want to forward the traffic. If your unit has a built in service for VNC great, and if it allows you to specify the computer name rather than IP, that is even better as you are likely using DHCP and using the name will always work.
The one catch: the required port is 5500. Some versions of VNC use port 5900 & 5901, make sure your service is using 5500. If not, you will have to do so by port number.
Also if you have any firewalls or security suites installed on your PC (the one to which the router forwards the 5500 traffic), you need to disable it, or configure it to allow incoming 5500 traffic.
Effectively the client is making an incoming connection to you, using the VNC SC custom file you provide.
>>"I thought that if I opened 5500 for VNC, and VNC program calling that router would be passed on through."
When you create your custom SC file for the client, it will contain the public IP of your router. The SC app contacts that IP, and then as you say, the router forwards that traffic to your PC. If the VNC listener is enabled, it will detect the request and prompt you to allow the connection.
I have only used the service a few times. it works well, but I had issues with the encryption as I recall. If having problems, try with out the encryption until you have it working and then add.
By the way you cannot test from one PC on your network to another. This would require the router support "hairpinning" which does not work with most routers.
i.e. you need to test from off site or a different external/public IP.
Longer answer: The router needs to know to which computer to forward the 5500 traffic. You may for example have 20 computers behind that router so one has to be specified. With most routers you use "port forwarding" or enable a "virtual server" service that allows you to specify the port (sometimes both external and internal), and the IP of the PC to which you want to forward the traffic. If your unit has a built in service for VNC great, and if it allows you to specify the computer name rather than IP, that is even better as you are likely using DHCP and using the name will always work.
The one catch: the required port is 5500. Some versions of VNC use port 5900 & 5901, make sure your service is using 5500. If not, you will have to do so by port number.
Also if you have any firewalls or security suites installed on your PC (the one to which the router forwards the 5500 traffic), you need to disable it, or configure it to allow incoming 5500 traffic.
Effectively the client is making an incoming connection to you, using the VNC SC custom file you provide.
>>"I thought that if I opened 5500 for VNC, and VNC program calling that router would be passed on through."
When you create your custom SC file for the client, it will contain the public IP of your router. The SC app contacts that IP, and then as you say, the router forwards that traffic to your PC. If the VNC listener is enabled, it will detect the request and prompt you to allow the connection.
I have only used the service a few times. it works well, but I had issues with the encryption as I recall. If having problems, try with out the encryption until you have it working and then add.
By the way you cannot test from one PC on your network to another. This would require the router support "hairpinning" which does not work with most routers.
i.e. you need to test from off site or a different external/public IP.
ASKER
I think your reply pertained to computers from outside my LAN contacting the VNC "listener" on my PC.
My question #2 pertained to computers that are ON my LAN. They do not see the public IP of my modem/router as they are connected on "this" side of the router.
To restate #2, if I want to place the Ultra VNC SC program on a computer that is connected to my LAN, can I just create a second program with the internal IP address (192.168.1.xxx) of my PC (the computer that will run VNC in listen mode) in helpdesk.txt?
Thanks.
My question #2 pertained to computers that are ON my LAN. They do not see the public IP of my modem/router as they are connected on "this" side of the router.
To restate #2, if I want to place the Ultra VNC SC program on a computer that is connected to my LAN, can I just create a second program with the internal IP address (192.168.1.xxx) of my PC (the computer that will run VNC in listen mode) in helpdesk.txt?
Thanks.
Sure just use the local IP, however you do not need to use SC inside a LAN. Basic VNC will work there or even Microsoft Remote Assistance, but perhaps you have reasons to do so. Also on a LAN you don't need to worry about the encryption features.
ASKER
Basic VNC? Don't I need a server on one machine and a client on the other?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for that explanation. However, if I would like to use SC on computer B, I can just use the local IP address in the helpdesk,txt file.
I'm trying to get a feel for SC so I can give detailed instructions to the non-technical people I assist.
I'm trying to get a feel for SC so I can give detailed instructions to the non-technical people I assist.
Thanks eschamp.
I can see using SC for that.
Can't you simply add the local IP under the [HOST] section of the heldesk.txt file?
I can see using SC for that.
Can't you simply add the local IP under the [HOST] section of the heldesk.txt file?
Here is a trick you can do to use a single vnc sc on the inside and outside the network.
Rather than using an IP address you can use a fully qualified domain name. eg vnc.mydomain.com
In your external dns you set vnc.mydomain.com to point to your external ip address.
If you have an internal DNS server you make it point to the private ip address
or
You make an entry in the hosts file on each PC to point to the internal ip address.
You can use this trick for other applications as well.
Rather than using an IP address you can use a fully qualified domain name. eg vnc.mydomain.com
In your external dns you set vnc.mydomain.com to point to your external ip address.
If you have an internal DNS server you make it point to the private ip address
or
You make an entry in the hosts file on each PC to point to the internal ip address.
You can use this trick for other applications as well.
Try both a local version and using your public IP, should be easy enough to test.
I hope this helps !