Failed to connect to server !

JohnHace · Post by **JohnHace** » 2010-04-28 22:48

I have the repeater running and when InstantSupport is run, I see the number appear in the log. But when I run Chunkviewer.exe, after a few seconds, the VncViewer Message Box gives me the "Failed to connect to server !" message.

The two computers with InstantSupport and Chunkviewer are on the same DSL network and the repeater computer is on a different cable modem.

I don't know where to start to resolve this.

I'd really appreciate your help.

supercoe · Post by **supercoe** » 2010-04-28 22:54

While viewing the repeater log window run ChunkViewer and enter the ID 555666 if you don't see "Viewer added to list 555666" then double check your port forwards.

Port 5901 needs to be forwarded to the repeater for the viewer to connect.
Port 5500 needs to be forwarded to the repeater for InstantSupport, which seems to be working for you.

JohnHace · Post by **JohnHace** » 2010-04-28 23:05

I tried 555666 and nothing appeared.

I double checked the port forwarding and 5901 is set to that internal IP.

If you look at post

[topic=17805][/topic]

He is working with me on this and we set it just like you said.

Any ideas?

Thanks.

supercoe · Post by **supercoe** » 2010-04-28 23:10

On the computer running the repeater goto http://www.canyouseeme.org type in 5901 for the port and click "Check"

If it says "Success" then we'll know that the ports are forwarded correctly to the repeater and the problem must be on the Viewer side.

If it says "Error" your port forwarding isn't setup correctly or isn't working.

JohnHace · Post by **JohnHace** » 2010-04-29 13:32

I got "success" on both 5901 and 5500 from the repeater computer. So I guess it is at the viewer.

I have used uvnc SC on this computer in the past, but it is not running now. I have shut off Windows Firewall and Zone Alarm.

What else should I look for?

Thanks.

supercoe · Post by **supercoe** » 2010-04-29 14:50

The windows firewall doesn't block outgoing connections so you'll be ok with that on. I've seen ZoneAlarm continue to block things even when disabled, try uninstalling completely. Are you running an antivirus that has a firewall as well?

Something seems to be blocking the outgoing connection on the viewer computer.

B · Post by B » 2010-04-29 15:02

Other things I would try.

1. On the viewer machine, telnet to the repeater on both 5901 and 5500 and see what response, if any, you get.

2. Swap roles and see if you have the same problem when the current Viewer acts as the server, and vice versa.

It could be related to the previous installation of VNC, but what's odd is that the Viewer is thankfully a relatively standalone component. I usually get in trouble with previous installations of the server.

When you run the ChunkViewer, what does it show on the bottom after "Using:" ? (Feel free to censor the name/IP address.)

supercoe · Post by **supercoe** » 2010-04-29 15:34

B, good thinking, I was assuming that since InstantSupport was connecting to the repeater ChunkViewer would have been setup with the same repeater IP. I need to stop doing that.

If the ChunkViewer directory was moved before compiling it wouldn't have the correct repeater IP address.

Do as B suggested and make sure at the bottom of the ChunkViewer window "Using:...." has the correct IP.

If it does not:
Open the \Viewer\Bin\chunkviewer.ini file in notepad and modify:

Code: Select all

[Repeater]
Address=repeater.ip.here:5901

B · Post by B » 2010-04-29 16:16

And keep in mind that wherever you run ChunkViewer from, it has to have a "Bin" subdirectory containing that chunkviewer.ini file. I have successfully moved and copied that as a set. In other words, it's best to keep the "Viewer" directory intact at all times, even after compiling.

