Port Forwarding (again!)

PhilTilson · 03-27-2009, 04:22 PM

Hi!

A few weeks ago I posted a couple of questions relating to my situation in southern Spain, and got some good ideas from a number of people. Well, the situation has changed, and I have some new facilities - but still can't get things to work!

In order to avoid lots of messages backwards and forwards, I will try to explain as fully as possible what my setup is, and what the problem is. If I miss something, I'm sure someone will ask!

Following advice, I now have my own static IP. My 'ISP' across the valley said: "ok looks like I´ve done it you have a public IP of 89.xxx.xxx.226 going through to your ip 192.168.1.234, test it and let me know". You've heard of the expression 'the blind leading the blind'?

So my problem is this. If I ping my new IP address, I get a perfect response. DynDNS (and other WhoAmI-type sites) confirm that I am my new IP address. Normal internet access and e-mails work just fine. So far, so good.

However, despite having forwarded a number of different ports in my router in order to test things, using DynDNS's OpenPort tool tells me that virtually all of the ports - including 5900 - time out, and that typically this means that "traffic to that port is being actively blocked by either a firewall or your ISP". But at least one port - 5800 - IS apparently "open and accepting connections".

On the other hand, port 5500 says Connection Refused, which "typically indicates that there are no services available on that port, but that it is NOT being blocked by a firewall or your ISP".

Now, ALL of these ports have been forwarded in exactly the same way in my router, to the same machine (which is the one I am attempting to use TightVNC on) so I cannot see that this can be anything to do with my router. Are these ports being blocked by my ISP? (I'm not sure he'd know if I asked!) or am I missing something obvious here?

At this stage I'll take any help I can get! TIA.

Phil

**Jason09** · 03-28-2009, 12:37 PM

With Dydns's port checking tool, the ports will only show as open if the service on that port is running.

PhilTilson · 03-28-2009, 03:32 PM

Quote:

Originally Posted by Jason09

With Dydns's port checking tool, the ports will only show as open if the service on that port is running.

OK... (sorry, but I'm a bit out of my depth here!) but if it says: "89.xxx.xx.226:5800 is open and accepting connections. This indicates the port is not being blocked by either a firewall or your ISP and is currently operational", then this is presumably because TightVNC is running - so shouldn't I be able to connect to it?

I can't!

Phil

**Jason09** · 03-28-2009, 06:16 PM

I would say then it's not setup properly. Yes, that message does mean the ports is fully open.

PhilTilson · 03-29-2009, 02:50 AM

Quote:

Originally Posted by Jason09

I would say then it's not setup properly. Yes, that message does mean the ports is fully open.

That was my assumption. So where is the problem? As I said originally, the other ports that I have 'opened' have been set up in precisely the same way, yet 'time out' on a DynDNS test. If I disable the port forwarding on 5800, sure enough it times out too, so that would suggest that the setup is correct on the router.

However, TightVNC is using port 5900 (as evidenced by the information that appears in the window) and the service is running on the machine the port is mapped to, yet DynDNS times out on port 5900 whatever I do.

Could this port have been blocked somewhere else? And what about all the others? I'm sure the solution is simple - I just don't know what it is!!

Phil

**Jason09** · 03-29-2009, 10:03 AM

What software firewall are you using?

PhilTilson · 03-30-2009, 02:44 AM

Quote:

Originally Posted by Jason09

What software firewall are you using?

ZoneAlarm (free version). But TightVNC has been correctly registered there and as I can access the desired machines quite happily from within the internal network, I don't think this is the problem.

Phil

**Jason09** · 03-30-2009, 11:16 AM

Ok. I do find it odd then that the port is open, because ZA is a strict software firewall that can interfere in this type of situation. But I guess not now, though.

clyde123 · 03-30-2009, 12:49 PM

Turn off all firewalls for the purpose of checking, see if that makes any difference.

PhilTilson · 03-31-2009, 03:27 AM

Quote:

Originally Posted by clyde123

Turn off all firewalls for the purpose of checking, see if that makes any difference.

Unfortunately not!

I still get:

5500 Refused (not blocked, but no service active)
5800 Open
5900 Timed Out (actively blocked)

Frustrating! Just to confirm, ALL these ports are forwarded identically on my router.

Phil

clyde123 · 03-31-2009, 12:18 PM

Windows Firewall ? Easy to forget that one.

PhilTilson · 04-01-2009, 02:12 AM

Quote:

Originally Posted by clyde123

Windows Firewall ? Easy to forget that one.

Never touch it!!

**Jason09** · 04-01-2009, 11:17 AM

Quote:

Originally Posted by PhilTilson

Never touch it!!

I think it may be on by default.

PhilTilson · 04-02-2009, 02:27 AM

Quote:

Originally Posted by Jason09

I think it may be on by default.

The machine I am attempting to access is running Win2K, so it's not even on there! On all my other machines (and on that one) I run ZoneAlarm by default, and always disable Windows Firewall.

**Jason09** · 04-02-2009, 11:27 AM

ZA might be strict enough that disabling it may not be enough.

asgley · 04-02-2009, 06:07 PM

Hi Phil,

think we spoke before, glad to see you finally got something sorted =)

anyway, just because you can connect to a port doesnt mean your connecting to your pc.

it would look as though your still on an internal network 192 etc so its all down to port forwarding through the isp's router.
what i would be tempted to do is run something like wireshark on a pc of yours, set it up in the DMZ of your home router and then use an external addy to hit your machine on all the ports that should work and see if anything shows up, if it doesnt then go call your isp.

