Based on your description that it can be accessed on 'localhost' and not externally would lead me to initially believe that it's only bound to 127.0.0.1 and not the external ip.
What does this command show? netstat -ano | findstr LIST | findstr :443 It should show something like: TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 9488 or TCP xxx.xxx.xxx.xxx:443 0.0.0.0:0 LISTENING 9488 where the xxx.xxx.xxx.xxx is the external ip but should not be: TCP 127.0.0.1:443 0.0.0.0:0 LISTENING 9488 On Thu, 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/
