If you use push/pull connection feature on IIS Live Smooth Streaming publishing points, you might run into a problem where somehow those connections failed to be established even though the same URLs work fine from your desktop applications (say Expression Encoder). If your server is behind a HTTP proxy, there is a good chance that it’s caused by the lack of HTTP proxy setting for your IIS worker process. IIS worker process by default runs under a lower privileged account and is not able to pick up the Internet Connection settings from your desktop user. The way to fix this problem is to use “netsh” command to set a machine level HTTP proxy for WinHTTP which the publishing point uses for establish push/pull connections.
An example of the command would be: “netsh winhttp set proxy myproxy” and you should see the following output:
Current WinHTTP proxy settings:
Proxy Server(s) : myproxy
Bypass List : (none)
The proxy value will be encoded in this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings
For more information about configuring WinHTTP through netsh commands, you can check out http://technet.microsoft.com/en-us/library/cc731131(WS.10).aspx#BKMK_5