Hey Edward, I'm fairly new to Azure myself, and I have more experience with AWS but there is something called Endpoints that need to be configured on a per-VM or per-Cloud service basis similar to security groups in AWS otherwise no connections can be made to the systems. You might want to check there to make sure they're configured to allow the correct protocols/ports for public and private. Sorry if you've already checked that, just thought i'd throw in my 2c.
Thanks, David On Sep 4, 2014, at 7:16 PM, Edward Ned Harvey (lopser) <[email protected]> wrote: > We have a customer who installed our software on an Azure windows server > (listens on port 443). They're not able to connect to it over the network, > but if they install a client on the server itself, then it's able to talk to > localhost. This verifies the service is actually running, and the problem is > either a routing or firewall issue. Of course they've thoroughly checked the > OS firewall. > > I am familiar with Amazon, where they have an added firewall layer in > addition to the OS firewall. Does Azure have something like that? > > Does Azure do some funky NAT stuff that might be confusing to someone > unfamiliar with it? > > Having never used Azure before, any clues what I should suggest they look at > to solve the problem? > > Thanks... > _______________________________________________ > Tech mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