(I have multiple versions of the Viewer directory since I want to connect when local and when roaming, and my router doesn't automatically translate the public IP address back to the private one.)

supercoe, maybe the next version should make the viewer self-extracting to a temp directory each time it's run, just as the InstantSupport.exe does? That would mitigate some of this kind of thing.

JohnHace · Post by **JohnHace** » 2010-04-29 16:21

B wrote:Other things I would try.

1. On the viewer machine, telnet to the repeater on both 5901 and 5500 and see what response, if any, you get.

2. Swap roles and see if you have the same problem when the current Viewer acts as the server, and vice versa.

It could be related to the previous installation of VNC, but what's odd is that the Viewer is thankfully a relatively standalone component. I usually get in trouble with previous installations of the server.

When you run the ChunkViewer, what does it show on the bottom after "Using:" ? (Feel free to censor the name/IP address.)

1. I've never used telnet, so I'm note sure how to do that.

2. If I launch the InstantSupport from the viewer computer, I do see the number in the log, so we are connecting on 5500.

3. When I launch the ChunkViewer, the Using: shows the correct IP address with :5901 appended.

Thanks.

supercoe · Post by **supercoe** » 2010-04-29 16:23

Something has to be blocking the Viewers outgoing connection to the repeater then. Like I said, try uninstalling ZoneAlarm.

Good Luck!

JohnHace · Post by **JohnHace** » 2010-04-29 16:24

B wrote:And keep in mind that wherever you run ChunkViewer from, it has to have a "Bin" subdirectory containing that chunkviewer.ini file.

I'm launching from the original location of the Viewer folder and it does have the "Bin" subdirectory.

Thanks.

B · Post by B » 2010-04-29 16:27

And yet the viewer's attempt is never reflected in the repeater's log?

I was going to suggest looking at encryption issues next, but if the viewer's not making it as far as the repeater I'm stumped at the moment.

supercoe · Post by **supercoe** » 2010-04-29 16:52

And keep in mind that wherever you run ChunkViewer from, it has to have a "Bin" subdirectory containing that chunkviewer.ini file.

Not entirely true but recommended, the Viewer folder should never be moved or else compiling will fail. After compiling just the viewer folder can be copied to the technicians machines if you don't want to give them the full ChunkVNC package. Keep in mind that if you compile a InstantSupport with a different repeater IP or new encryption key the Viewer folder will have to be copied again.

I'm stumped at the moment.

Me to, has to be a firewall/configuration issue on that machine.

B · Post by B » 2010-04-29 17:24

But that's all I said, that "wherever you run Chunkviewer from" -- usually but NOT necessarily the "Viewer folder" -- expects to see an enclosed Bin folder.

In other words, you could have Chunkviewer.exe sitting in d:\Windows\foobar22 as long as there was a d:\Windows\foobar22\Bin folder with the INI file in it.

Again, I suggest that the newer versions make all that self-extracting. I think the overhead and other implications would be minimal, compared to the benefits. (Even better would be if the EXE managed to incorporate the settings and plugins without the need for external files at all, but I gather from both the original SC and these newer flavors that that's much easier said than done.)

JohnHace · Post by **JohnHace** » 2010-04-29 17:30

Suddenly the message has changed.

It now is saying Connection failed - Invalid Protocol !

Possible causes:

- You've forgotten to select a DSMPlugin and the Server uses a DSMPlugin
etc, etc.

Does this help?

Thanks.

supercoe · Post by **supercoe** » 2010-04-29 17:31

B,

Sorry, don't know where that came from?? I read it again and was like WTF.... At least I have you here for backup.

Once again, you're spot on.

Hmmm... self contained ChunkVNC, I like that idea but you're right with the easier said than done...

supercoe · Post by **supercoe** » 2010-04-29 17:50

JohnHace,

Since you're not seeing the Viewer ID show up in the repeater log I'm sure you're going to get all sorts of UltraVNC errors. Is it possible for you to copy the Viewer folder to a different machine and test if you can get an ID to show up in the Repeater log from there?

JohnHace · Post by **JohnHace** » 2010-04-29 18:19

supercoe wrote:JohnHace,

Since you're not seeing the Viewer ID show up in the repeater log I'm sure you're going to get all sorts of UltraVNC errors. Is it possible for you to copy the Viewer folder to a different machine and test if you can get an ID to show up in the Repeater log from there?

I tried that. Same result. However, the other computer is on the same network as the repeater. Does that have any effect?

Thanks.

B · Post by B » 2010-04-29 18:26

I tried that. Same result. However, the other computer is on the same network as the repeater. Does that have any effect?

It would probably pay to be a bit clearer about IP addresses involved. Are any of the ones you're seeing, in either the router logs or the VNC apps, private addresses?

Yes, the network absolutely has an effect -- when you're on the same private network as the repeater, you will likely need to use a different compilation of the viewer, or at least change that .txt file.

The only way you wouldn't have to do it is if your router automatically "hairpins" the request to the router's public IP address back in to the repeater's private address. Unless your repeater only has a public address. And DNS is an issue too if you're using names.

So it would help to diagram out what the networks and addressing are a bit more... Listing the IP addresses of the components will help; leave off the last octet (after the last period) for each one. This will indicate your general vicinity but won't necessarily tell anyone where you are.

And here's a much simpler test you should try. Run the InstantSupport.exe from the desired station. Then run the ChunkVNC viewer from that SAME STATION. Please let us know what happens.

JohnHace · Post by **JohnHace** » 2010-04-29 18:32

We just tried moving the repeater to another computer (on the same network as the first). CanYouSeeMe showed both ports open.

Same result.

I appreciate your persistence with me on this.

B · Post by B » 2010-04-29 19:28

I finally filled in my previous post above. Please refer.

JohnHace · Post by **JohnHace** » 2010-04-29 22:50

B wrote: And here's a much simpler test you should try. Run the InstantSupport.exe from the desired station. Then run the ChunkVNC viewer from that SAME STATION. Please let us know what happens.

I'm working on the first part, but just to let you know on the suggestion above, same result. (Failed to connect.)

B · Post by B » 2010-04-29 23:01

Well, I was thinking before that encryption would be the next suspect. So you're now regularly getting that "maybe it's a DSM issue" error message? Or do you mean that now you're getting a "failed to connect" message only, again?

It now is saying Connection failed - Invalid Protocol !

Possible causes:

- You've forgotten to select a DSMPlugin and the Server uses a DSMPlugin

BUT you still don't see ANY change in the repeater log when the ChunkViewer attempts to connect? Even from the same machine that is able to, at the same time, reach the repeater with InstantSupport ?

Makes no sense. I would want to see exactly what's in the repeater's settings.txt file, the ChunkVNC's chunkvnc.ini file, and the viewer's chunkviewer.ini file, as well as a complete map of ip addressing and routing. Some netstats and the aforementioned telnet probing wouldn't hurt either.

JohnHace · Post by **JohnHace** » 2010-04-30 13:59

B wrote:BUT you still don't see ANY change in the repeater log when the ChunkViewer attempts to connect? Even from the same machine that is able to, at the same time, reach the repeater with InstantSupport ?

Makes no sense. I would want to see exactly what's in the repeater's settings.txt file, the ChunkVNC's chunkvnc.ini file, and the viewer's chunkviewer.ini file, as well as a complete map of ip addressing and routing. Some netstats and the aforementioned telnet probing wouldn't hurt either.

That is correct. Nothing hits the log from any viewer.

Let me describe the networks here. We have two. One is a DSL, 68.16.235.xxx, the other is a Comcast cable, 173.15.219.xxx. We have tried repeaters on two different computers on the cable network. After port forwarding, CanYouSeeMe.org reported ports 5500 and 5901 were open. Then with a computer on the dsl, we launched the InstantSupport.exe. The number shows in the log at the repeater. From another computer on the dsl, we open the viewer. After a few seconds, we get the "Failed to connect" message. The other DSMPlugin message seemed sporadic. Nothing from the viewer shows in the repeater log. We also tried opening the viewer from a computer on the cable network, but as you said, that was likely to fail anyway.

Last attempt was to launch the viewer from the same computer running InstantSupport. Nothing happened at the repeater.

I have a zip file with the items you asked for, but I do not see a way to attach it here.

The contents of the chunkviewer.ini are:
[Repeater]
Address=173.15.219.xxx:5901

[ChunkViewer]
ListMax=10
List=664598|760005|915162|915162|915162|915162|915162|555666|555666|402650
Quality=3

The contents of the chunkvnc.ini are:
[Repeater]
Address=173.15.219.xxx:5500

[ChunkVNC]
Installed=0
Path=
ID=

The contents of the settings.txt are strange characters.

Let me know if I need to clarify any of this or add to it.

Thanks for helping.

B · Post by B » 2010-04-30 14:27

That looks right to me, but I'm not supercoe (the author).

The one distinction in my own current setup is that my ChunkVNC.ini file looks like:

Code: Select all

[Repeater]
Address=pconmynetwork.local:5500

[ChunkVNC]
Installed=1
Path=C:\Program Files (x86)\ChunkVNC
ID=xxxxxx

where xxxxxx is a static ID, as I've installed Chunk as a service (and it therefore created the permanent Program Files directory). Your InstantSupport would be running from a temp directory... but that's not the problem here, as it's your viewer that doesn't reach the repeater. (I'm also using non-standard port for part of the repeater.)

The only other thing you could show us is the beginning of your repeater log window after restarting the repeater and attempting both server and viewer connection. But I'm still stumped.

supercoe, it definitely would register a repeater hit even if the DSM stuff were completely screwed up, right?

It's possible the DSL ISP is filtering one port but not the other, but that's unlikely, particularly since it's an outbound attempt.

Did we already cover whether or not you've tried the viewer from additional locations besides those two networks? If you want, you could "PM" the repeater's full IP to supercoe or me and let us see if we can get any viewer to register in your repeater.

Edit: Here's another thought, as long as we're throwing darts. If you don't start the InstantSupport first, and just have the repeater running, and then try a viewer, does that register at the repeater? The crazy theory on this one is that there's an inbound connection limit somewhere (e.g., cable ISP). But like I said, crazy.

supercoe · Post by **supercoe** » 2010-04-30 14:54

Settings look good.
B, just so you're aware the repeater app stores its settings in binary so we'd need a screenshot of the settings window.

it definitely would register a repeater hit even if the DSM stuff were completely screwed up, right?

Correct, the connection to the repeater doesn't care much about protocol.

I'm willing to work with you over Gtalk if you want me to test your repeater. I'm really interested to find out what is going on here.

To make sure that the problem is with the connection to your repeater why don't you try a ready to run version of ChunkVNC:
http://www.walkernerds.com/chunkvnc/Chu ... _Swiss.zip

Just run InstantSupport, this will connect to a public repeater (thanks to Redge) and give you an ID, run the viewer with the ID and see if it works.

You can even do this on the same computer, I just got done trying it to make sure the swiss repeater was up and it worked great for me.

Good luck.

JohnHace · Post by **JohnHace** » 2010-04-30 17:49

supercoe wrote:Settings look good.
To make sure that the problem is with the connection to your repeater why don't you try a ready to run version of ChunkVNC:
http://www.walkernerds.com/chunkvnc/Chu ... _Swiss.zip

Just run InstantSupport, this will connect to a public repeater (thanks to Redge) and give you an ID, run the viewer with the ID and see if it works.

I downloaded this but when I extracted my AVG said the InstantSupport.exe has a Trojan horse Generic2_c.LEN.

Is it safe to ignore this?

Thanks.

supercoe · Post by **supercoe** » 2010-04-30 21:48

AVG sucks, it always detects AutoIT scripts (the programming language ChunkVNC was made in) as a virus. You can safely ignore the message.

I wonder if AVG is causing all your headaches, it wouldn't supprise me...

I'd suggest switching to Avira antivirus, much better protection, lighter on resources and still free (for home use).

JohnHace · Post by **JohnHace** » 2010-04-30 23:03

supercoe and b,

I owe you both a huge apology.

When I thought I uninstalled Zone Alarm, as the uninstall ended, the computer locked up. (A common occurance with this Win7 x64). When I rebooted, it seemed to be gone. I just found out it was still running.

I had to reinstall and then uninstall again and chunkviewer worked the first try.

I am so sorry I wasted so much of your time for my stupid mistake.

I really appreciate all of your effort.

UltraVNC

Failed to connect to server !

Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !

Re: Failed to connect to server !