locked
Security certificate question RRS feed

  • Question

  • Overall, installation went smooth for me as well. The connector software prompted me to update for both my Vista x32 and x64 machines.

     

    The  one problem I have seen so far is now, when I try remote access into the server at the url I configured when I first got the Mediasmart ex470, I get this error page.

     

    There is a problem with this website's security certificate.

     

    The security certificate presented by this website was issued for a different website's address.

    Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server.

     

    We recommend that you close this webpage and do not continue to this website.

     

    Click here to close this webpage.

     

    Continue to this website (not recommended).

     

    More information

    Remote access always worked well before and if I choose to continue with the error, I can still access the server normally, albeit with the dark colored address bar in IE 7.

     

    Any ideas why the certificate error occurred after upgrading to Power Pack 1?

    Larry

     

    Tuesday, June 10, 2008 10:36 AM

Answers

  • I split your post out into a separate thread so it was not buried in the "everything is good post"

     

    I assume you have a ***.homeserver.com domain?    If you read the KB article that went with the November 2007 update, the one that provided free SSL certificates for accessing your home server over the internet - http://support.microsoft.com/kb/941914 

     

    Trusted certificate availability

     

    After you apply this update, you may receive a notification that recommends that you update your domain configuration for Windows Home Server remote access. You receive this notification if you have previously run the Domain Name Setup Wizard to configure a personalized domain for your home server. After you update the domain configuration, your home server remote-access site will have a trusted certificate.

    After you apply this update, you will no longer receive certificate warnings in the Web browser when you access your Web site by using an external URL, such as https://your_name.homeserver.com. However, if you try to access the same site by using an internal URL, such as https://server_name, you will receive a certificate warning from the browser. This warning will indicate that the name on the certificate does not match the name of the site that you are trying to access.

    This behavior occurs because the trusted certificate contains only the external name for your home server remote access Web site. However, when you access your home server across your internal home network by using https://server_name, you can safely ignore this warning after you verify that the URL on the Address bar of the Web browser is indeed that of your home server. Additionally, you can use the external name for a remote access Web site, such as https://your_name.homeserver.com, from both inside and outside your home

    Tuesday, June 10, 2008 12:59 PM

All replies

  • An update to my previous post - it seems the certificate error I mentioned earlier only occurs if I am doing a remote access on one of my home computers that contain the current Windows Home Server connector software after installing Power Pack 1.

     

    Now that is not a big deal as normally I access the server directly from home and things also still seem to be fine now in truly remote systems (eg work) when accessing my server.

     

    But since this certificate error never occurred before even when accessing through the website on my home systems, I was just wondering what may cause this to now occur on Power Pack 1 clients containing the Windows Connect software.

     

    Larry

    Tuesday, June 10, 2008 12:26 PM
  • I split your post out into a separate thread so it was not buried in the "everything is good post"

     

    I assume you have a ***.homeserver.com domain?    If you read the KB article that went with the November 2007 update, the one that provided free SSL certificates for accessing your home server over the internet - http://support.microsoft.com/kb/941914 

     

    Trusted certificate availability

     

    After you apply this update, you may receive a notification that recommends that you update your domain configuration for Windows Home Server remote access. You receive this notification if you have previously run the Domain Name Setup Wizard to configure a personalized domain for your home server. After you update the domain configuration, your home server remote-access site will have a trusted certificate.

    After you apply this update, you will no longer receive certificate warnings in the Web browser when you access your Web site by using an external URL, such as https://your_name.homeserver.com. However, if you try to access the same site by using an internal URL, such as https://server_name, you will receive a certificate warning from the browser. This warning will indicate that the name on the certificate does not match the name of the site that you are trying to access.

    This behavior occurs because the trusted certificate contains only the external name for your home server remote access Web site. However, when you access your home server across your internal home network by using https://server_name, you can safely ignore this warning after you verify that the URL on the Address bar of the Web browser is indeed that of your home server. Additionally, you can use the external name for a remote access Web site, such as https://your_name.homeserver.com, from both inside and outside your home

    Tuesday, June 10, 2008 12:59 PM