Specifications

interface IP address or DNS name.
3rd Party access points however do not tunnel RADIUS request to the BSC and therefore you are
required to configure a RADIUS client in the RADIUS server for every single 3rd Party AP.
Alternatively configure a RADIUS client in the RADIUS server for the 3rd Party APs with an IP
range.
I am trying to renew my ssl certificate on the BSC but I do not see an option to generate a
CSR on the weblogins>ssl>renewal tab.
If the renewal setup tab does not have an option to generate a CSR you may have previously
generated a CSR or applied a certificate. Simply click delete csr or delete cert as appropriate.
Deleting the CSR or cert on the renewal setup tab will not affect the certificate that is currently in
operation. After you delete the CSR or cert on the renewal setup tab you will be able to generate
a new CSR.
I am using the default ssl certificate that came pre-installed on the BSC. Why am I
receiving a certificate error from the browser indicating the certificate was not issued by a
trusted certificate authority?
Examples of the browser error include:
Internet Explorer: "The security certificate presented by this website was not issued by a trusted
certificate authority."
Firefox: "The certificate is not trusted because it is self signed."
Safari: "Authentication failed because the server certificate is not trusted."
By default the BSC uses a pre-installed SSL certificate that is self-signed by Bluesocket. You
will receive a certificate error from the browser indicating the certificate was not issued by a
trusted certificate authority because the certificate is self-signed by Bluesocket and Bluesocket is
not a trusted root certificate authority like Verisign or Godaddy for example. There are two ways
to stop the generation of this web browser certificate error. Install the Bluesocket self-signed
certificate on every client in the browser's list of trusted root certificate authorities, or install an
SSL Certificate Provided by a CA such as VeriSign or Godaddy on the BSC that is already in the
client's list of trusted root certificate authorities.
I cannot make more than one client connection to a Microsoft file share over the BSC. Are
there any known issues with Microsoft file shares and the BSC?
See Microsoft Knowledgebase article: http://support.microsoft.com/kb/301673