Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 72
  • Last Modified:

IIS 8.5 NOT allowing Web App Access via Forefront TMG

After building a new Web Application (a simple one-pager actually) with VS 2015 Rev 3, then publishing to WS 2012R2 IIS 8.5, and creating the simple rule in Forefront TMG to allow the site to be visible to the public internet, the site does not respond / times out.

Fiddler on the gateway machine where TMG is based states that all 200's are being returned for the page, and there is no access issue. When browsed from inside the private network, the URL is obviously going through TMG (port 80 is returned, not port 99 which is how the web application is setup internally).

I've been working on this for a day-and-a-half, and have pretty much had it. Other existing websites are responding without issue, even on the same web server.

I can only think this has something to do with the publishing process for IIS 8.5, or something to do with VS2015 Rev3, but I am hoping that someone out there has had an identical issue and resolved it.

Thank you.
0
Chaste Swedge
Asked:
Chaste Swedge
  • 2
1 Solution
 
Dan McFaddenSystems EngineerCommented:
Is this all on a single server or is the TMG a separate server from IIS?

Have you run the BPA Tool?

Also been discussed here on EE: https://www.experts-exchange.com/questions/25728039/I-have-a-publishing-issue-with-TMG.html

Dan
1
 
Chaste SwedgeAuthor Commented:
Thanks Dan. After much consternation, research, trial and error, and rebuilding Web Server VS's multiple times (too many to count). I found the problem by mistake. As is usual for these types of problems, I was looking in the wrong place for an answer because the actual place 'seemed' to be working.

As I had hypothesised in my question, this issue had nothing to do with VS2015 Rev 3, nor all the new 'junk' that the system adds to a new web site upon creation, nor IIS 8.5.  

For some very strange reason, the external NIC connected to the public internet on the TMG box (separate Virtual Box - 17 in total spanning 2 large physical servers) had an issue. The reason I did not notice this at first was because this particular NIC has 13 public IP's assigned to it, and the ones utilized most often (for Exchange Server and VPN access) were working without issue.

However, while the new Web Server's public IP on the TMG box was placed on a unique IP on this NIC, it was not responding on the external WAN, but had no problems responding on the internal LAN. It took a client complaint for me to notice the problem even existed, and I found the problem when I switched the DNS assignment to a different public IP, and still there was no response on the outside.

It seems that several of the public IP's (but not all obviously) on this NIC were in fact NOT WORKING via the outside WAN. After resetting the NIC, all started working.

I am still baffled by the fact that two out of the 13 public IP's assigned to this NIC were working flawlessly and for many months, while others were not working at all. It's all THE SAME DAMN NIC!  Regardless, this can be an investigation for another time.

Thanks for your assistance Dan!
0
 
Chaste SwedgeAuthor Commented:
I found the problem myself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now