Any issues with Server 2012?

[Jim A]

Hi All: I have an web app installed on a remote server and am unable to receive any requests on the ports they have opened for the application.  I'm guessing that the problem is on their side -- but would like to see if any of you have experienced the same.

The server is at www.hyperfive.com.  It is running tsPlus without any problems.  I was told that all ports above 8000 are already open.  I tried a combination of those with the NT web app but nothing comes through. I asked them to open 5080 -- same results. The app is secured, if that matters. 

Every other install has worked without a hitch.  Any ideas?  Is there a way I can test this?  I could downgrade to Server 2008 if that would help.

Thanks,

Jim

[Bruce]

server 2012 is fine.

I recommend adding your web server as an exception to the Windows Firewall running on the machine,

cheers
Bruce

[Jim A]

Thanks Bruce. I will pass that along.

[Jim A]

Here are the answers I've been given:

I asked about adding the app as an exception on the router.  They replied:

Network firewalls do not look at executables on your server. It simply denies or allows ports to your server. We have ensured the port is open at the network edge.

They also said:

We are using TCPView from Sysinternals on the server and cannot see the application opening the port.

It just looks like the server is not grabbing the port.

What do you make of that?

[Bruce]

>> Network firewalls do not look at executables on your server

They're completely correct.

However I wasn't talking about NetWork Firewalls, I was talking about Windows Firewall which is almost certainly running on the server, and absolutly does work on an EXE basis.
Control Panel, Windows Firewall, Add Exception etc.

You've seen this window popup on your own machine whenever you run a new server ( Block / Allow) - but on Windows Server versions that window (by default) does not popup up. You have to go to the firewall manually.

cheers
Bruce

[Jim A]

Nice.  Thank you!

[terryd]

Hi Jim. Used both Server2012 and Server 2012 Express with no issues.

[peterH]

Just a long shot: any chance that another web server is running already and listening on the same port? Then your server won't stand a chance.

Peter

[kevin plummer]

try running as non ssl as a test. If it works then it is your ssl setup.

[Jim A]

Thanks guys.  Actually, this is getting more strange.  I uploaded one of the NT demos.  The app won't even run.   Just a flash and nothing.

Their tech guy is available to chat later this morning.  Hoped to have it figured out before that, but worst case, will see what he says.

[Jim A]

The problem is definitely with the SSL.  I recompiled the web1.app demo and it works fine in regular mode.  When I tried the Always SSL (web9) demo, it hears and responds the request coming in at: http://127.0.0.1:88 -- but when it tries to switch over to the SSL address, it stops dead in the browser.

I thought maybe my cert. was off (tho it works everywhere else), but even the demo certificates don't do the trick with the demo app.

Not sure what to do next.  The Windows Firewall is turned off and I still don't get anything through.  Argh.

[Bruce]

Turn off "suppress error messages" to see if that tells you anything. (just remember to turn it back on once you've fixed the error.)

[Jim A]

Thanks Bruce.  That pointed out my mistake (didn't have all the necessary dlls).  All's good.

Not sure how I managed to omit them in this install.  Thanks for the help and the reminder to let it produce error messages. That made it easy.

Best,

Jim