"TotalStream.net" wrote:
[Quoted Text] > > Simply setup a windows media server on the internal lan, and have your > internal dns server point requests for the 100 internal users to the > IP address of the internal windows media server. Then have one > inbound stream to your publishing point, and replicate it. You should > be able to setup the publishing point on port 80 inbound, which is > normally open with most firewalls. >
I agree this is clear and easy way of proxying streaming, but I finally know that colleagues responsible for frontend firewall will not open path for inbound traffic on port 80 directly to media server. There is no issue for me to publish external stream under different URI than original source, I will deny access to it from any host on internal network except media server and announce internal URI instead to everybody. Problem is different: There is front firewall not under my control, then ISA 2006 as backend firewall which I can manage, and media server is behind both firewalls on internal network. ISA Server is allowed to establish connection on all necessary ports to hosts on Internet. So what I need is advice how to tell Media Services to act as pull client (Media Player) behind ISA server. I have read something in Windows Media SDK and it leads me to the need of custom plugin - there are properties and methods related to use of proxy in object model, but I do not believe I am first man on the planet trying to do stream proxying through ISA Server... and somebody has already easy workaround at hand for this situation ;-)
|