Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
New UVNC user, having difficulty with SC on 'net
New UVNC user, having difficulty with SC on 'net
I am happy to have found this treasure! VNC is an awesome product, and while I've known of it for years, only now do I have a good application for it personally.
The viewer is a home implementation, so I have admin on the home computer, as well as the DSL Router. The SC portion would be for my parents & friends to use, and if it works well, eventually my clients.
I have made two .exe files using the online utility. One is internet driven (using DDNS), and one is intranet driven (using private IP). The private implementation works well, however, the internet version does not work.
I have sank three days into this, and have tried various things. Two routers, mounds of articles & documentation. I've even attempted IP Passtrhough.
Here's the deal--I used wireshark to capture the success of the intranet UVNC configuration. Comparing that to my failure in the intranet variant, I can see the SC machine making the initiation. I DO NOT SEE the machine hosting the viewer--in lisenting mode--responding as a source the way I do in the successful intranet use. I've tried different ports for SC, different routers, and even IP Passthrough to no avail.
Have I missed something basic? I don't want to be reliant on repeater, epecially if I want this to mature.
Any suggestions are GREATLY appreciated.
The viewer is a home implementation, so I have admin on the home computer, as well as the DSL Router. The SC portion would be for my parents & friends to use, and if it works well, eventually my clients.
I have made two .exe files using the online utility. One is internet driven (using DDNS), and one is intranet driven (using private IP). The private implementation works well, however, the internet version does not work.
I have sank three days into this, and have tried various things. Two routers, mounds of articles & documentation. I've even attempted IP Passtrhough.
Here's the deal--I used wireshark to capture the success of the intranet UVNC configuration. Comparing that to my failure in the intranet variant, I can see the SC machine making the initiation. I DO NOT SEE the machine hosting the viewer--in lisenting mode--responding as a source the way I do in the successful intranet use. I've tried different ports for SC, different routers, and even IP Passthrough to no avail.
Have I missed something basic? I don't want to be reliant on repeater, epecially if I want this to mature.
Any suggestions are GREATLY appreciated.
Re: New UVNC user, having difficulty with SC on 'net
Very interesting...
Specifically what I am not seeing on the Viewer PC Network when the SC program is initiated from a computer on the internet is the VNC protocol from the computer running SC. I see the TCP from the SC computer, but not the VNC 'next step' which seems to initiate the success from my internet.
I wonder if I have happened across two routers that aren't supportive of VNC protocol, which I have never heard of before. The only setup options for forwarding is TCP & UDP, and my understanding WAS that VNC only used TCP.
Could be a poor characterization in WireShark Network Monitoring?
Thanks!
Specifically what I am not seeing on the Viewer PC Network when the SC program is initiated from a computer on the internet is the VNC protocol from the computer running SC. I see the TCP from the SC computer, but not the VNC 'next step' which seems to initiate the success from my internet.
I wonder if I have happened across two routers that aren't supportive of VNC protocol, which I have never heard of before. The only setup options for forwarding is TCP & UDP, and my understanding WAS that VNC only used TCP.
Could be a poor characterization in WireShark Network Monitoring?
Thanks!
Re: New UVNC user, having difficulty with SC on 'net
Hey, I think I am having the exact same problem here....yzarcem wrote:I am happy to have found this treasure! VNC is an awesome product, and while I've known of it for years, only now do I have a good application for it personally.
The viewer is a home implementation, so I have admin on the home computer, as well as the DSL Router. The SC portion would be for my parents & friends to use, and if it works well, eventually my clients.
I have made two .exe files using the online utility. One is internet driven (using DDNS), and one is intranet driven (using private IP). The private implementation works well, however, the internet version does not work.
I have sank three days into this, and have tried various things. Two routers, mounds of articles & documentation. I've even attempted IP Passtrhough.
Here's the deal--I used wireshark to capture the success of the intranet UVNC configuration. Comparing that to my failure in the intranet variant, I can see the SC machine making the initiation. I DO NOT SEE the machine hosting the viewer--in lisenting mode--responding as a source the way I do in the successful intranet use. I've tried different ports for SC, different routers, and even IP Passthrough to no avail.
Have I missed something basic? I don't want to be reliant on repeater, epecially if I want this to mature.
Any suggestions are GREATLY appreciated.
I am not able to connect with SC from the internet but am able to connect with SC through my lan. For instance, if I have both PC's on local ip's such as 192.168.1.X SC connects right away to the viewer in listening mode. However, if I put the listening viewer machine on a STATIC IP on my DSL (netopia 2247nwg router) I can not make the SC connection from any computer. This includes from the internet and also includes from other computers on my network that also have static IP's from my DSL router (I have 5 static IP's). I dont really understand why, because the local numbers and the DSL numbers both put the host and remote computers on the same net and subnet, they should connect just the same I would think but dont? Of coarse I changed the SC IP over from the LAN IP to my Static IP, so thats not the problem. Could this be a bug with SC? Or a router thing? I have my firewalls off and there is no NAT so no port forwarding needed (with static IP) so I just dont know what is going on or what else to try?
I was thinking of trying a different port but dont know how to change the listening port on the viewer? If anyony knows what flag I should use on the viewer to change the port on listening mode I would appreciate it. Also, is there some other way SC can connect than using the viewer?
Re: New UVNC user, having difficulty with SC on 'net
Sounds very similar to my problem. To change the port from the default 5500 regarding the viewer, from command line, it is:
C:\Program Files\UltraVNC> vncviewer.exe -listen 5501
This example would run the viewer in listening mode on port 5501.
I'm open to suggestions from anyone. I believe we can rule out probelms with the PC running the viewer, right? I saw some writing geared towards an option on the viewer to allow external connection & not just local, but I can't find that on my viewer version (1.0.5).
Ideas anyone? I do think it's the viewer for some reason, though. I don't understand why the PC running the viewer wouldn't respond (proven through the Wireshark observation) unless it were something like that.
C:\Program Files\UltraVNC> vncviewer.exe -listen 5501
This example would run the viewer in listening mode on port 5501.
I'm open to suggestions from anyone. I believe we can rule out probelms with the PC running the viewer, right? I saw some writing geared towards an option on the viewer to allow external connection & not just local, but I can't find that on my viewer version (1.0.5).
Ideas anyone? I do think it's the viewer for some reason, though. I don't understand why the PC running the viewer wouldn't respond (proven through the Wireshark observation) unless it were something like that.
Re: New UVNC user, having difficulty with SC on 'net
Thanks for the info RE changing listening port. I was thinking something similar, like a flag that is set to allow only local or local and external connections? I assume this flag would be set on the viewer? I haven't really seen any docs that list all the flags and parameters that can be used with these UVNC apps, perhaps if we had that all in front of us we could figure it out? Or maybe someone with experience can help us out here???yzarcem wrote:Sounds very similar to my problem. To change the port from the default 5500 regarding the viewer, from command line, it is:
C:\Program Files\UltraVNC> vncviewer.exe -listen 5501
This example would run the viewer in listening mode on port 5501.
I'm open to suggestions from anyone. I believe we can rule out probelms with the PC running the viewer, right? I saw some writing geared towards an option on the viewer to allow external connection & not just local, but I can't find that on my viewer version (1.0.5).
Ideas anyone? I do think it's the viewer for some reason, though. I don't understand why the PC running the viewer wouldn't respond (proven through the Wireshark observation) unless it were something like that.
Please let me know if you make any progress and I will do the same, thanks....
-
- Posts: 2
- Joined: 2008-09-06 20:45
- Location: Houston
- Contact:
Re: New UVNC user, having difficulty with SC on 'net
I would advise two things. First, on a computer with winvnc installed, right-click on winvnc, and click Add Client - this is the way to make a reverse connection in the full package, basically what SC does for you. That will remove SC from the equation - if it does not work, you know it is a firewall or vncviewer issue, not an SC issue.
Second, telnet from a computer to your external ip and port number... what you should see is a successful connection and then nothing. Type in
and hit enter. An almost identical response should appear on a line by itself. This tells you that vnc is listening.
example:
Again, in the above, I typed the first RFB line, and it responded with the second. If the RFB line appears the instant you connect telnet, you have connected to a winvnc server, not a vncviewer listener.
If you get connection refused, that says you don't have the port successfully opened in the firewall.
Once you can successfully connect with both telnet, and a reverse connection (Add Client) from winvnc, then you can create your SC and deploy it with confidence.
Second, telnet from a computer to your external ip and port number... what you should see is a successful connection and then nothing. Type in
Code: Select all
RFB 003.006
example:
Code: Select all
user@machine:~$ telnet somecomputer.dynalias.com 5501
Trying 99.99.99.99...
Connected to somecomputer.dynalias.com.
Escape character is '^]'.
RFB 003.006
RFB 003.004
If you get connection refused, that says you don't have the port successfully opened in the firewall.
Once you can successfully connect with both telnet, and a reverse connection (Add Client) from winvnc, then you can create your SC and deploy it with confidence.
Howard C. Shaw III
Re: New UVNC user, having difficulty with SC on 'net
Thanks for your help. That sets my direction, at least. I tried a traditional Server setup before I posted...it was the same result. It worked great on a local/private network, but when I stand it up on the internet, I have the trouble.
Thanks for the telnet advice...I didn't think of that. My results yield the same problem that I see with VNC. From the machine that would be the viewer, I can see the tenet request being forwarded to my PC on port 5500. However, there is no response. From the machine that I use to initiate the telnet on 5500, "Could not open connection to the host on port 5500: Connect failed."
I can see the telnet initiator coming inside the router (from the IP), but there is no repsonse generated. I changed the viewer version to 1.0.2 and got the same result. Am I looking in the wrong place? The modem/router I am using is an older Westell (Bellsouth), and the port forwarding setup is almost too easy. I also tried a Netopia, which was equally as easy to setup. Same results on both.
Any other recommendations? Buying a new router is against my grain, but if anyone thinks it may be an advantage, I'm game.
Thanks for the telnet advice...I didn't think of that. My results yield the same problem that I see with VNC. From the machine that would be the viewer, I can see the tenet request being forwarded to my PC on port 5500. However, there is no response. From the machine that I use to initiate the telnet on 5500, "Could not open connection to the host on port 5500: Connect failed."
I can see the telnet initiator coming inside the router (from the IP), but there is no repsonse generated. I changed the viewer version to 1.0.2 and got the same result. Am I looking in the wrong place? The modem/router I am using is an older Westell (Bellsouth), and the port forwarding setup is almost too easy. I also tried a Netopia, which was equally as easy to setup. Same results on both.
Any other recommendations? Buying a new router is against my grain, but if anyone thinks it may be an advantage, I'm game.
Last edited by yzarcem on 2008-09-07 01:22, edited 1 time in total.
Re: New UVNC user, having difficulty with SC on 'net
Last note for the evening. I configured & tried each of my two routers (for the viewer PC) for complete IP Passthrough and gave VNC, as well as telent as described above, a shot. Same results.
Thinking that the machine running the viewer (Vista machine) might have a firewall issue that would allow it to work in my local subnet, but deny internet, I disabled the firewall & Windows Defender, too. No joy. I uninstalled UVNC & gave the RealVNC Viewer a shot. Same deal...no joy. Very interesting.
Thinking that the machine running the viewer (Vista machine) might have a firewall issue that would allow it to work in my local subnet, but deny internet, I disabled the firewall & Windows Defender, too. No joy. I uninstalled UVNC & gave the RealVNC Viewer a shot. Same deal...no joy. Very interesting.
Last edited by yzarcem on 2008-09-07 12:50, edited 2 times in total.
Re: New UVNC user, having difficulty with SC on 'net
Here's my LAN Success Log--192.168.1.1 is the machine running the SC executable. 192.168.1.97 is my Viewer running in listen mode.
No. Time Source Destination Protocol Info
13 1.860859 192.168.1.1 192.168.1.97 TCP
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
14 1.860965 192.168.1.97 192.168.1.1 TCP
Transmission Control Protocol, Src Port: fcp-addr-srvr1 (5500), Dst Port: opennl (1258), Seq: 0, Ack: 1, Len: 0
No. Time Source Destination Protocol Info
15 1.861419 192.168.1.1 192.168.1.97 TCP
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 1, Ack: 1, Len: 0
No. Time Source Destination Protocol Info
16 1.866583 192.168.1.1 192.168.1.97 VNC Server protocol version: 003.016
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 1, Ack: 1, Len: 12
Virtual Network Computing
No. Time Source Destination Protocol Info
17 1.882335 192.168.1.97 192.168.1.1 VNC Client protocol version: 003.016
Transmission Control Protocol, Src Port: fcp-addr-srvr1 (5500), Dst Port: opennl (1258), Seq: 1, Ack: 13, Len: 12
Virtual Network Computing
No. Time Source Destination Protocol Info
18 1.888090 192.168.1.1 192.168.1.97 VNC
Frame 18 (70 bytes on wire, 70 bytes captured)
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 13, Ack: 13, Len: 4
Virtual Network Computing
No. Time Source Destination Protocol Info
19 1.888093 192.168.1.1 192.168.1.97 VNC
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 17, Ack: 13, Len: 182
Virtual Network Computing
No. Time Source Destination Protocol Info
20 1.888189 192.168.1.97 192.168.1.1 TCP
Transmission Control Protocol, Src Port: fcp-addr-srvr1 (5500), Dst Port: opennl (1258), Seq: 13, Ack: 199, Len: 0
No. Time Source Destination Protocol Info
13 1.860859 192.168.1.1 192.168.1.97 TCP
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
14 1.860965 192.168.1.97 192.168.1.1 TCP
Transmission Control Protocol, Src Port: fcp-addr-srvr1 (5500), Dst Port: opennl (1258), Seq: 0, Ack: 1, Len: 0
No. Time Source Destination Protocol Info
15 1.861419 192.168.1.1 192.168.1.97 TCP
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 1, Ack: 1, Len: 0
No. Time Source Destination Protocol Info
16 1.866583 192.168.1.1 192.168.1.97 VNC Server protocol version: 003.016
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 1, Ack: 1, Len: 12
Virtual Network Computing
No. Time Source Destination Protocol Info
17 1.882335 192.168.1.97 192.168.1.1 VNC Client protocol version: 003.016
Transmission Control Protocol, Src Port: fcp-addr-srvr1 (5500), Dst Port: opennl (1258), Seq: 1, Ack: 13, Len: 12
Virtual Network Computing
No. Time Source Destination Protocol Info
18 1.888090 192.168.1.1 192.168.1.97 VNC
Frame 18 (70 bytes on wire, 70 bytes captured)
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 13, Ack: 13, Len: 4
Virtual Network Computing
No. Time Source Destination Protocol Info
19 1.888093 192.168.1.1 192.168.1.97 VNC
Transmission Control Protocol, Src Port: opennl (1258), Dst Port: fcp-addr-srvr1 (5500), Seq: 17, Ack: 13, Len: 182
Virtual Network Computing
No. Time Source Destination Protocol Info
20 1.888189 192.168.1.97 192.168.1.1 TCP
Transmission Control Protocol, Src Port: fcp-addr-srvr1 (5500), Dst Port: opennl (1258), Seq: 13, Ack: 199, Len: 0
Re: New UVNC user, having difficulty with SC on 'net
Here's my sap story...an attempt to make this same thing work using the internet. 192.168.1.97 is still my Vista machine running the viewer in listen mode (listening on the same default port...5500), and 24.214.10.146 is the origin of the client running the SC executable. Same results running the full-up server. Notice there is no 'VNC' protocol, as mentioned in the success above. Also notice that there is no source response from the viewer--192.168.1.97.
No. Time Source Destination Protocol Info
1 0.000000 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: sdsc-lm (1537), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
2 3.004608 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: sdsc-lm (1537), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
3 9.026900 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: sdsc-lm (1537), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
4 40.033331 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: 3ds-lm (1538), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
5 43.002692 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: 3ds-lm (1538), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
6 49.013169 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: 3ds-lm (1538), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
7 75.085188 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: intellistor-lm (1539), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
8 78.057231 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: intellistor-lm (1539), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
9 84.064281 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: intellistor-lm (1539), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
1 0.000000 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: sdsc-lm (1537), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
2 3.004608 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: sdsc-lm (1537), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
3 9.026900 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: sdsc-lm (1537), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
4 40.033331 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: 3ds-lm (1538), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
5 43.002692 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: 3ds-lm (1538), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
6 49.013169 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: 3ds-lm (1538), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
7 75.085188 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: intellistor-lm (1539), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
8 78.057231 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: intellistor-lm (1539), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
No. Time Source Destination Protocol Info
9 84.064281 24.214.10.146 192.168.1.97 TCP
Transmission Control Protocol, Src Port: intellistor-lm (1539), Dst Port: fcp-addr-srvr1 (5500), Seq: 0, Len: 0
Last edited by yzarcem on 2008-09-07 19:23, edited 1 time in total.
Re: New UVNC user, having difficulty with SC on 'net
Making prgress here. I have isolated my problem to a config within Vista.
Here's the deal--I dropped in a plain-Jane XP machine behind my router. I turned off the XP Firewall, installed VNC 1.0.5, updated my router to give the XP machine the same rules that the Vista machine, and IT WORKS.
Something about Vista!
Now...does anyone have any recommendations for Vista configuration? I'd hate to install a KVM, or a Virtual Machine, to make this work.
Here's the deal--I dropped in a plain-Jane XP machine behind my router. I turned off the XP Firewall, installed VNC 1.0.5, updated my router to give the XP machine the same rules that the Vista machine, and IT WORKS.
Something about Vista!
Now...does anyone have any recommendations for Vista configuration? I'd hate to install a KVM, or a Virtual Machine, to make this work.
Re: New UVNC user, having difficulty with SC on 'net
Alright...let's close this out. I found the problem.
Vista, like XP before it, as it comes from hp & various other manufacturers, has several add-ons that are useless to most folks. We all know that.
Normally, I wipe the hard drive & re-install so I KNOW WHAT I HAVE. Vista has changed that concept. Norton & several othter things were loaded on this machine when it arrived in my home. I removed (via Control Panel) all of the baggage. Normally I give the registry a scrub with Norton, but removal went unusually well (Kudos to them, I thought), so I let it ride.
When I ran across this VNC issue, I started looking at all elements of Vista...what could be hamepring my PC from responding. I found that while I had disabled Windows Firewall (I made the rules, but when I still expereienced problems, I opened it completely in this way), The Security Center still noted that I had an active firewall. NOTON ANTIVIRUS listed as a firewall. Thought I had removed that, right? Wrong. I scrubbed the registry, found the handy removal tool & ran it, too, for good measure, rebooted...
Now I'm in business. The connections work as they should. Norton should be ashamed of distributing something that can't clean up after itself, although they've been doing it for years. That's the basics!
Anyhow, I know I'm preaching to the choir, and I'm glad I posted in the begginner's forum for such a basic cause.
After all of this, for grins, I turned on my wimpy Windows Firewall with the rules added, and I'm still in business. Now...on to encryption & optimization.
Vista, like XP before it, as it comes from hp & various other manufacturers, has several add-ons that are useless to most folks. We all know that.
Normally, I wipe the hard drive & re-install so I KNOW WHAT I HAVE. Vista has changed that concept. Norton & several othter things were loaded on this machine when it arrived in my home. I removed (via Control Panel) all of the baggage. Normally I give the registry a scrub with Norton, but removal went unusually well (Kudos to them, I thought), so I let it ride.
When I ran across this VNC issue, I started looking at all elements of Vista...what could be hamepring my PC from responding. I found that while I had disabled Windows Firewall (I made the rules, but when I still expereienced problems, I opened it completely in this way), The Security Center still noted that I had an active firewall. NOTON ANTIVIRUS listed as a firewall. Thought I had removed that, right? Wrong. I scrubbed the registry, found the handy removal tool & ran it, too, for good measure, rebooted...
Now I'm in business. The connections work as they should. Norton should be ashamed of distributing something that can't clean up after itself, although they've been doing it for years. That's the basics!
Anyhow, I know I'm preaching to the choir, and I'm glad I posted in the begginner's forum for such a basic cause.
After all of this, for grins, I turned on my wimpy Windows Firewall with the rules added, and I'm still in business. Now...on to encryption & optimization.
Last edited by yzarcem on 2008-09-08 13:29, edited 1 time in total.