Firmware 2.01.86 Disconnection Solution

I think I solved the, “The previously selected content source has been disconnected. Would you like to browse a different source?” Warning message that pops up when you are watching media being streamed from your samba server. This has been tested on my Windows 7 computer used as the server and the streaming being done wirelessly.

First hit the WindowsKey+R on your keyboard to bring up a run prompt and type in " cmd" to open a command prompt. You may have to elevate yourself to administrator. Once there type in " net config server" and idle session time should be set to 15 minutes. Now type " net config server /autodisconnect:2" to change it to 2 minutes or if you want more aggressive try 1. I don’t know why maybe the server is sending SIGTERM packets to the WDTV Live keeping it active lol.

If you still are having problems maybe it is a samba master browser conflict on your network in which case you can open the registry and mess around in there just be careful. You can reference this page  http://technet.microsoft.com/en-us/library/cc959923.aspx for modifing the registry keys needed to make your windows 7 computer have a higher chance for Master Browser. MaintainServerList is still relevant to Windows 7 but I’ve read IsDomainServer isn’t and that key won’t be in the registry. You can add it back like I did, but I don’t think it worked for me.

So far, I haven’t had any disconnects while streaming or the WD hasn’t been disconnected while just hanging out at the Home screen. If this helps out anyone then great, my mission will have been complete. I was struggling with this for a while and did a rollback, but decided to come back to this version to see if I could get it working.

Your post contains a mish mash of technologies from different operating systems!   :smileyvery-happy:

I wonder how Microsoft feels about “Samba” becoming the name for their file sharing protocol among so many people.  Must give the Samba project people quite a laugh.  Of course you are not running a “samba server” if you are using WIndows 7.  I suggest you look at Wikipedia to learn the difference between Samba and SMB:

http://en.wikipedia.org/wiki/Samba_%28software%29

http://en.wikipedia.org/wiki/Server_Message_Block

Actual Samba servers work perfectly with the SMP.

Then there is your “SIGTERM packets”??  Definitely no such thing.  SIGTERM refers to a particular Linux/UNIX signal, and signals have nothing whatsoever to do with networking (TCP/IP) protocols.  Again, you might want to have a look at Wikipedia:

http://en.wikipedia.org/wiki/Unix_signal

If you want to learn about the SMB protocol, Microsoft has now published specs.  See the footnotes in the Wiki article about SMB to find links to the MS pages.

Oh yes, Sorry my liege, I meant the SMB/CIFS protocol implemented in Windows not the much superior Samba protocol that is being used on my GNU /Linux(for you Stallman folk) computer. If I had my choice, I would install a much larger hard drive in my GNU/Linux computer and use NFS and be done with this problem.

As for the SIGTERM you got me again, I just threw that out there because I didn’t look to see how SMB/CIFS works and as much didn’t really care. I’m sure it’s some compatibility problems with the way WDTV Live and Windows is communicating and the connection just gets dropped.

If you can find another way to help remedy this problem be my guest or in the mean time we’ll have to wait for WD guys to fix the problem.