locked
Remote and local http/https/rd access. RRS feed

  • Question

  • I've just installed my homeserver.

    When using the console to set up remote access it fails on the router setup for remote access.

    I have forwarded the relevant ports - tested them using shields up - and in the end reconfigured another machine to the same address and wrote a program to open those ports for testing and they are definatly open and forwarding to the right ip adress. 

     

    Interestingly if I access the machine on the local network with http://servername/home - I get the welcome picture and when I click 'log on' I get  diverted to http://servername/home/Default.aspx  and the 'Internet explorer cannot display the web page' message

     

    if i use https://servername/remote I get the 'I'E can't display the web page'

     

    http://192.168.0.18 also fails -  and only the /home seems to show anything.

     

    So it doesnt appear to be remote access via the router - but even access locally doesn't work -

     

    Yes I have got a user setup who is allowed remote access!

     

    Has anyone got  any suggestions?

     

    This is driving me slightly crazy..

    Saturday, February 9, 2008 5:11 PM

Answers

  • I was the first person who had posted saying I had the same problem as rich-navsys.

    I just followed the steps that rich-navsys laid out and it solved my problem. The steps were:
    1) Open the WHS Console
    2) Navigate to Settings->Remote Access
    3) Under the Domain Name section choose Unconfigure
    4) Under Web Site Connectivity choose Turn Off
    5) Reboot server
    6) Re-open WHS Console
    7) Navigate to Settings->Remote Access
    8) Under Web Site Connectivity choose Turn On
    9) Under Domain Name choose Setup
    10) Configure a different domain from the one you had before
    11) Under the status it should say Testing then Working
    12) You can then click OK or Apply to save your settings

    What I was able to do afterward was unconfigure the new domain name and go back to my old one and everything still worked.

    Thanks Rich-navsys
    Sunday, March 2, 2008 8:26 PM

