Library browsing is performed against databased located on Central Muzecast Server.
Metadata is sent from your computer to Central Server. It looks like metadata was sent without any errors.
But sending a file to be streamed to your device is failing with error like: Connection was interrupted.

Ports to send metadata and music file are the same: 80, 65000 and 65001.
Method of sending metadata and music file are also the same.

I am still investigating what is going on, but so far, only your connection has this issue.

I have not tried the case when computer was updated to Windows 10. Test machine with Windows 10 is a fresh install of muzecast, including .NET framework 3.5.

On Windows 10 if you open Control Panel->Add/Remove Programs->Turn Windows features on or off, the least of features shows the following checked:

.NET Framework 3.5
.NET Framework 4.6

O.K...thanks for looking into this. If you need me to do anything my end, let me know. Currently the Muzecast server is running under Windows 7 VM, so ignore any recent successful transfers. I'll switch back to Windows 10 as soon as you have something that you need me to try.

Two things to note when testing with Windows 10:

1) I'm running "Professional" not "Home Edition". Microsoft have been known to change or tweak certain network settings under professional edition in the past because it is intended to be used on an office network rather than at home. If you are testing make sure you really run Professional and not Home, it may make a difference. It probably doesn't make any difference, but I also have remote access enabled because this is a headless server which I usually connect to through RDP (something that only the Professional edition supports).


2) Steaming works fine on local network. When you are testing, make sure you are on a network that is remote to the server


I also checked programs and features. I have both .NET framework 3.5 and .NET framework 4.6 advanced services enabled.

It looks like streaming is working now for your server running under Windows 10. Could you validate that you can stream over 4G.

Have you changed anything on your end?

I checked back in the same location where it was not working yesterday (bad reception area), and today it is working fine, so the problem is definitely resolved, and I know exactly what I did to fix it, but you're not going to like the answer.

In a last-ditch attempt to avoid having to run a Windows 7 VM just for Muzecast, I shut down the service, then I edited the properties of Vorlan.HomeDJ.Server.exe and set "run in compatibility mode" to "Windows 7", then I re-started the service.

I tried to stream after that yesterday, but I guess I didn't wait long enough on a slow network for it to stream enough of the file to start playing, so I though it hadn't fixed the problem. Anyway, at that point I just gave up and left it running. I guess at some point this morning, my son tried to stream some tracks, and that's when you noticed it working.

When I get the chance, I will confirm that this is what resolved the problem by shutting down again and un-setting compatibility mode, and re-starting to see if it breaks.

This really doesn't help you much since you don't want to have to deliver something that needs to run in Windows 7 compatibility mode, but it does serve to eliminate other system factors such as TCP stack. My guess is that running in compatibility mode causes the program to utilize some of the .NET shared libraries differently, maybe it even fails back to 3.5.

Since no one else has seen this problem yet, I'm O.K. to run with the "compatibility mode" work-around, but if you need me to try anything' let me know.

Thanks for your support on this. I've seen it said a few times, but you really do have amazing support for your product, and the product itself is top-notch. Keep up the good work.

Edited by user Monday, January 4, 2016 12:48:48 PM(UTC)  | Reason: Not specified

compatibility mode was still on. I turned it off and re-started the service, and now, magically, everything is streaming over 4g fine.

I can't explain this, unless you tweaked something on your server, or re-coded to allow transfers with blocksize below 64k. Did you change anything on your end?

Anyway, whatever it was, it is all working fine now.

Again...thanks for the help...great product and superb support.

Thanks Guys.

no Windows updates since Dec 30th, but I did make one other change on Sunday. I drilled in to .NET 4.6 and I noticed one sub-component was not enabled: WCF Service -> HTTP Activation, so I enabled it. I definitely tested after I made that change and it didn't seem to fix the problem, but maybe it required a server re-start or something.

If this was it, I guess it defaults to disabled on Windows 10 professional, and this will cause Muzecast to fail. Otherwise it must have been some change you made on your servers.

Edited by user Thursday, January 7, 2016 7:44:35 AM(UTC)  | Reason: Not specified