Example Testing Environment for a Networked Media Device
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The following diagram shows an example of a lab environment for testing a networked media device.
.gif "Aa933911.86b8427a-ee72-4ae9-83e2-fbf382e4f195(en-US,WinEmbedded.60).gif")
This configuration is designed to replicate the type of network environment that a home user is likely to have. The central feature of this configuration is that the networked media device and all Windows Media Connect servers are on their own private IP network and are not joined to a domain. You can assign static IP addresses to the devices on the private network, or you can let a DHCP server on the private network assign the addresses. Although you can allow the development workstation to be joined to a domain, in practice you might find it more convenient to place the workstation on the private network as well.