This content has been marked as final. Show 3 replies
Hello Fateh,1 person found this helpful
I'm not sure about Win 2012, as I didn't have any hands on that release yet. Certainly it's not certified (yet) for any of the components you've listed... ;)
Though this is probably not relevant for that specific issue, I'd recommend to consider using supported environments for (public) production systems only.
But as you've found out, this seems to be a purely network related issue. How is your 2012 machine connected to these two networks, especially, does it have two network interfaces or is the external connection going through your local LAN interface?
If you have two interfaces, you probably have two different network zones with individual firewall settings and probably different network zones (including certain trust levels). Instead of disabling the firewall completely, it should be possible to configure firewall/trust/other security policies accordingly. I don't think this is an APEX Listener related issue...
I hope that you are doing well these days...
Actually, I had the same problem previously with Win 7 and Win 2008, and I thought that some of you experienced the same thing...
I have only one Network card .. The server is connected to a small business Netgear router... I am planning to move to the cloud, but they did not give access yet...
I hope you are doing well, too.
I have only one Network card .. The server is connected to a small business Netgear router...So I assume you've configured your router to use your Server as DMZ Host, right? This would ususally be a scenario for dedicated LAN interfaces to separate DMZ traffic from local traffic. Though it might be possible to configure your firewall to get this separated somehow, I'd recommend to change your router configuration from using a DMZ-host to a NAT-Mapping. Your server will treat these requests like other internal requests and your router will do the mapping. Another positive side effect would be that your server isn't facing the internet directly and your "poor" windows firewall isn't supposed to handle all kinds of attacks including resource consuming port scans, etc.. That's what NAT routers are designed for.