Unable to use Chunk over internet

[manf0001]

Hello,

I have been using Chunk internally but I'm wanting to use it outside of my lan. I have port forward the ports 5901 and 443 to the server that the repeater is on. But I am still unable to access a remote machine over the internet.

When I've installed the instant support and obtain the number, I enter it into my viewer and it tries to connect it will just time out.

When I look at the repeater (the one included in the download) it does add the remote support number, showing that it does attempt to connect. If I work on the LAN its totally fine.

I've even tried moving the repeater to another server and changed the port forwarding to the new server, still does not connect over internet, I even tried changing the 443 port to something else in the repeater and recompiled the support but again still unable to connect over the internet.

Other than Port 443 and 5901, would there be any other ports that need to be opened or forward? I'm not using a basic home router, I'm using a Astaro Security Gateway Now known as Sophos UTM (Unified threat Management)

Thanks

Update So I've started everything from scratch.

Reinstalled the Repeater using ports 5901 and 55000 (because the server I want to use it on already uses port 443)
Removed and reinstalled Chunk and recompiled using my static IP for the WAN and my server's IP for the LAN using ports 5901 and 55000
I also setup port forwarding for the two ports to point to my server that the repeater sits on
I run the instant support file inside my network on a test machine and I can connect fine.
I run the instant support on a machine outside of my network and it shows the support number but after about 1 min or so, I get an error saying "connection to the repeater was not possible"

SO is there any trick to using another port other than 443

I have even opened up my firewall to allow everything from the outside, but still no go

[supercoe]

Please overview the installation guide: http://www.chunkvnc.com/installationguide.html

Did you test that your port forwarding is actually working?
This tool will tell you the port is open when the repeater is running and port forwarding has been done correctly:
http://www.yougetsignal.com/tools/open-ports/


You say it works internally fine but not externally, this is one more thing that points to your port forwarding not being correct.


You should be able to use any port you wish for the server but 443 is recommended as it is the only way to support HTTP proxies.

Good luck!

[manf0001]

Yep, I've gone through the instructions a hundred times... and yes I have verified that my ports are open...

I know I'm probably missing something very simple... back to the drawing board...

[supercoe]

Check that the ports say closed when you don't have the repeater running.
It doesn't make much sense to me that the ports could be forwarded to the repeater successfully and it wouldn't work...

Keep me posted on what you find, this is an interesting one.

Good luck!

[manf0001]

Thanks.. I think I'm going to need the luck..

so when I closed the repeater and tested my ports 5901 and 55000 it says closed. When I open the repeater and test the ports again it says open.

One thing that I did notice, maybe it was there lastnight but too tired to see it. is that when I reopened my repeater it goes through binding the two ports and each port says succeded But the last line show "Reading Proxy settings erro"

But I will keep you posted. the fun life of a network admin... hahaha

[supercoe]

When InstantSupport or ChunkViewer is run it opens a connection to the repeater just to check it's existence, when it does this you will see "Writing protocol version erro".

If you're saying that you start the repeater and don't have ChunkViewer or InstantSupport running then something else is trying to make a TCP connection to the repeater.

I'm wondering if your security gateway is doing some kind of packet inspection? Maybe it doesn't like what it sees?

"the fun life of a network admin" lol tell me about it, at least when you crack this one it will feel like a great accomplishment!


EDIT: wrong error message, corrected

[manf0001]

Ok status Update..

It turns out that it's not my security gateway.

1) I installed a cheap dlink router and still could not get two of my remote computers connected to my repeater.
2) I accessed a third PC and I was able to connect to it.
3) I put my Main router back on and tried to access that third PC out on the internet and it connected fine.
4) A buddy has chunk on his PC so I tried to use it on the two remote PCs that I couldn't get to and I still couldn't get to it with his setup of chunk, but I could on the third PC.

SO I believe that with the two sites I can't access has to do with their routers, it would make sense if both routers were the same, but it's not. One network uses a CISCO small business router while the other uses a consumer grade Buffalo router.

Almost solved it just have to figure out how I can get access to those two PCs.

at least I have RDP access to them but I'm wanting to close RDP access.

Thanks

[supercoe]

What do you mean "a buddy has chunk on his pc" ?

Do you mean he is running a repeater and you tried to compile using his repeaters address?

Can you be more specific as to when and where you are running the Viewer/InstantSupport/Repeater?

Please post IPs/DNS names you are compiling with, just comment out part of the address for security purposes.

I'd like it if you could try a repeater running somewhere else that we know is setup and working.

