Home Server Setup

pioneer2000 · 4 Nov 2008 at 00:22

Trying to get windows home server working over the internet- It won't connect though...

Ports are forwarded and firewall is ok- seems port 4125 is closed however. Not sure if it's Pipex that are blocking it.

Anyway to get this working?

Is rather annoying!

Zarf · 4 Nov 2008 at 05:11

Are ports 80 and 443 also forwarded to your WHS?
Don't worry about Pipex, they arn't blocking anything. WHS apparently keeps 4125 closed until RWW needs it to open.

pioneer2000 · 4 Nov 2008 at 10:55

I have forwarded 80, 443 and 4125 to the IP of my WHS.

When I run the remote access setup thing in WHS console it shows explanation marks next to the last 2 items (access whs homepage and remote access i think!).

PhillyDee · 4 Nov 2008 at 20:56

Enable uPNP on your router when in the box, then tell it to fix it. Might sort it.

rah^ · 4 Nov 2008 at 21:50

as a strange question have u gone to system properties and under remote tab enabled it ?
probably totally pointless post but mm

pioneer2000 · 4 Nov 2008 at 23:03

Remote desktop is enabled and I have tried with upnp on and off.

From what I understand it maybe because my router (Netgear 834pn) doesnt support loopback?

hmmm it works when accessing from another house if I type the WAN IP address in IE- but if I type the .homeserver.com address it does not.... any ideas?

Skidilliplop · 5 Nov 2008 at 09:26

pioneer2000 said:
Remote desktop is enabled and I have tried with upnp on and off.

From what I understand it maybe because my router (Netgear 834pn) doesnt support loopback?

hmmm it works when accessing from another house if I type the WAN IP address in IE- but if I type the .homeserver.com address it does not.... any ideas?

^ that there be a DNS issue not a port forwarding issue.