Note : use a machine you dont mind reinstalling afterwards, you would need to disable all the firewalls and stuff to be sure your getting the correct results

Asg

03-27-2009, 04:22 PM	#1 (permalink)
PhilTilson Registered User Join Date: Apr 2008 Posts: 14 OS: XP SP2	Port Forwarding (again!) Hi! A few weeks ago I posted a couple of questions relating to my situation in southern Spain, and got some good ideas from a number of people. Well, the situation has changed, and I have some new facilities - but still can't get things to work! In order to avoid lots of messages backwards and forwards, I will try to explain as fully as possible what my setup is, and what the problem is. If I miss something, I'm sure someone will ask! Following advice, I now have my own static IP. My 'ISP' across the valley said: "ok looks like I´ve done it you have a public IP of 89.xxx.xxx.226 going through to your ip 192.168.1.234, test it and let me know". You've heard of the expression 'the blind leading the blind'? So my problem is this. If I ping my new IP address, I get a perfect response. DynDNS (and other WhoAmI-type sites) confirm that I am my new IP address. Normal internet access and e-mails work just fine. So far, so good. However, despite having forwarded a number of different ports in my router in order to test things, using DynDNS's OpenPort tool tells me that virtually all of the ports - including 5900 - time out, and that typically this means that "traffic to that port is being actively blocked by either a firewall or your ISP". But at least one port - 5800 - IS apparently "open and accepting connections". On the other hand, port 5500 says Connection Refused, which "typically indicates that there are no services available on that port, but that it is NOT being blocked by a firewall or your ISP". Now, ALL of these ports have been forwarded in exactly the same way in my router, to the same machine (which is the one I am attempting to use TightVNC on) so I cannot see that this can be anything to do with my router. Are these ports being blocked by my ISP? (I'm not sure he'd know if I asked!) or am I missing something obvious here? At this stage I'll take any help I can get! TIA. Phil

03-28-2009, 12:37 PM	#2 (permalink)
Jason09 Moderator, Games Team Join Date: Jan 2009 Location: Near Washington, D.C. Posts: 2,314 OS: Windows XP Home Edition Service Pack 3 My System	Re: Port Forwarding (again!) With Dydns's port checking tool, the ports will only show as open if the service on that port is running. __________________ Gaming troubleshooting steps. Real peace cannot be found in what happens in Washington, D.C. Only God can give true peace to people.

03-28-2009, 06:16 PM	#4 (permalink)
Jason09 Moderator, Games Team Join Date: Jan 2009 Location: Near Washington, D.C. Posts: 2,314 OS: Windows XP Home Edition Service Pack 3 My System	Re: Port Forwarding (again!) I would say then it's not setup properly. Yes, that message does mean the ports is fully open. __________________ Gaming troubleshooting steps. Real peace cannot be found in what happens in Washington, D.C. Only God can give true peace to people.

03-29-2009, 10:03 AM	#6 (permalink)
Jason09 Moderator, Games Team Join Date: Jan 2009 Location: Near Washington, D.C. Posts: 2,314 OS: Windows XP Home Edition Service Pack 3 My System	Re: Port Forwarding (again!) What software firewall are you using? __________________ Gaming troubleshooting steps. Real peace cannot be found in what happens in Washington, D.C. Only God can give true peace to people.

03-30-2009, 11:16 AM	#8 (permalink)
Jason09 Moderator, Games Team Join Date: Jan 2009 Location: Near Washington, D.C. Posts: 2,314 OS: Windows XP Home Edition Service Pack 3 My System	Re: Port Forwarding (again!) Ok. I do find it odd then that the port is open, because ZA is a strict software firewall that can interfere in this type of situation. But I guess not now, though. __________________ Gaming troubleshooting steps. Real peace cannot be found in what happens in Washington, D.C. Only God can give true peace to people.

03-30-2009, 12:49 PM	#9 (permalink)
clyde123 Registered User Join Date: Apr 2008 Location: Glasgow Posts: 397 OS: xp sp2	Re: Port Forwarding (again!) Turn off all firewalls for the purpose of checking, see if that makes any difference.

03-31-2009, 12:18 PM	#11 (permalink)
clyde123 Registered User Join Date: Apr 2008 Location: Glasgow Posts: 397 OS: xp sp2	Re: Port Forwarding (again!) Windows Firewall ? Easy to forget that one.

04-02-2009, 11:27 AM	#15 (permalink)
Jason09 Moderator, Games Team Join Date: Jan 2009 Location: Near Washington, D.C. Posts: 2,314 OS: Windows XP Home Edition Service Pack 3 My System	Re: Port Forwarding (again!) ZA might be strict enough that disabling it may not be enough. __________________ Gaming troubleshooting steps. Real peace cannot be found in what happens in Washington, D.C. Only God can give true peace to people.

04-02-2009, 06:07 PM	#16 (permalink)
asgley Registered User Join Date: Feb 2009 Posts: 105 OS: xp32, vista64, gentoo, rhle4, rhel 5 64, centos 64, debian, solaris, 2k3, 2k8	Re: Port Forwarding (again!) Hi Phil, think we spoke before, glad to see you finally got something sorted =) anyway, just because you can connect to a port doesnt mean your connecting to your pc. it would look as though your still on an internal network 192 etc so its all down to port forwarding through the isp's router. what i would be tempted to do is run something like wireshark on a pc of yours, set it up in the DMZ of your home router and then use an external addy to hit your machine on all the ports that should work and see if anything shows up, if it doesnt then go call your isp. Note : use a machine you dont mind reinstalling afterwards, you would need to disable all the firewalls and stuff to be sure your getting the correct results Asg