Unable To Open Port 4125
Go to Virtual servers and set your router accordingly as in the piture except inserting the IP address of your server. I did read your post here a few weeks ago. Example. I was hoping a simple firewall rule in the router may be the culprit, but can't figure what it may be. Source
Sign in here. 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 a few I was fairly diligent in making sure everything would be accessible on the server side...
Maybe. Only Utorrent Traffic Through Openvpn By surya kumar · Posted 15 hours ago I've been doing that every time, because the data doesn't go through openvpn.exe. It gets annoying having to Logged Print Pages:  « previous next » D-Link Forums > D-Link Xtreme N (Platinum Products) > DIR-655 > cant forward ports 443 or 4125 SMF 2.0.12 | SMF ©
I've changed the HTTP and HTTPS ports to different ports in the WHS2011 IIS and then forwarded those ports to my WHS2011 so I can use both servers via web access. A year ago on WHSv1 I did have remote access configured properly and working. Home Help Search Login Register D-Link Forums > D-Link Xtreme N (Platinum Products) > DIR-655 > cant forward ports 443 or 4125 « previous next » Pages:  Print Author Topic: 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
All of my necessary ports are open, there are sometimes when I try to connect that it says this computer can't connect, or sometimes when I change some settings around it My ISP is Cox and they do block port 80 (HTTP) but WHS uses HTTPS on port 443, which Cox has told me they do not block.I'm using this port cheecker Chat with us Why are faster speeds not available? We will not share your information.
To use WHS Ports, you must first remove connectToCiscoAP from the application list of Cisco_AP_ATT. On the firewall do a port forwarding on port 3389 to the server (internal ip address).when you think you have it right on the firewall you can use www.grc.com , go Go to Solution. You have to block www.green-it-software.com or www.homeserversoftware.com on your server and then delete the new version from the registry HKEY_LOCAL_MACHINE\SOFTWARE\AxoNet Software GmbH\LightsOut\UpdateVersion.
IT STINKS!!!! It's customary to create an A record in your public DNS zone with your site static IP, something like remote.mycompany.com so that you and your remote users don't have to remember Message 7 of 37 (11,092 Views) 0 Kudos Reply Reply SomeJoe7777 Expert Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content http://cleantechinnvest.com/unable-to/unable-to-open-tcp-ip-port.html I talked to Cox support weeks ago, and before I bought the new router (DIR-655).
I guess that was buggering up access to 4125 somehow (sort of like, not allowing it to pass the baton from 443 to 4125? There is a small section that is specific to WHS 2011 IIS in this WHS 2011 unleashed e-book, which I have.My next step is to attempt this as suggested. I could be wrong.
Sorry to say but you're busted, you can't open ANY ports on that firmware, I have the same problem. :-( Logged bananaman Level 2 Member Posts: 55 Re: cant forward ports
To access your WHS site you could use your external address followed by the port number such as https://10.1.5.6:443 where 10.1.5.6 is your external IP Address. It seems that this product is in never neverland between real HP servers and HP PCs. Good luck! I checked the windows firewall on the server and enabled RDP connections on 3389, but still nothing.
Reset my router back to default settings3. Reply Philip Churchill says: June 29, 2007 at 10:19 PM Thanks to Daniel Keller for the details on the two virtual private networking (VPN) applications. See the following article:http://forum.wegotserved.com/index.php/tutorials/article/29-set-up-alternate-ports-for-windows-home-... Check This Out I get the router failed picture as I posted above.
it says they are closed.I'm setting up a Windows Home Server if that makes any difference. 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). Edited by st3lvio, 12 May 2011 - 08:21 AM.