I have published website via TMG 2010 Sp2 installed on windows 2008 R2 Standard
The website works fine and I can see most of the the pictures
There is only one picture coming with x sign and pic writte on site
I traced it on TMG and getting below error

Failed Connection Attempt TMG01 7/11/2013 4:14:37 PM
Log type: Web Proxy (Forward)
Status: 10061 No connection could be made because the target machine actively refused it. 
Rule: Allow Web Access for All Users
Source: Internal (10.15.16.172:57330)
Destination: External (122.56.22.2:80)
Request: GET http://web.com/images/thumbs/0000363.jpg Filter information: Req ID: 13ad0312; Compression: client=No, server=No, compress rate=0% decompress rate=0%
Protocol: http
User: GROUP\diM
 Additional information
Client agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36
Object source: Internet (Source is the Internet. Object was added to the cache.)
Cache info: 0x100 (Request includes the CACHE-CONTROL: MAX-AGE, or CACHE-CONTROL: MAX-STALE, or CACHE-CONTROL: MIN-FRESH header.)
Processing time: 3026 MIME type: image

AOA ,

Are you using any web security filtering with TMG for example Websense and other.

WS

No I am not using any security filtering

There is standard web publishing rule in TMG Server

What port are you listening on? Is that port unblocked in your windows firewall?

Yes it is on port 80

It is open

If you are publishing an internal resource and your external clients are encountering this error, the most likely cause is that your internal web server operating system is running, but the web service has stopped. Again, your ISA/TMG is communicating with your internal server, but with the IIS stopped, the server responds with a RST ACK since nothing is listening on TCP 80. If you are running a web service on an internal server on a non-standard port, ISA/TMG can bridge that connection, but you need to make sure you specified the correct port. Specifying the wrong port in the bridging will result in this same error.

 

The repair here is as simple as a quick restart of IIS, or specifying the correct port in the bridging configuration. Youll be back in business in no time. While this covers the most common 10061 errors you may encounter, feel free to ask about any other situations in the comments, and I will get back to you promptly with some advice.
This guest post was provided by Ed Fischer on behalf of GFI Software Ltd. GFI is a leading software developer that provides a single source for network administrators to address their network security, content security and messaging needs. More information:

I checked both TMG and website is listening on port 80

There are multiple websites published on web server

One of the website works fine and it is only one of the picture does not showing while browsing

Hi,

Thank you for the post.

I'd like to confirm whether the internal client that bypass TMG server can access the web site correctly.

Regards,

Hi Nick

It works fine if I bypass TMG for internal client

Regards