Remote We Access help needed please

[Termin@l]

Hi all,

Some help before I tear my hair out will be greatly appreciated.

I have got a new HP Microserver running WHS 2011 and I have been trying to get the Remote Web Access up and running, everything else is going well.

The problem is that when running the auto setup within WHS 2011 it says that upnp is not turned on (it is) and that the router is not working. Having read countless threads on sky user and elsewhere I have not made any progress to solve the issue.

I have port forwarded 80, 443 and 4125 in the router settings for both inbound and outbound plus the same within the WHS 2011 firewall application.

When I ping the ports using shieldsup 80 is open, 443 and 4125 are stealthed and when using canyouseeme 80 is fine but 443 and 4125 the connection times out.

When I try to access xxxxxxxx.homeserver.com the connection times out wether I am on my LAN or on a separate Internet connection.

What is going on?

I have the sagem 2504 (grey dimpled router) and the server is connected via a wired connection. It has a static ip address assigned via the router settings as well as most of the other it devices in my house.

Any help will be greatly appreciated.

[Scubbie]

Have you tried accessing the server from outside you home network?

In most cases you will be unable to use the WAN IP Address from inside your home network with the Sky router.

Also it may pay you to forward the ports to the server, if you haven't already done so.

[Termin@l]

I have done both those things Scubbie, when accessing from outside the home network it times out. Why are the ports remaining in stealth when I have opened them all and linked them to the ip of the server?

[Isitme]

If you have a firewall enabled in the server, try putting the server address into the DMZ of the router. Even though you have opened them the two firewalls may be conflicting.

As Scubbie says, you will not be able to connect to the server from within your LAN using its external address as the default Sky routers do not support NAT Loopback.

[Termin@l]

So added the server ip to the DMZ and no change.

[Isitme]

Have you rebooted everything and crossed your fingers etc?

[Termin@l]

Nope but I'll be giving it a shot tomorrow

[Termin@l]

wait, 80 and 443 have just opened but 4125 is still on stealth.

[Termin@l]

but still cannot connect to server

[Termin@l]

I think it may of worked!!!

Yes it has, thankyou for the help......greatly appreciated