Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
what do you mean "microservices running on IIS"?
Is It an API endpoint exposed on a certain port?
This sounds like a DNS thing (specially if customers i.e., public internet can access it)
Maybe your network can't resolve it to your port on your IIS machine?
Im assuming your company network's DNS in resolved in-house to access company-specific resources, which is where the issue/gap might be -
@azuredivay So I've got a couple of self contained nodejs microservices and one flask microservice running with their ports exposed, added to IIS, all that good stuff. I guess it could be a DNS thing, and of course no one here has any idea how that works either. I'll do my own investigating I guess, but thanks for the tip.
-
@mostr4am Will do, but I'm going to wait until a little later, because I really don't want to deal with Customer Service at the moment. I have a suspicion that it's because of whatever the stupid local dns is. I always set mine to 1.1.1.1, so that could be it.
Pinging the ip didn't work, I think some genius set the server up to drop pings or something.
Yet another commercial seminar upset I won't give up a day of my time to fly to the UK to speak at the event f...
Boom! Official answer.
Got a legit question/semi rant for anyone who may know. I want to start by saying that I'm not really a "network" person, at least on MS systems. I can physically plug cables in and shit like that, but the software side of networking is not a thing with which I can claim familiarity. Anyone who's read my recent rants will know that I am forced to deal with IIS, because my boss is an insufferable microshit fanboy of the highest level, and is easily frightened and threatened by the use of a keyboard for anything other than using facebook.
I've got a couple of microservices running under IIS, and our customers thankfully are able to access them with no issues. Those of us in the "IT department" are also able to access it. No one else in the building, on our network can, and despite me not having set up this network, or really having anything to do with it, the rest of my "team" (LOL) refuses to help me solve the problem, because developer = networking specialist and printer fixer. Does anyone here have an idea? I found a think on Stack Overflow about firewall rules, but those are already set appropriately.
question
iis
networking