You could test with the public repeaters from the RTR version (keep in mind I haven't tested these in a long time they may be down)

Swiss
Using repeater03.ultravnc.info located in Switzerland.
http://www.chunkvnc.com/ChunkVNC_3_2_RTR_Swiss.zip
MD5: 345cc813be758473f022828583fbbb50

German
Using repeater02.ultravnc.info located in Germany.
http://www.chunkvnc.com/ChunkVNC_3_2_RTR_Germany.zip
MD5: bfe63b6ebf252c44c3fef0fe32124e25

[manf0001]

Sorry.

My buddy runs a repeater on his server (72.38.x.x)

I installed his viewer on my computer (64.140.x.x) and his instant support program on a PC at 72.38.x.x it would not allow me to connect.

But If I installed the same instant support on another PC located at 72.38.x.x it worked fine.

So Switch to My own repeater and viewer at 64.140.x.x and install my instant support at 72.38.x.x again would not connect.

I installed my instant support on a PC at 72.38.x.x I could connect to it.

There is another location that I can't remote into but unfortunately I've lost access and don't know it's network as that location uses a dynamic IP

I tried downloading those two links and it said I could not download them

[supercoe]

Sorry, I didn't mean for you to try the RTR version, I meant for you to try the repeaters themselves and just copied to much.

repeater03.ultravnc.info
repeater02.ultravnc.info

[supercoe]

It would be useful if you were more specific, this is still vague information "would not connect".

Try this format:
Running repeater on 72.38.1.1 ports 5901, 443
InstantSupport on 64.140.1.1, ID:123456, repeater log shows server 123456 connected
Chunkviewer on 64.140.1.2, ID:123456, repeater log shows viewer 123456 connected

[manf0001]

OK So here are the log files, one pair is using my friends Repeater, one that works and one that does not work, the other Pair is from my repeater

Connects

Running repeater on 72.38.186.1 ports 5901, 55000
InstantSupport on 72.38.103.1, ID:810140,
Chunkviewer on 64.140.119.1, ID:810140, repeater log shows viewer 810140 connected Contents of Log Below

2013/4/6 8:33:35 2013/4/6 8:33:47 2013/4/6 8:33:47 2013/4/6 8:34:10 Transmitted: 75k
2013/4/6 8:34:12 2013/4/6 8:34:16 Transmitted: 0k
2013/4/6 8:36:21 2013/4/6 8:36:21 Transmitted: 0k

Does Not Connect

Running repeater on 72.38.186.1 ports 5901, 55000
InstantSupport on 72.38.138.1, ID:773436,
Chunkviewer on 64.140.119.1, ID:773436, repeater log shows viewer 773436

2013/4/6 8:36:26 2013/4/6 8:42:11 Transmitted: 0k This is the only line in the log the below is what the viewer displays after a few mins of not being able to connect.


Viewer Times out on Negotiate Protocol version saying: Connection Failed-End of Stream, possible causes: Another user is already listening on this ID, or Bad Connection


Does Not Connect

Running repeater on 64.140.119.1 ports 5901, 55000
InstantSupport on 72.38.138.1, ID:835518,
Chunkviewer on 64.140.119.1, ID:835518, repeater log shows viewer 835518 (Viewer is pointing to the repeater on internal network (192.168.2.11 where repeater is)

2013/4/6 8:51:11 2013/4/6 8:56:52 Transmitted: 0k This is the only line in the log the below is what the viewer displays after a few mins of not being able to connect.

Viewer Times out on Negotiate Protocol version saying: Connection Failed-End of Stream, possible causes: Another user is already listening on this ID, or Bad Connection

Connects
Running repeater on 64.140.119.1 ports 5901, 55000
InstantSupport on 72.38.103.1, ID:774484,
Chunkviewer on 64.140.119.1, ID:774484, repeater log shows viewer 774484 (Viewer is pointing to the repeater on internal network (192.168.2.11 where repeater is)

2013/4/6 9:3:27 2013/4/6 9:3:42 2013/4/6 9:3:42 2013/4/6 9:3:52 Transmitted: 69k
2013/4/6 9:3:55 2013/4/6 9:3:59 Transmitted: 0k


All of these tests were using Chunk 3.3.1 as is.

I then decided to upgrade the UVNC files to the latest, and recompile chunk using my repeater and it started working fine on the other machines. I Can't explain it, because I was using the same files in chunk before I started testing over the internet.

[supercoe]

Which files did you update and to what version?
I wonder if there is a bug with server port numbers that high?

[manf0001]

I updated the winvnc ver 1.1.8.8 and the same with the vncviewer

I pulled the two files from bin x86 1180 xp-win7 1.1.8.0 located on the UVNC download site. Even though it has both 32 and 64 bit it seems that the 32 bit version works well on the 64 bit platforms.

One other thing I've found that I like with this new version of vnc, is that when you install the support as a service, it will automatically try to reconnect instead of closing it down, and you having to relaunch the viewer.

[supercoe]

Glad you sorted it out, still doesn't make sense as to what was going on.
Anyways good luck!

[manf0001]

Ya I agree, it was very odd I don't understand it either. But oh well.

thanks