All replies

  • I made a mistake in the title - I can get in with RD directly to the server - its the http/https stuff that doesnt work internally or externally -

     

    The only page that can be displayed is the /home page - even going to the root at http:/192.168.0.18 just redirect me to http://192.168.0.18/home/default.aspx?gotodefault=true which gves the IE cannot display mesage.

     

    It's the same externally - only http://servername.homeserver.com/home works - pressing the login gives a connection interrupted error.

     

    So its the server that seems to have a probelm - any ideas anyone?

     

    Saturday, February 9, 2008 6:12 PM
  • I'm having the exact same problem.

     

    I can RD to the server from within the home network. From there I try to do a http://localhost from a browser on the server machine and I get the same error message.

     

    I've run the Connector Troubleshooter software in advanced mode and it comes up with no errors. Is something screwed up with the IIS configuration or the web permissions or something.

     

    I'm definitely stumped at this point.

     

    Saturday, February 9, 2008 8:37 PM
  • Try Eric's "Changing the web server ports on your HP MediaSmart Server"

    This is his own Web Site running off his HP MediaSmart.

     

    http://www.myhomeserver.com/?page_id=23

     

    or

     

    http://www.myhomeserver.com/

     

    Good Luck and Let us know how you make out............and don't forget to Thank Eric if everything works out.

     

    Saturday, February 9, 2008 11:48 PM
  •  

    Sadly that site is dealing with external access - My ISP doesn't block any ports so there is no need to change them. The problem is that I can't even access the web server correctly from the local network side - just the /home page. So port 80 is working - its just the server gives up or drops the connection when trying to serve up any other page.

     

    So I don't even get as far as step one of his trouble shoting guide - I can't even get in locally!

     

     

    I can't see anything wrong with the IIS settings - I'd put off looking at them but they appear ok - this is a completely new out of the box machine we are talking about here. - Nothing more complicated had been done than entering a few users and granting remote access rights where applicable. So I would assume I wouldn't need to be mucking around with these settings on a so called 'Home' server.

     

    My next option is to wipe the machine and start again. - Not something I really want to do - but it's probably what MS tech support would tell me to do!

     

     

    Sunday, February 10, 2008 12:12 AM
  • Rich

     

    Exactly the same problem here although at one point I think it was working (but was that on the 120 day trial version before I installed the full version?) but never had external access working! Does anyone know what services are meant to be runnng on WHS to allow remote access. Remote desktop connection works fine.

     

    Phil

    Sunday, February 10, 2008 1:15 PM
  • Rich

     

    1. What exactly is the configuration of you WHS is it one that you built yourself?
    2. Are you using "Static IP" on your home server?
    3. Did you change any "Firewal" settings on you WHS ?
    4. Any ADD-IN or Software installed on your WHS?

    Have you tried to access your Webpagees directly from the WHS ?

     

     

     

     

    Sunday, February 10, 2008 1:38 PM
  • Rouza

     

    Your question was not addressed to me but here is my situation:

     

    1. Made by myself. 2 x WD 500GB drives, Dlink GB NIC and a Athlon 2400+ processor

    2. Static IP 192.168.2.100 - Can access the Welcome page at either this address or via the WHS name.

    3. No changes to any firewall settings

    4. No software installed after installation other than a Windows update.

     

    Tried accessing webpages from WHS with exactly the seme results!

     

    Phil

     

    Sunday, February 10, 2008 1:47 PM
  •  PhilipJH wrote:

    Rouza

     

    Your question was not addressed to me but here is my situation:

     

    1. Made by myself. 2 x WD 500GB drives, Dlink GB NIC and a Athlon 2400+ processor

    2. Static IP 192.168.2.100 - Can access the Welcome page at either this address or via the WHS name.

    3. No changes to any firewall settings

    4. No software installed after installation other than a Windows update.

     

    Tried accessing webpages from WHS with exactly the seme results!

     

    Phil

     

     

    Try  removing the static IP

     

    Reconfigure  you port fowarding as needed

     

    Test again from the WHS

    Sunday, February 10, 2008 1:58 PM
  • Removed static IP and rebooted the WHS. WHS machine picked up the same IP from DHCP server after reeboot.

     

    Exactly the same symptome - can access "Windoes Home Server Website" with Internet Explorer but as soon as I click

    "Logon" I receive the "Internet Explorer cannot display the webpage" error message.

     

    Phil

    Sunday, February 10, 2008 2:19 PM
  • Philip

     

    I would like you to check a setting in "IIS"

     

    I need you to check the "Permissions" on the "Remote site"  under the "Default Web Sites"

     

    If we change anything here we can cause more trouble

     

     

    all Programs

    Administrativee tools

    collaspe servername(Local Computer)

    Collaspe " Web Sites"

    Colaspe Default Web Site"

    right click on "Remote" select "Properties"

    Click on the " Virtual Directory" Tab

     

    Let me know whats check off in the "Local Path" section on the left side

     

    "Script Source Access"

    "Read"

    "Write"

    "Directory Browsing"

     

    By default the correct setting should be selected but just checking.

     

    Again please do not change anything at this point I do not want to cause any more damage to you installation.

     

     

     

     

     

     

    Sunday, February 10, 2008 3:12 PM
  • c:\inetpub\remote

     

    Boxes checked are:

    "Read"

    "Log Visits"

     

    Drop down settings:

    Default Application

    Scripts Only

    Remote AccessApp Pool

     

    Phil

     

    Sunday, February 10, 2008 3:28 PM
  • Philip

    Thanks

     

    Now Last area to check follow the same steps as before and now select the "Directory Security"

     

    under "Authentication and Access Control"  click on "Edit"

     

    The setting should be

     

    "Allow Annoyomus Access" should be selected (checked) and the username shoud be "IUSR_Server" Server = the name of your server and you see a password entered as ".............."

     

    So if you server name is WHSBOX the username should read "IUSR_WHSBOX"

     

     

     

    also check

    all Programs

    Administrativee tools

    collaspe servername(Local Computer)

    Collaspe " Web Sites"

     Default Web Site"

    right click on "default Web Sites" select "Properties"

    see if there is an entry  on the "Web Site" tab for SSL Port . Should be "443"

     

    Sunday, February 10, 2008 3:51 PM
  •  

    Rouza

     

    Thanks for your continuing support.

     

    All checks out as you suggested above on both areas!

     

    I feel a reinstall coming on?

     

    Phil

    Sunday, February 10, 2008 6:52 PM
  •  PhilipJH wrote:

     

    Rouza

     

    Thanks for your continuing support.

     

    All checks out as you suggested above on both areas!

     

    I feel a reinstall coming on?

     

    Phil

     

    I am feeling it too!!!

     

    Its a shame that the WHS team does not weigh in on this.

     

    As I understand  it

     

    http://server  should resolve to https://server/home   by default and from what the original poster said this does not seem to happen

     

    However if you type http://server/home it will take you to http://server/home not https://server/home  as was reported in the original post.

     

     

    IF all the settings are as reported then there is a deeper error somewhere and it will involve someone with the coding knowledge to see where the error is.

     

    I supposed reinstalling  should fix it but you might have a bad DVD.

     

    On another thread someone suggested installing net framework 3.0 caused problems with remote websites.

     

    Anyway reinstalling might be your next best step.

     

    Wait  if you can hopefully the WHS team may get involved.

    Sunday, February 10, 2008 7:59 PM
  • Sorry - took some time out to sort out someone elses network!

     

    1) Its a tranquil PC T2-WHS-A3 straight out of the box 2x500mb, 1Gb ram ( http://www.tranquilpc-shop.co.uk/acatalog/T2_WHS_A3.html#a54 )

     

    2 Nope

    3 Nope

    4) Nope

     

    5) Yep - RD'ing directly and running its inbuilt browser it can only access http://snuggles/home not - http://snuggles or https://snuggles/remote

    - a bit weird it can't even see itself.

     

    I've looked at your later posts and all seems to be correct there too.

     

    Ok I own up - the computers name is snuggles.....

    Sunday, February 10, 2008 8:07 PM
  •  Rich-navsys wrote:

    Sorry - took some time out to sort out someone elses network!

     

    1) Its a tranquil PC T2-WHS-A3 straight out of the box 2x500mb, 1Gb ram ( http://www.tranquilpc-shop.co.uk/acatalog/T2_WHS_A3.html#a54 )

     

    2 Nope

    3 Nope

    4) Nope

     

    5) Yep - RD'ing directly and running its inbuilt browser it can only access http://snuggles/home not - http://snuggles or https://snuggles/remote

    - a bit weird it can't even see itself.

     

    I've looked at your later posts and all seems to be correct there too.

     

    Ok I own up - the computers name is snuggles.....

     

    In your case "Snuggles" I would lay this trouble on Tranquil PC after all you paid them for a functioning  WHS

     

    This should work locally on the WHS regardless of router configurations.

     

    But I was thinking  if you tried changing the server name back to the "Original Name" and see what happens.

     

     

    Sunday, February 10, 2008 8:18 PM
  • Rouza

     

    All you say above is correct. I am just about to leave for a foreign trip for a week so I am not going to reinstall today! Hopefully there may be another response from the WHS team when  get back.

     

    Not sure how relevant it is but when running the "Router Configuration Details" it confirms positive on "Verifying your website is available on your home server" but shows a failure "Verifying that Remote Access is available on your home server".

     

    Thanks again.

     

    Phil

     

    Sunday, February 10, 2008 9:06 PM
  • I'm getting exactly the same symptoms as yourself, but just before I got an Unknown Error (0x80004e23) during Domain Name Setup while establishing my new homeserver.com domain name.

     

    (See related thread: http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2819292&SiteID=50)

     

    I can see my home page from my internal network, but, same as you, attempting to log in gives me a "Internet Explorer Can't find the page" error.

     

    I wonder if the two are related.....

     

    Lots of people are reporting WHSs returning "Unknown Error (0x8004e23)" over the weekend, check out the posts here:

     

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2819192&SiteID=50

     

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2818813&SiteID=50

     

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2817211&SiteID=50

     

    There's lots of speculation in these posts as to why this is returning such an obtuse error (unknown error = unknown next step)....

     

    Most people have tried clean reinstalls, and that doesn't fix it.

     

    Since I suspect the two are related, I'd love to know the outcome of this.

     

    Cheers,

    M

    Sunday, February 10, 2008 9:28 PM
  • Hi all,

     

    Hate to be the 1,000,000th person to say this, but I have the same issue. Just installed the evaluation copy a couple of days ago - BTW evaluation not going well (that was aimed at you microsoft LOL).

     

    I ran through the connector troubleshooter and it works fine on server/home etc but does not give me the option to log in never mind get an error, then just a few hours ago it returns the error message of 'Internet Explorer cannot display the webpage'.

     

    I have checked all the firewall troubleshooting addresses and firewall appears open. All ports appear correct in windows firewall and my router is enablled for UPNP.

     

    However, remote access details in the console return as UPNP not as standard and unable to access via remote or web. I have run a microsoft windows independant router checker and it passed UPNP by opening 15 ports and deleting them afterwards. It was the initial router checker to make sure of compatability with WHS. I have spent the last 24 hours researching blogs and every article I could find on WHS to no avail. I have altered and reset tens of setting on my router, firewalls, home computers and windows home server in case of conflict with no success. Now everything is back to normal I am left feeling like I wasted all that time moving and storing my 1tb media collection.

     

    I MAY HAVE GOOD NEWS THOUGH - I HOPE LOL. I found a september update on the WHS support page that states, and i quote

     

    "Remote Access configuration and troubleshooting
    The configuration of Windows Home Server Remote Access may fail because of different factors. This package updates the remote access configuration steps and the corresponding Help files. This improvement helps you troubleshoot issues that occur with home network routers, with firewalls, and with other broadband implementations."

     

    If anyone out there can confirm whether this might have been successful for them or if you know this did not resolve your problem. Unfortunately I have to wait to be approved.

     

    In case anyone is interested I have a BT Voyager 2110. I wish us all luck and I will let you know the minute this gets solved.

     

    Thanks Andy

    Monday, February 11, 2008 12:43 AM
  • I too had been plagued by this problem and couldn't understand why it was acting this way.  My router (Linksys WRT-54GS v2) was properly configured (first by manually setting port forwarding, then also by installing DD-WRT and letting WHS do it's UPnP thing as well).  IIS didn't appear to be out of whack from what I could see in the properties pages.  I could reach the WHS web interface via //localhost on the WHS and from the WAN (by both anonymous proxy and client machines).  I was also plagued by the problem in this thread ( http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2818813&SiteID=50 ).  A lot of hair pulling, much cussing and many hours of reinstalls later, I have a solution for both of them.

     

    First, if you have the "Unknown error (0x80004e23)" bug that is in the above linked thread (as well as a couple of others), reinstall WHS.  After reinstall, turn off automatic updates and manually do the Windows Updates.  When presented with the KB941914 (GoDaddy Security Certificate) Update, do not install it.  Be sure to uncheck it and tell Windows Update to hide it.  Don't install this and just live with the certificate error until MS fixes this (you can always add your WHS to trusted sites if you don't want IE to squawk at you about the certificate).

     

    Next, what I did (quite by accident) to fix the problem of not being able to access the WHS web interface (other than http://servername.homeserver.com/home) was to install the Whiist add-in and add a website (make sure it places a link on your public homepage).  Restart the WHS.  You should now be able to access all of the web content and remote in to your WHS via IE from your LAN.

     

    I don't know why this works, but it does and I am now much happier with WHS.  I've spent enough time (more than 20 hours) trying to "fix" these two problems and I'm not going to spend anymore to trace code and figure out why this resolved the problem (but if anyone else does, I wouldn't mind seeing the explanation here in the forums).

     

    Hope this is of some help to someone here, as these do not seem to be isolated problems.

    Monday, February 11, 2008 4:35 AM
  •  

    *THIS IS BEING REPLIED BACK TO ALL THE POEPLE THAT ARE HELPING ME - A BIG THANK YOU*

    OK, here is a list of my completed actions from your replies:

    1. I have removed update KB941914 without re-installing as I have collected about 1tb of data in the last 4 years and I can't risk loosing anymore by taking it off again. IT WORKED! Thank you. I have now set-up a domain name successfully.

    2. When I try to access my website using https://<mydomainname>.homeserver.com I get 'Internet explorer cannot display the webpage, however, when I access http://<mydomainname>.homeserver.com  I get my router configuration page. Any idea's why this may happen?

    3. I have looked through the router configuration of my BT Voyager 2110 and I can't see anything that mentions 'Remote Administration'. There is only one setting for 'Remote access to your router from the web' and this is disabled. I have enabled this before with no improvement. Any idea's what remote administration would look like?

    4. I have forwarding ports 80, 443, 4125 to my home server internal IP address and am about to check shields up. I have noticed that this IP address does change depending on what computer are connected to the network. Won't this render the port forwarding useless? I have tried putting a static IP address on with the prts forwarded to no avail. I can confirm ports 80 and 443 are open and 4125 doesn't appear like you said it wouldn't. I did notice that port 5000 UPNP is closed. Should that not be open?

    5. I would like to try and resolve this to use WHS and not an add-on like Whiist, but thank you and I shall keep that as a last reort.

    6. Lastly, I found some administrative tools last night on WHS. One being router and remote access. There was a red disabled mark next to it. Could that be causing any issues? Could you let me know how yours appears?

    Any feedback would be great. Thanks again.

    Monday, February 11, 2008 1:45 PM
  • As a side note when i go to http://<myservername>/home i get my web page with the log on button. When I click this i get 'Internet explorer cannot display the web page'. Any idea's?

     

    Thanks, Andy

     

    Monday, February 11, 2008 1:49 PM
  •  

    1: yep removing that allows you to edit the domain name - but I'm afraid thats all it cures.

    2: Thats because you are doing it from inside your network - so the router sees the packets going out and grabs them thinking you want to access its management interface instead of forwarding them to the homeserver. This is common with a lot of routers - someone coming from outside would see the home server.

    3. Disble this or it wont forward packets from the outside world on port 80 (http port) to the homeserver but it will assume they want to manage your router.

    4. Yes - You can configure WHS to use a static address but I wouldnt go down that route till the underlying problem has been solved my microsoft

    5. Well other than uninstalling and not doing the upgrade it is currently your only choice.

    6. Sadly no - that is just a symptom of the problem we are all having.

     

    Monday, February 11, 2008 1:55 PM
  • sadly the login button bit is part of the same problem,

     

    I'm afraid its reinstall or wait till microsoft get off their backsides and do something

     

     

    Monday, February 11, 2008 1:56 PM
  • Thanks for the reply. At least I know I am not going mad LOL!

     

    Do you really think a re-install will solve the problem? I have read that others have done it and acheived nothing.

     

    Monday, February 11, 2008 2:05 PM
  •  

    reinstalling and turning off automatic updates and then doing the updates apart from the 941914 patch does apparently work according to one thread.

     

    However just removing it without re-installing means you can set up you homeserver.com account but the server wont work anyway so not much point there. Some of the people who have reinstalled had the auto update on so it reinstalled the patch after their reinstall so they were back in the same position as the rest of us.

     

     

     

     

    Monday, February 11, 2008 2:11 PM
  • Hi All

     

    Any update on this problem particularly from the WHS Team? I would rather not have to re-install even if that is an allowed option when re-booting from the WHS install disk!

     

    Phil

     

    Thursday, February 14, 2008 3:38 PM
  • OK, in the absence of any advice from the WHS Team and having returned from my business trip, I did the following:

     

    1. Reinstalled WHS (not a new installation).

    2. Set Windows Updates to "Manual".

    3. Fixed the IP address of the server.

    4. Set up xxxx.homeserver.com domain name.

    4. Tested http/https access on both internal LAN and Internet successfully.

    5. Ran Windows Update manually and installed all critical updates with the exception of 941914 and IE7.

    6. Retested http/https access successfully.

    7. Defragged the System Drive (CSmile with the WHS defrag tool.

    8. Retested http/https access successfully.

    9. Am now drinking a beer to celebrate.

     

    So it seems that 941914 is the root cause of the problem and just removing it does not help, it requires a full reinstall! Thanks to all who tried to help and hopefully this may prove of use to someone else.

     

    Phil

    Sunday, February 17, 2008 5:39 PM
  • I had the same problem.  I had a Netgear WPN824 that was working fine(last check was a few days ago).  I just upgraded it to a Netgear WNR3500.  UPnP looked like it set it up fine, but I couldn't access the server using the homeserver domain.  I could access it using http://server though.  I disabled UPnP and rebooted the router, then manually configured Port Forwarding using ports 80, 443 and 4125.  My Server has a static IP.  I had to use different names for each port, like WHS, WHS1 and WHS2.  I can now access xxxxx.homeserver.com.  I just noticed that the computer tab doesn't show up though.

     

    Monday, February 18, 2008 1:48 AM
  • I am having exactly the same problem, Has the WHS Team not got a solution  it can post  maybe a 'settings' checklist

     

    Mike

    Tuesday, February 19, 2008 10:55 AM
  • The problem that occurred seems to be to do with the server getting an invalid certificate from microsofts servers during the install process. This magically sorted itself out a couple of days later when microsoft solved the problem.

     

    If you are getting exactly the same problem - ie you cant even get to http://ip_address_of_server or http://servername when on a machine on your home network then what I had to do is the following.

     

    Wait until microsoft fix their servers

     

    go into the remote access, turn off websites, unconfigure the router, unconfigure the domain then reboot the machine

     

    go back into remote access again

     

    turn on websites

     

    reconfigure the domain name - but choose a new domain name

     

    reconfigure the router.

     

    It then worked.

     

     

    For some reason the critical bits seemed to be the reboot after unconfiguring anything and getting a new domain name. It still told me the router wasnt configured for remote access but it did work fine anyway.

     

     

    If it isnt exactly the same - ie you can access locally but not remotely then its 90% most likely going to be the router configuration

     

    Tuesday, February 19, 2008 11:04 AM
  • Rich-navsys

     

    Are you saying you have a system working with 941914 installed?

     

    What do you mean by "Wait until microsoft fix their servers" ? Are the servers fixed and by that do you mean 941914?

     

    Any idea why you need to choose a new domain name?

     

    Phil

    Tuesday, February 19, 2008 12:50 PM
  •  

    Yep 941914 is installed.

    From what I can work out through various peoples experiences is that when you first configure the remote networking, the server connects to microsoft for some sort of certificate. Once that is installed the system should work. However when this thread started microsofts servers were either down or giving out dodgy certificates.

     

    Now 941914 was the update that first introduced the need for a certificate - so if you do a reinstall and dont install that patch the system will work.

     

    But if  you just uninstall it some stuff seems to work - like setting up the domain - but the secure server in WHS doesn't work as uninstalling the patch still seems to leaves some dependencies on the certificate being installed.

     

    The router not configured for remote access shows as failing as the test used to see whether its working is to make a secure connection to your home server from outside - which of course fails as the secure server isnt working. So the 'it's your router not configured correctly' posts that people make are wrong in this instance. Whilst thats the most common reason its not valid in this case - the telling point being you cant e access the secure pages or the home page even by rd ing into the WHS and using the inbuilt ie7. 

     

    So if you happen to set it up when the microsoft servers are faulty the only option is the reinstall and dont apply the patch.

     

    The second option is to wait until microsoft fix it and try it all again.

     

    Myserver didnt bounce straight into life when microsofts servers came up. I tried rebooting, then followed the suggestion about turning the websites off - but it still wasnt right even when i resetup my domain name.

     

    So when I changed the domain name to a new name a new certificate was issued for the new domain name - I assume that my old name had an invalid certificate against it so it didnt work.

     

    Now all the above is just guesswork and patching together lots of other experiences from other threads and a lot of experimentation - but as a theory it does  fit the observed facts. As far as I am aware microsoft haven't commented giving an official explanation.

     

     

    Tuesday, February 19, 2008 6:04 PM
  • I was the first person who had posted saying I had the same problem as rich-navsys.

    I just followed the steps that rich-navsys laid out and it solved my problem. The steps were:
    1) Open the WHS Console
    2) Navigate to Settings->Remote Access
    3) Under the Domain Name section choose Unconfigure
    4) Under Web Site Connectivity choose Turn Off
    5) Reboot server
    6) Re-open WHS Console
    7) Navigate to Settings->Remote Access
    8) Under Web Site Connectivity choose Turn On
    9) Under Domain Name choose Setup
    10) Configure a different domain from the one you had before
    11) Under the status it should say Testing then Working
    12) You can then click OK or Apply to save your settings

    What I was able to do afterward was unconfigure the new domain name and go back to my old one and everything still worked.

    Thanks Rich-navsys
    Sunday, March 2, 2008 8:26 PM
  • Worked for me too even with 941914 installed!

    Thanks

    Phil
    Wednesday, March 5, 2008 11:36 AM
  •  

    Hey guys,

    hopefully someone picks this up.
    I have been struggling with this for days and all-nighters now.  I am ready to collapse Smile
    I have exactly the same issue and was beginning my cry for help here
    http://www.wegotserved.co.uk/forums/index.php?showtopic=957&st=0&gopid=4578&#entry4578

    Then I found this, but despite everything I cannot get this damed https remote access to work. I did everything.  It must be this certificate stuff. But does anyone have more info about it?

     


    I give up Sad.
    I really tried every posting I found on the internet.

    Especially from here : http://forums.microsoft.com/windowshomeserver/showpost.aspx?postid=2818627&siteid=50&sb=0&d=1&at=7&ft=11&tf=0&pageid=2

    --quote from that forum ---

     just followed the steps that rich-navsys laid out and it solved my problem. The steps were:
    1) Open the WHS Console
    2) Navigate to Settings->Remote Access
    3) Under the Domain Name section choose Unconfigure
    4) Under Web Site Connectivity choose Turn Off
    5) Reboot server
    6) Re-open WHS Console
    7) Navigate to Settings->Remote Access
    8) Under Web Site Connectivity choose Turn On
    9) Under Domain Name choose Setup
    10) Configure a different domain from the one you had before
    11) Under the status it should say Testing then Working
    12) You can then click OK or Apply to save your settings

    What I was able to do afterward was unconfigure the new domain name and go back to my old one and everything still worked.

    -- end of quote ---

    I did the same + even additional steps :

    Removing .net framework (for the sharepoint install) (which worked flawlessly by the way)
    Removing KB 941914


    Still the same old damned issue.

    http://xxx.homeserver.com/Home no issues
    http://server/Home no issues

    Clicking on the log on button gives page cannot be displayed
    Entering the URL without /Home gives page ccannot be displayed

    https://xxx.homeserver.com/Remote
    https://server/Remote

    Give page cannot be displayed immediately.  But way too quick in my opinion. Like it is not even trying long enough to resolve. 

    I can telnet in my ports fine, I tested with Shields up. All good. It is not router/firewall.

    I strongly suspect something with the security certificate that is linked to the custom domainname.
    How does this work? Is Microsoft DynDNS service issueing such a certificate to be linked to your .homeserver.com domain.  I have the feeling there is no such certificate linked to my domainname. 

    I am so stumped and still want to get this working as the remote access is so important for me.

    Any brilliant ideas, anyone?

    PS:  I do get a green check saying https is working oddly enough

    Friday, March 7, 2008 8:38 AM
  •  

    My ongoing searches have finally brouhgt me to the root cause of the issue.  It is not fixed yet, but finally I see why https access is not possible on this guys WHS.

    When going in IIS/right click default website/directory security/secure communications/view certificate  I get nothing.  So I have no SSL certificate at all!

    On My WHS box, when I click this I get a GoDaddy certificate.  On my box https works fine.  On this guys box, only http.

    I am now talking about the full names like : https://xxx.homeserver.com/Remote
    Without the /home (for http) and /remote (https) nothing works, but I don't care.  I just want this https to work. If it requires the full URL so be it.

    So all this port changing in IIS, router changes etc etc was all waste of time.  No wonder I could not get it to work.

    I did already 3 new .homeserver.com names, I always get a green check but still no certificate.  Does anyone know how to force it?  I know I can buy one, but still I like the homeserver (free) ssl thing....

    At least I am glad I do not longer need to focus on ports, any tips are welcome!

    PS: and I think I also found why it happend after all.  I pre-configured his machine in my house.  Including setting up the homeserver.com domainname.  I am on a different provider than he is. 
    When I brought over the box, it still worked (I can http, rdp fine to xxx.homeserver.com) i guess, it just took that guyds IP by itslef but then probably the SSL got messed up as two totally different Dunamic IP ranges.  Makes sence or am I loosing it completely now?

    Friday, March 7, 2008 10:26 PM
  • Out of curtsey just a followup.

     

    I bought an SSL certificate (19 Euro) generated the initial key via IIS and entering my desired hostname server.xxxxx.be.

    I imported the bought SSL key into IIS and hurray!! It works without a hitch!  https://server.xxxxxx.be/remote

     

    So in case this would be picked up by the MS WHS team :

     

    The SSL certificate issueing (GoDaddy) is not without hick-ups.  When you first expirience the issue you can even try and unconfiguring and applying for new .homeserver.com domainnames you will never get the SSL certificate allthough a green check in WHS Consule (but a red cross in the details of https domainname status)

     

    If you go in IIS security you'll notice there is no SSL certificate and it seems impossble to force and get a new one.

     

     

    What I suspect happend is that the initial configuration of the WHS box took place when connected to provider A.

    I then took the box with me to install at a frieds house connected to provider B, since then it seems like it never worked anymore (alltough I cannot be 100% sure as I did not test https access when pre-configuring it)

    I did also install SharePoint 3.0 SP1 with the .net framework but I do not think it did a break up of anything (i run it all on my box without problems)

     

    Hope this post helps other people (unfortuantely it will cost a little bit of extra money to apply for your own domainname and asking for an SSL certificate)

     

     

     

     

    Sunday, March 9, 2008 11:45 AM
  • I am not sure if this is of any help, or in time. But I found it easier too make my WHS NIC card use a static address, what took me awhile to figure out was I need to use the DNS number of my ISP  to make it accesssable to the outside world despite the router having all that info. All I saw for 2 weeks was the yellow indicator saying my network was at risk, and could find a shred of info to send me in the right direction in the help files or from Microsoft.

     

    Hope this solves the issue you are having.

     

    Discystein

     

    Tuesday, March 11, 2008 6:13 AM
  • Having the same issues.

    It all hapened after installing net framework 3.0

    I have reinstalled the WHS already twice, has not solved the problem

     

     

     

    Wednesday, April 30, 2008 8:26 PM
  • Further to the various posts on here - DID THIS EVER GET FIXED ? :(

    I have the all the relevant ports forward as needed BUT you can NOT access the server remotely outside of my network.  The remote access option says it can not get a connection so although all the relevant connections work fine internally, externally nothing.

    If I change the port forward to a different IP address they all work fine - they are only blocked when pointed to the WHS IP.

    I have seen else where on here people have had the same issue back in 2008 but there appears to be nothing since and it's now 2010 - so has anyone come up with a working solution / patch as yet ?

    A while back it used to work - so it looks like its a patch or application which is causing the conflict.

    I currently have SharePoint working internally but I really need to be able to access this externally - any help any one can provide would be most usefull.

    Thursday, April 29, 2010 6:44 PM