Re: Self Signed Certificates

Hi, Thanks for the reply.

Companyweb works internally using http://companyweb.
RWW works fine using SSL port 443.
I want external users (who have domain accounts in AD) to be able to access
the web site directly using https://companyname.dyndns.org:444 using Windows
authentication as the site contents is confidential.

This works perfectly for several users using home broadband but several
users are based at remote sites within other company networks. When they
type the address https://companyname.dyndns.org:444 nothing appears to happen
and no apparent error is given - the egg timer appears and eventually
timeouts. it does not even prompt for username and password.

I have checked firewall I control (port 444 is forwarded) and do not beleive
this is the problem. My gut feeling is that the problem is related to the
use of windows authentication (company users would be accessing from a domain
based account where as home users would not) or possibly the use of SSL port
444 being blocked by other routers.

My config for the site is using port 444, windows authentication, SSL is
enabled and no IP restrictions are enforced.

Port 443 is used for RWW, how i can test sharepoint on this port without
affecting RWW access.

Thanks
Scott





"Lanwench [MVP - Exchange]" wrote:

In news:3684817D-2CC1-4659-8568-AA002ADB3D7E@xxxxxxxxxxxxx,
Scott Shinnie <ScottShinnie@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Thanks for the quick reply, i have used the http://***.dyndns.org one

which is reassuring, not sure if this should use https or http or if
it makes a difference when creating the certificate.

You don't enter anything like that at all when creating the cert. Just

myname.mydomain.com

You use https: when you're trying to use/*access* something - this should
not be in your certificate name at all.


I have a sharepoint site which is setup for external access using SSL
and Windows authentication as the site needs to be secure. The site
is working perfectly for home broadband users but users within a
company network cannot access the site.

What configuration/permissions does the site have? How are they trying to
access it (meaning, via what name - and can't they use
http://internalservername/site ? without SSL internally?

I thought this might be
related to the use of integrated authentication as users wihtin
company network would have their own domain. Only other thing I could
think of was firewalls but this does not appear to be the problem.
One user on this newsgroup appeared to have a similar problem and
suggested this was due to certificate issues. Just trying to narrow
down the problem.

Thanks
Scott

"Lanwench [MVP - Exchange]" wrote:

In news:13E165EE-3A77-4125-8C7A-E4F994F0C09A@xxxxxxxxxxxxx,
Scott Shinnie <ScottShinnie@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Quick Question.

I have a SBS domain named connectndt.local

The company has an external web address which is hosted by another
provider .com

I am using dynamic dns provided by dyndns.org to assign an address
to our static Ip address i.e. http://*******dyndns.org.

Does it matter what name i give to the self signed certificate
created by the SBS server. I currently assign the dyndns.org
address but I think this might be causing problems with external
access.

Thanks

You should use the same FQDN you use for your public access (the
dyndns.org one).

What problems are you having with external access? Your SSL cert
wouldn't normally have anything to do with that.




.

Relevant Pages

  • Re: Self Signed Certificates
    ... RWW works fine using SSL port 443. ... My config for the site is using port 444, windows authentication, SSL ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing ISA Server for first time
    ... Please note that though correct for HTTP SSL on non standard ports I'm not ... the ISA 2004 can only allow SSL 443 port go through it. ... Microsoft is providing this information as aconvenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Std and WSS 3.0 remote access
    ... I have added the self signed certificate to the IIS site and added ... port 444 as the SSL site which naturally corresponds to the old SSL ... RWW and clicks on Use my company's internal Web site they get the same ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing ISA Server for first time
    ... the ISA 2004 can only allow SSL 443 port go through it. ... Microsoft is providing this information as aconvenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: running an ssl webserver
    ... >> My machine is only listening for port 80 connections This is through ... >> How do i open an ssl port on this internal webserver. ... SSLRandomSeed startup builtin ...
    (comp.os.linux.security)