[Martin Hescock]

Hi, I have been using my LX195 for a month or so but have never been able to achieve remote access. One of my computer has a XP Pro operating system and I use a DI 524 router with UPnP enabled. My ISP assures me that ports 80, 443, and 4125 are open and that was verified by two different techs at Wavecable. Although my router is UPnP, I have also set up port forwarding manually using advice from the forums. Port forwarding was set up and my server has been given a static IP. However, when I go to sites that check for open ports I find 80 and 443 are open but 4125 is not. On checking the WHS firewall, I found exceptions for 80 and 443 but not 4125. However I am not experienced with the WHS let alone server firewalls and wonder why would a server's software needing 4125 not have the firewall open to 4125 by default. So, I am assuming that I can not achieve remote access because of a blocked 4125. Of course I have done all the stuff with enabling remote access and configuring. I have the domain and can reach the domain using IE but when I click on log in I get IE can not find website. So any ideas why 4125 is blocked? Do I need to make an exception in the WHS firewall and if so why is there nothing in the forums on it?

[sallbee]

I don't think you need to be futzing around in the WHS firewall...the router is what will be opening the ports (or not!). I could be wrong.

I don't have that particular router so I'm not sure, but I just had an experience setting up a router/firewall using Untangle and ran into a similar problem and just posted about it on WGS a few minutes ago.

The WHS Settings> Remote Access test/repair were (IIRC) showing 80 and 443 as open, but blocked on 4125. However, the issue wasn't 4125 itself; in my case, the router was reserving the HTTPS port (443) for itself, for remote access/configuration to the router/firewall itself (not for access to WHS). I guess that was buggering up access to 4125 somehow (sort of like, not allowing it to pass the baton from 443 to 4125? I don't know, over my head).

In any event, in your router, try turning off remote configuration, and/or changing the HTTPS port for such access to something else (e.g., from 443 to 4433).

Good luck!

[Drashna Jaelre (WGS)]

4125 almost always shows up as blocked. Port scanning my network shows the same thing but I've definitely used the port.

[Martin Hescock]

sallbee, on 09 February 2010 - 03:50 AM, said:

I don't think you need to be futzing around in the WHS firewall...the router is what will be opening the ports (or not!). I could be wrong.

I don't have that particular router so I'm not sure, but I just had an experience setting up a router/firewall using Untangle and ran into a similar problem and just posted about it on WGS a few minutes ago.

The WHS Settings> Remote Access test/repair were (IIRC) showing 80 and 443 as open, but blocked on 4125. However, the issue wasn't 4125 itself; in my case, the router was reserving the HTTPS port (443) for itself, for remote access/configuration to the router/firewall itself (not for access to WHS). I guess that was buggering up access to 4125 somehow (sort of like, not allowing it to pass the baton from 443 to 4125? I don't know, over my head).

In any event, in your router, try turning off remote configuration, and/or changing the HTTPS port for such access to something else (e.g., from 443 to 4433).

Good luck!

[Martin Hescock]

Hi Sallbee,

I still have not achieved remote access. But I did find an excellent PDF titled "Windows Home Server Technical Brief Remote Access" wherein firewall issues both server and client are discussed. Also, since my router is more than six years old perhaps it is time to buy a new one so I have purchased a Linksys WRT54GL it is not new technology but certainly a tried and true performer. Maybe when I install it I will get lucky.

Marty