Faulty DNS recognition by WM server

From: Beth (anonymous_at_discussions.microsoft.com)
Date: 05/10/04 

Date: Mon, 10 May 2004 08:26:10 -0700

I just did a live stream and the server failed at a crucial point in an unusual way.

My WM Encoder is on a Win2000 machine that I use for live streams. This is a mobile setup that I move around campus for various live events. The machine is setup for DHCP and it is registered for DHCP on the University network.

My broadcast publishing point is set up to point to the DNS name of the Encoding machine: streamer.xxxxx.domainname.edu The server doesn’t usually have a problem recognizing the DNS and starts the stream.

Sunday we had network issues, the switch in the building I was working in went down after I had been streaming for an hour. After a reboot of the switch my stream would not start again. After some trial and error I used terminal services and changed my publishing point to look for the IP address of the streaming machine rather than the DNS. It streamed just fine after that. Why would the server suddenly not recognize the DNS?

I should mention that before changing the IP of the pub. point I did a restart of the encoder (no help), then I did a reboot of the Win2000 machine (no help). At one point I clicked the Refresh button on the WM Services page on the server, but it didn’t do anything noticeable (I’m not sure what that’s supposed to do, but I was desperate.)

It is difficult sometimes to access the server remotely so I don’t want to go in and change the pub. point each time I do a live broadcast.

Thanks,
Beth