Windows Media Services and NAT (284211)
The information in this article applies to:
- Microsoft Windows Media Services 4.0
- Microsoft Windows Media Services 4.1
This article was previously published under Q284211 SUMMARY
You can host Windows Media Services behind a Network Address Translation (NAT) server. When you host a Windows Media server inside of an NAT server, you must configure the NAT software to forward requests for TCP and UDP port 1755 to the Windows Media server. The exact steps to configure the NAT can vary depending on the software vendor. When you point a Windows Media Player client to the Windows Media server, you need to use the NAT's external internet protocol (IP) address instead of the Windows Media server's actual IP address.
MORE INFORMATION
You can also use the Windows Media Encoder on the inside of an NAT server and have a Windows Media server connect to the Windows Media Encoder with a similar process. Instead of configuring the NAT for port 1755, you can configure it to forward the port that you set up on the Windows Media Encoder. Usually, this is port 8080 for Windows Media Encoder 7.0 and port 7007 for Windows Media Encoder 4.1, but it can be any port that you want. When you point the Windows Media server to the Windows Media Encoder, use the NAT's external IP address instead of the Windows Media Encoder's actual IP address. Because the Windows Media Administrator uses DCOM to communicate with Windows Media Services, it is not possible to administer a Windows Media server with the Windows Media Administrator through a NAT server.
For more information on NAT, see "Request For Comments (RFC) 1631 - The IP Network Address Translator (NAT)."
| Modification Type: | Major | Last Reviewed: | 10/28/2003 |
|---|
| Keywords: | kbinfo KB284211 |
|---|
|