Hi Shane,
IIRC you must have used the option to create a website when you installed/setup Windows Media Services. If you did this on the same machine as your DNN webserver, you shouldn't have done that or should know how to re-configure to provide only streaming services (main problem is possible website contention, but otherwise is probably not a big deal but I just never do things that way so can't say for sure). Note that the streaming content doesn't have to be (but can be) served from the same box as the DNN webserver, it makes little difference if it's served from another box or even another site on the Internet.
For anyone interested in this, here are the nuts and bolts.
First, as others have posted if you don't install a streaming server application (like Windows Streaming Server/Service which can be installed free on any Windows Server going as far back as NT4), the file will be downloaded completely before it can be played.
When you install a streaming server, the file can be "streamed" by serving the file from the streaming server application to a media player running on the client. To make things convenient, you can embed a player in a webpage either by web browser plugin (like Flash) or by calling a separate player already installed on the machine (like Windows Media Player).
So, describing the recommended setup in just a little more detail...
- Install Windows Media Streaming services on a Server (can be the same as the DNN webserver but can be any server on the Internet).
- Configure the Streaming server, usually pointing to the directory media repository and assigning a URL mimimally.
- Compile/optimize your media content for streaming/streams.
- Recommended practice although often not required is to create metafiles that describe the file(s) to be streamed instead of pointing the client directly to the file
- Install and configure a DNN media module. Although the DNN module described in this forum should work and is more versatile, in the past i've just installed the DNN HTML module and pasted the code to display the WMP in a web page. The code is widely available, one source is here
http://www.streamalot.com/wm-embed.shtml
- Lastly, configure the embedded player (or whatever) to point to the metafile you created, not the actual media file.
Remember that this method of invoking an embedded Windows Media Player requires the client to be runnig Windows, it won't invoke a third party app capable of playing windows media files which would be the case on something like Linux or Mac.
One further comment... you described pushing live content to your website and then in turn streaming to at least one client. Be aware that requires very heavy resources, and typically there is special hardware costing multiple thousands of dollars to do that, but you can see for yourself how far you can go with lesser hardware. Both the Windows Media Encoder (free download from MS) and third party solutions like VLC(also free) provide capability to re-broadcast live streams. I'd recommend at the very least you deploy on the beefiest hardware you can afford running 64-bit. And, of course provision your bandwidth to support both inbound and outbound traffic at whatever bandwidth you want to support.