Link to home
Start Free TrialLog in
Avatar of NSSUK
NSSUKFlag for United Kingdom of Great Britain and Northern Ireland

asked on

2008 r2 rdweb ssl issue

We have setup rdweb using a go daddy cert and internally it works fine and the remote apps are working, when connecting to https://remoteweb/rdweb we get page cannot be found, if we remove the rdweb part i get the default iis 7 page so i know the port redirection is working, if we create an vpn connection to the server and use the internal ip/rdweb we get a security mismatch as expected but the rdweb does work.

Thanks
craig
Avatar of LesterClayton
LesterClayton
Flag of Norway image

It is CaSe SenSiTiVe.

Try https://remoteweb/RDWeb
Avatar of NSSUK

ASKER

tried that but still the same
Check IIS on the server which hosts RDWeb, and be sure that it's not been changed from default.  Is the web server running?

Here is a working RDS Web server of mine.

Naturally, there are other questions like, are you sure that this is the server your forwarding is pointing to?  The fact that it shows you a default page doesn't confirm that it's THIS server.  Can you modify the iisstart.htm document to add some text so that you can see beyond reasonable doubt that this is the web server being read?
RDWeb-Virtual-Folder.png
One thing  that can also interfere with a web site operation is the use of HTTP Redirect.
Avatar of NSSUK

ASKER

have double checked everything and it seems ok, one thing i should of mentioned when i go to the correct address remotely i get a certificate warning to start with, i click continue and it then gives me the message, when i look at the certificate warning it does show the correct go daddy cert, i do also get the cert warning if i look at the default iis page remotely as well but i do see the iis page, sorry should have mentioned that first
Avatar of NSSUK

ASKER

sorry also noticed i dont have remote desktop gateway manager installed which people talk about, should i install this ??
Remote Desktop Gateway manager is only if you intend to use a Remote Desktop gateway - which is a good thing to have.  It means that instead of opening up ports 3389 for the machines to connect to you, you tunnel them over the SSL port of the Gateway server.

If you're getting a certificate warning, this isn't a good thing.  Connecting to it locally is understandable, because it's no doubt using localhost to browse, rather than the external URI.

Would you be prepared to let me have the URL so that I may do some testing?  If you'd rather not put it here, you can e-mail it to me at lester at netscenario dot no.  I'll connect to the host at the URL it should be, using the path it should be, and I'll verify if the certificate is OK or not.  I will understand if you prefer not to do this, but it's hard for me to troubleshoot a problem I can't see.

If you like you can view one of my working setups at top dot toppidrettsgymnaset dot no.  You should be able to get as far as the login page with working SSL.
Avatar of NSSUK

ASKER

I have emailed you the link

Thanks
Craig
ASKER CERTIFIED SOLUTION
Avatar of LesterClayton
LesterClayton
Flag of Norway image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of NSSUK

ASKER

Thank you for your help it was very much appreciated.