External Access Blocked?

[surfymark]

So I have been with Sky Broadband for about 6 months now.

I am using my own router - a Linksys WAG354G.

Back when I got Sky, I set up Port Forwarding to enable me to access my NAS externally.

This has been working great on two different ports (for two applications) ever since.

This morning it stopped working completely. I have LogMeIn so can log into a PC on the local network remotely. I have checked the router and it has not been updated and all the Port Forwarding rules etc are still the same.

If I put the external IP address it is reporting into my remote PC (along with the port number) it just says that Google cannot connect to it.

I have rebooted the router and the NAS twice each with no luck. I have also tried pinging the external IP address but got no response back (should I get a response back?)

Could Sky have blocked this some how? I can't really see how.

Internet access is fine from the local network at home and I have tried from a mobile data network as well as my work network so it is not the remote end.

Any ideas?

cheers
Mark

[Isitme]

Any chance your NAS IP address has changed?

I think you should get a ping response if you have 'Respond to Ping' ticked.

[Scubbie]

I've not heard of Sky blocking specific ports.

At the moment I have the Sky Netgear router connected and LogMeIn is working just fine this morning.

Have you tried checking the LogMeIn Wiki pages & help pages to ensure that they haven't changed a port number?

LogMeInWiki

Free - LogMeIn Help

[surfymark]

Any chance your NAS IP address has changed?

I think you should get a ping response if you have 'Respond to Ping' ticked.

Thanks for and good points.

I have just rechecked my NAS IP Address from my internal PC and no it hasn't changed (and I can log in to the same port using the internal IP address no problem).

I can't see a respond to ping tickbox but I can see a blocked services section which includes Ping as an option. No services are blocked currently.

cheers
Mark

[surfymark]

I've not heard of Sky blocking specific ports.

At the moment I have the Sky Netgear router connected and LogMeIn is working just fine this morning.

Have you tried checking the LogMeIn Wiki pages & help pages to ensure that they haven't changed a port number?

LogMeInWiki

Free - LogMeIn Help

I think you have the wrong end of the stick here. LogMeIn is working fine. I am trying to log into my NAS directly via a web browser (Chrome) using an IP address which has been working fine but is not now.

thanks
Mark

[Scubbie]

I think you have the wrong end of the stick here. LogMeIn is working fine. I am trying to log into my NAS directly via a web browser (Chrome) using an IP address which has been working fine but is not now.

Yeah I did, sorry.

Tom's post is probably identifying the right cause.

You may wish to set a fixed IP address for the NAS or use a service such as DynDNS.

I'm not sure how DynDNS would work with your NAS as I haven't much experience on them at present, but if it is an available option, it would help IMHO.

[Isitme]

All I can suggest is that you reset your router and set it up again to give access to your NAS. I don't think Sky will have anything to do with it really, it may be some update you have received that is causing the problem.

[surfymark]

Yeah I did, sorry.

Tom's post is probably identifying the right cause.

You may wish to set a fixed IP address for the NAS or use a service such as DynDNS.

I'm not sure how DynDNS would work with your NAS as I haven't much experience on them at present, but if it is an available option, it would help IMHO.

Thanks for this. Yes it is fixed on the NAS rather than dynamic but occasionally it does change for some reason.

I am also using a DDNS from no-ip.com but when I found this not working I switched over to the actual IP address to diagnose it.

If only Sky would give me a fixed IP address!

cheers
Mark

[surfymark]

All I can suggest is that you reset your router and set it up again to give access to your NAS. I don't think Sky will have anything to do with it really, it may be some update you have received that is causing the problem.

Hmm ok thanks. Took me ages to get it working before so a little reluctant to set it all up before but I guess that is what it will take.

cheers
Mark

[Scubbie]

I'm not familiar with no-ip.com, but the Sky routers, like most others, do support DynDNS, which is free.

There are issues with some of Sky's routers not correctly supporting some Ethernet printers, I wonder if this is a related issue? The problems have been fixed when an update was automatically applied to the router.

If you have a non-Sky router of your own, it might be worth extracting the password from the router (see this forum for more on this topic) and trying with that to see if it all works.

As for the IP address, there are issues with IP addresses being 'sticky' at the moment. The effect of this means that although Sky do not provide static addresses, once you have one, it can be very difficult to get it changed.

The fact that you IP address has been changed, suggests that your connection may have changed from PPPoA to MER.