Port Forwarding Error Windows Home Server
Contents |
Latest News 22 By Philip Churchill on June 28th, 2007 What Ports do I forward in my Router for WHS? Some of you have emailed asking which ports you need to forward windows home server 2011 port forwarding on your router for Windows Home Server. So here we go: The first
What Is My Ip
port to forward to your WHS is the "standard web traffic" (HTTP) port 80, although this is optional. If you don't forward it, you can access your WHS machine using https://
instead of http:// Next is the "secure http web traffic" (HTTPS) port 443. Then Remote Web Workplace (RWW) which uses port 4125. This enables you to access the web interface feature. Web Interface Feature Finally the Remote Desktop Protocol (RDP) port 3389. This allows you to use "Remote Desktop Connection" to connect to your Windows Home Server desktop. Windows Home Server Desktop All ports are TCP only - UDP is NOT necessary. Share this WHS Article with Others: | | Remotely • Tutorial • Windows Home Server Comments (22) Trackback URL | Comments RSS Feed Daniel Keller says: June 29, 2007 at 1:39 PM Hello Philip Personally I dont expose my WHS directly to the Internet since I have all my personal data on it. I use the free version of Hamachi so I can access from my Notebook trought a secured VPN Tunnel and I have more controll who connects to the server. (user restrictions) Another very secure connection is LogMeIn Free, there you have options like one time password and this way you can have Desktop Access to your server. Just some ideas from me….have a great day Reply Simon Smith says: June 29, 2007 at 9:00 PM Are you sure about port 3389? My router only port forwards 443 and 4125 and I have remote accessed PCs on my network via WHS. (port 80 not forwarded toWHS as I also run a web server). Reply Philip Churchill says: June 29, 2007 at 9:26 PM Without port 3389 being forwarded you will still be able connect via the "Remote Desktop Connection" using: The servers name, in my case "SERVER" or your Internal IP address e.g. 192.168.1.XXX So when connecting from within the local network all is fine. But you will not be able to connect via the "Remote Desktop ConnectSign Up All Content All Content This Topic This Forum Advanced Search Browse Forums Downloads Guidelines Staff Online Users More Activity All Activity My Activity Streams Unread Content Content I Started Search More Store Orders Manage Purchases My Details Personal Information Addresses Account Credit Alternative Contacts More Support Support More We Got Served More More All Activity Home Home Servers & NAS Windows Home Server & Windows Server Windows Home Server 2011 Remote Access Whs 2011 Remote Web Access Problem http://www.mswhs.com/2007/06/what-ports-do-i-forward-in-my-router-for-whs/ Sign in to follow this Followers 1 Whs 2011 Remote Web Access Problem Started by pfisher, February 27, 2013 11 posts in this topic pfisher 0 Member Members 0 14 posts Posted February 27, 2013 I have a WNDR 3800 router. The router has the latest firmware. I am sure this problem is NOT a strange problem to most 3700 and http://forum.wegotserved.com/index.php?/topic/27608-whs-2011-remote-web-access-problem/ 3800 routers. For some reason, I am having problems with successfully configuring my router to WHS 2011. This problem is about WHS 2011. Let me explain, I have a WHS V1 server and I have WHS 2011 server. My router configures and works fine on the WHS V1 server. I don't encounter any configuration or setup problems on the WHS V1. However, on the WHS 2011, I encounter configuration/setup issues. When I go to setup (remote access) my router, WHS 2011 starts the configuration. It will attempt to configure the router to work with WHS 2011. During this process before it completes the setup, I get an error message about 443 is blocked. YES, I have the 80, 443, and 4125 set to the WHS 2011 IP address. YES, I have the WHS 2011 IP address reserved. YES, firewall is turned off on the WHS 2011. NO, I don't have any antivirus programs running or installed on the WHS 2011 YES, my router works fine otherwise. YES, UPnP is enabled. (Even if I disable UPnP, I still get an error messa
FACEBOOK GET UPDATES BY EMAIL Enter your email below to get exclusive access to our best articles and tips before everybody else. RSS ALL ARTICLES FEATURES ONLY TRIVIA Search How-To Geek Setup Remote Access in Windows Home Server http://www.howtogeek.com/howto/14123/setup-remote-access-in-windows-home-server/ One of the many awesome features of Windows Home Server, is the ability to access your server and other computers on your network remotely. Today we show you the steps to enable Remote Access to your home server from anywhere you have an Internet connection. Remote Access in Windows Home Server has a lot of great features like uploading and downloading files from shared folders, accessing files from machines on your network, and controling machines remotely (on supported OS port forwarding versions). Here we take a look at the basics of setting it up, choosing a domain name, and verifying you can connect remotely. Setup Remote Access in Windows Home Server Open the Windows Home Server Console and click on Settings. Next select Remote Access, it is off by default, just click the button to turn it on. Wait while your router is configured for remote access, when it’s complete click Next. Notice that it will enable UPnP, if you windows home server don’t wish to have that enabled, you can manually forward the correct ports. If you have any problems with the router being automatically configured, we’ll be taking a look at a more detailed troubleshooting guide in the future. The router is successfully configured, and we can continue to the next process of configuring our domain name. The Domain Name Setup Wizard will start. Notice you will need a Windows Live ID to set it up –which is typically your hotmail address. If you don’t already have one, you can get one here. Type in your Live ID email address and password and click Next… Agree to the Home Server Privacy Statement and the Live Custom Domains Addendum. If you’re concerned about privacy and want to learn more about the domain addendum, make sure to read about it before agreeing. There is nothing abnormal to point out about either statement, but if this is your first time setting it up, it’s good to review the information. Now choose a name for the domain. You should select something that is easy to remember and identifies your home server. The name can contain up to 63 characters, numbers, letters, and hyphens…and must begin and end with a letter or number. When you have the name figured out click the Confirm button. Note: You can only register one domain name per Live ID. If the name isn’t al