Unable to connect to web sites On Vbox VM using SSL

[joeller]

I am trying to set up web sites on my Windows Server 2003 R2 VM. These sites would be accessed from a browser on the host. Since this environment is going to mimic the deployment environment, I need to set IIS on these sites to use SSL and require client certificates. However, each time I set a site to do so then I an "Internet Explorer cannot display web page." Firefox is even less helpful. All it shows is "The connection to cpvfssql200364 was interrupted while the page was loading."

When I change the configuration of the web site to not use SSL, then in IE I reach the site correctly but because the application using the client certificates to authenticate the person attempting to connect I correctly get the application specific error that it failed to receive the client certificate information, as it is supposed to. (Firefox on the other hand throws up an NMCI (Navy Marine Corps Intranet) "Network Error" page reporting a 503 error.)

It occurs to me that it is possible that the port enabling SSL communications is not open. However, the section on the user manual about Host only networks does not provide any information about SSL ports. The only mention about SSL is in the discussion on Remote Virtual machines (which I am not using).

Does anyone know what is wrong?

[Perryg]

Not going to be a VirtualBox issue AFAIK. I know for sure it work so maybe it is a configuration issue, Firewall, or Corp network issue.

[joeller]

How can it be a firewall issue? Windows Firewall on the guest OS on the VM is not on. The host machine can reach any other SSL site including those generated on the host machine's IIS Express.

This machine is deliberately set up using host only networking so that there would be no issues with the Navy's network.

I've tried to connect using https and explicitly stating port 443, and port 18083 (that I found in the VBox manual). All I get is internet explorer cannot display web page.

[socratis]

Have you tried a port scanner? Or even simpler, telnet to the port that you expect your server to be? Internet Explorer is not the best network troubleshooting tool.

[edstevens]

How can it be a firewall issue? Windows Firewall on the guest OS on the VM is not on. The host machine can reach any other SSL site including those generated on the host machine's IIS Express.

This machine is deliberately set up using host only networking so that there would be no issues with the ****'s network.

I've tried to connect using https and explicitly stating port 443, and port 18083 (that I found in the VBox manual). All I get is internet explorer cannot display web page.

I wish you hadn't mentioned who you work for. It adds nothing to the technical discussion, and now -- if I were A Bad Guy (tm) I'd be using every means at my disposal to find a vulnerability through you. And given your employer I'm shocked that you didn't consider that before posting.


See my response and the follow-ups in http://groups.google.com/groups?hl=en&l ... cle.server

[joeller]

Have you tried a port scanner? Or even simpler, telnet to the port that you expect your server to be? Internet Explorer is not the best network troubleshooting tool.

I would be very interested in finding out what is a port scanner or what is telnetting. I did a ping to the machine and connected to the VM in both browsers without using SSL.

@edstevens;
It is set up as host only. There is no connection to anything except the host machine.

[joeller]

Running https://localhost on the browser on the guest machine returns: "Cannot find server or DNS Error" This despite the new server certificates provided, the proper configuration of the web site the verification that port 443 is being listened to.

So it is certain it is not the Virtual Box interface between the two machines that is at issue. I fail to understand though why this process which has always been so straightforward in IIS 6.0 on Windows 2003 should be acting out so stubbornly. Is it possible that the installation onto a virtual machine made a difference in the behavior of the application? I can't see why that would be the case.

So unless anyone has any ideas I will turn to the forums.IIS.net for an answer.