You must install the proper certificate

Discussion in 'Windows Small Business Server' started by Solve-IT, Sep 14, 2009.

  1. Solve-IT

    Solve-IT Guest

    We get a message when connecting to client desktops in SBS 2008 Standard
    that says "To connect to Remote Web Workplace, you must install the proper
    certificate. Contact the person who provides technical support for your
    network". We connect OK to the server and get the default Web page that
    shows the links for "Check E-mail, Connect to a computer, And Internal Web
    site, etc". We click on "Connect to a computer", get the logon message for
    the computer and then the certificate message.
    We do not have a public Web server and are connecting over the Internet
    using the IP address of the server in the format HTTPS://xx.xx.xx.xx/remote
    We used the certificate already installed on this server option instead of
    purchasing a trusted certificate. We copied the Install Certificate Package
    to the remote client and it said it installed OK.
    What am I doing wrong and how can I fix it?
    Thanks foi your help.
     
    Solve-IT, Sep 14, 2009
    #1
    1. Advertisements

  2. Take my advice - get yourself an SSL cert now, and stop using your public IP
    address to access your network remotely. See
    http://sbs.seandaniel.com/2009/02/installing-godaddy-standard-ssl.html for
    info on the SSL cert.

    You can use a self-signed cert but this is VERY much discouraged, especially
    in SBS2008, and you can't use an IP address with that. You need a hostname -
    e.g., remote.mycompany.com.
     
    Lanwench [MVP - Exchange], Sep 15, 2009
    #2
    1. Advertisements

  3. Hello,

    Thank you for posting here.

    According to your description, I understand that:

    You receive the error while accessing the SBS 2008 RWW.

    If I have misunderstood the problem, please don't hesitate to let me know.

    Yes, Lanwench is right. A certificate is essential for publishing RWW. For
    more detailed information, you may refer to:

    Receiving Certificate Errors When Connecting to Clients/Servers with TS
    Gateway or Remote Web Workplace on SBS 2008
    http://blogs.technet.com/sbs/archive/2008/10/03/receiving-certificate-errors
    -when-connecting-to-clients-servers-with-ts-gateway-or-remote-web-workplace-
    on-sbs-2008.aspx

    If you have any questions or concerns, please do not hesitate to let me
    know.


    Best regards,

    Miles Li

    Microsoft Online Newsgroup Support

    ==================================================================
    Please post your SBS 2008 related questions to the SBS newsgroup on Connect
    website:
    https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx


    Please post your EBS related questions to the EBS newsgroup on Connect
    website:
    https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx


    If you want to use a newsreader other than a web forum to access these
    newsgroups,
    please refer to the following blog to apply NNTP password and configure a
    newsreader:
    http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-20
    08-newsgroups.aspx
    ==================================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ==================================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
    ==================================================================
     
    Miles Li [MSFT], Sep 15, 2009
    #3
  4. Solve-IT

    Martin Guest

    Just get an DNS A record with the same name as your certificate eg. if your
    certificate is remote.yourdomain.com then get an A record (from whoever
    controls your DNS) and then use that to connect - will work a treat!

    If the client doesn't have the certificate package you can email it to them
    as they can still get into Outlook Web Access with an invalid certificate.
    The other advantage of a valid certificate is that RPC over HTTP will work
    (if you need to use that)

    But, yes, I suppose is is easier to buy a cert but for purely your own use
    it does seem slightly pointless - you didn't need to in 2003...
     
    Martin, Sep 15, 2009
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.