locked
Significance of port 4125 RRS feed

  • Question

  • Hello again everyone.

    I've had my server working now for a little over a month and so far I can't see how I was able to manager without it! Love it!

    Okay..but I have been having wireless router problems not forwarding ports and not being able to access my server from outside of my network (the web).

    It would randomly decide to not forward certain ports. I would go to www.canyouseeme.org and it would tell me what ports were opened or not.

    Often I could not bring up the http://myservername.homeserver.com from outside although I could access it using my IP address.
    www.canyouseeme.org would say that port 4125 was blocked even though it was opened in the router.

    Tonight I was fed up and hooked up a wired router and I am now using it to forward the ports and I am using the wireless router only as an access point.

    That seemed to clear up the problem of not being able to bring up the http://myservername.homeserver.com problem but surprisingly when I went
    into www.canyouseeme.org it STILL shows port 4125 is blocked.  I have verified it is opened in the wired router along with ports 443 and 80.

    Everything seems to be working and I could even access the WHS Console and log in the webpage.  So, why does it show port 4125 is blocked?
    Doesn't the server need this port opened?  I am confused...LOL..
    Monday, October 5, 2009 5:11 AM

All replies

  • The port can as well be blocked by your ISP or by some security appliance in the company from which you try to access the server.
    That you configured port forwarding therefore is not always identical with having it open.
    Port 4125 is only used for accessing the server from the Computers tab in the Remote Access website (to control the console from outside of your home).
    So as long as you dont try to use this feature, you will not experience any loss in functionality.
    Best greetings from Germany
    Olaf

    Monday, October 5, 2009 6:44 AM
    Moderator
  • Port 4125 will only appear as open when you initiate remote connection to the server console or a WHS client computer from from the WHS remote access webpage. 

    as  Olaf already mentioned, it's not relevant for accessing the server website. only when try to you connect to console (or a client computer) from the remote website port 4125 is required. 

    The fact that you can only access your server by IP address is a different (DNS) issue:

    Could be your server does not publish DNS info appropriately or client machine you are using to connect to the server is not appropriately configured, or if you recently configured remote access (or your external IP address has changed) it's possible the public DNS records are not yet up to date. 

    If you are trying to http://myservername.homeserver.com from within your homenetwork this may or may work (depends on your router, it should support internal loopback). If you are testing remote access from outside your network please try a computer on a different location. 
    Monday, October 5, 2009 9:24 AM
    Moderator
  • I had a similiar problem and then twigged that WHS (or Win2003) has an inbuilt firewall.  When I checked (Network Settings) I found that port 3389 (RDP) was set with a scope of Subnet only, and so would allow connection from inside my LAN but not from the Internet.  4125 is linked with 3389 and they share the same scope it seems, so when I changed the scope of 3389 I was about to see both ports open from a port checker site like https://www.grc.com/.

    Hope this helps,
    Alexander
    Thursday, October 8, 2009 1:37 AM
  • I had a similiar problem and then twigged that WHS (or Win2003) has an inbuilt firewall.  When I checked (Network Settings) I found that port 3389 (RDP) was set with a scope of Subnet only, and so would allow connection from inside my LAN but not from the Internet.  4125 is linked with 3389 and they share the same scope it seems, so when I changed the scope of 3389 I was about to see both ports open from a port checker site like https://www.grc.com/.

    Hope this helps,
    Alexander
    Port 3389 has nothing to do with Remote Access on WHS.  It's not used for Remote Web Workplace (which is what allows you to open the Console within the website from outside your LAN).  Port 3389 is Remote Desktop Connection, which is not the same thing.  Port 3389 on your server firewall should be set have the scope set to subnet only.
    Thursday, October 8, 2009 3:29 AM
    Moderator