Quantcast
Channel: Forefront TMG and ISA Server forum
Viewing all articles
Browse latest Browse all 3822

RealMedia Streaming Failure through TMG

$
0
0

Howdy 

We are implementing TMG on a test-basis.  Some of our users stream RM data to watch business-related meetings/conferences.  In testing the setup, we keep having this kind of data fail.  The media player is set to not use any kind of web proxy. Any clues as to what I'm doing wrong?

The streaming application filters are enabled, and there are no firewall policy rules blocking any traffic, but TMG is giving these entries: 

Initiated Connection
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63685)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:8080)
Protocol: HTTP Proxy

Initiated Connection 
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63684)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:8080)
Protocol: HTTP Proxy

Initiated Connection 
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63683)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:80)
Protocol: HTTP

Initiated Connection 
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63682)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:80)
Protocol: HTTP

Failed Connection Attempt
Log type: Firewall service
Status: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63681)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:554)
Protocol: RTSP

Failed Connection Attempt
Log type: Firewall service
Status: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63687)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:554)
Protocol: RTSP

Failed Connection Attempt
Log type: Firewall service
Status: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63686)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:554)
Protocol: RTSP

Failed Connection Attempt
Log type: Firewall service
Status: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63689)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:7070)
Protocol: PNM

Failed Connection Attempt
Log type: Web Proxy (Forward)
Status: 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Rule: Allow Web Access for All Users(1)
Source: Internal (165.91.79.35:63682)
Destination: External (realvideoe.house.state.tx.us 204.65.64.46:80)
Request: GET http://204.65.64.46/SmpDsBhgRlc06d14d8-4f88-4c06-8362-f2847aae111c
Filter information: Req ID: 0d74936e; Compression: client=No, server=No, compress rate=0% decompress rate=0%
Protocol: http


Viewing all articles
Browse latest Browse all 3822

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>