I have 2 identical ASP.NET applications, one running on Windows Server 2003 with IIS6 and another running on Windows Server 2008 with IIS7.
The one on IIS6 runs perfectly, but on IIS7 I'm unable to seek while playing my video.
They are both using the exact same HTTP-handler for streaming.
I'm using the JW player for Flash (v. 5.2) and Sorenson Squeeze 6 for converting the videos from .mpg to flv.
The FLV stream-handler is very (but not completely) similar to the one on this site
The one on IIS6: demo.orbicon.dk/wgv
The one on IIS7: kloakkort.nk-forsyning.dk/webgrafvideo/?filename=15050
I'm not allowed to post more than 1 hyperlink yet, so this will have to do :)
Seems like this is an issue with keyframe metadata. Keyframes are used in streaming servers to indicate the nearest position to which you can safely seek. Now, look at your files in the LongTail testing tool:
IIS 6: http://bit.ly/9cAM9X
IIS 7: http://bit.ly/cCoair
You'll notice that the IIS 6 file has several hundred keyframes, while the IIS 7 file does not. This means that the player is making a seek request every time you click in the controlbar, but the only keyframe that's available is at the start of the video, so it restarts.
This could be caused by two things: either the file doesn't have the keyframe metadata, or the streaming server isn't sending the keyframes along. If it's former, that can be fixed using FLVMDI. If it's the later, you'll need modify your server config / streaming script, and for that I defer to the IIS folk.
Best,
Zach
Developer, LongTail Video
Related
In the domain we have two types of networks. One type is allowed to connect to the internet and the other does not allow connections to the internet. The internal network is available to both.
We have a webserver in the network that hosts a Blazor Server application (using iis). The server is in the network that can use the internet. Now when i use my laptop that is also in the network that can connect to the internet, the website on the server is fast and gives me a snappy response. When i open the same site on a computer that is in the network that is not allowed to connect to the internet, the loading speeds are dramatically decreased. We see a slight increase when we set the protocol to http instead of https, but it is not a game changer.
We see that the data is loaded realy fast but the network request takes up to 6.5 seconds and the loading of data 29 miliseconds.
Anyone have any ideas?
We switched the application from https to http. This was a slight increase.
We used wireshark to check the networktraffic but we see the delays in there as well. The connection itself is good not red flags.
We changed the underlying platform of the application from .net 6 to .net 7. This did not make any difference.
We changed the deployment mode from framework-dependend to self-contained. Still no difference.
As soon as we enable the internet for the network, the site is fast again.
UPDATE 26-01-2023
After some more research we figured out that there are two ip addresses that need to be let through to make it fast again. The IP's are 142.250.179.131 and 23.2.226.23. The first IP is an IP owned by Google and has something to do with gstatic, and the second is from a company named Akamai Technologies.
None of the nuget packages or references in the application code reference any of the packages created by Akamai Technologies or Google. Or is there something else i am missing?
Well, if this is the case. I think this also needs to narrow down the scope of this issue. Have you tried to access the site directly using the domain name and port? For this result, you may need to take different actions:
Issue still occurs. Then this problem may be related to the application code development, you need to review the code and troubleshoot.
Issue resolved. Then you may need to check the performance of IIS server. Try to use the Debug Diagnostic Tool and check its performance. Something like this:
My goal is to run flash locally on a Windows Surface RT tablet. From research, I have found that for websites to run flash, they have to be whitelisted on Microsoft's website. Through further research, I have found how to hack the whitelist to add any domain:
http://www.redmondpie.com/how-to-enable-flash-for-any-site-in-windows-8-rt-metro-internet-explorer-10/.
However, I cannot add the local file system (i.e. C:\ or file:\\) as they are not domains. One solution, I have though of is by using localhost. How can I write a web server to run on Windows 8 Surface RT, or can it be done?
In C#, I know you can use System.Net.HttpListener: http://www.codehosting.net/blog/BlogEngine/post/Simple-C-Web-Server.aspx. Is System.Net.HttpListener supported with Surface RT? If not, what are alternative solutions to play flash locally?
Theoretically, it is possible. You need to use StreamSocketListener to get a StreamSocket. Then you handle http input from that socket (tons of work), and send back your response. I've made my protocol work. One thing you might need to pay attention is that you might need a second machine to send the http request. I use IE from another PC to send the test request. Win8 network isolation won't allow tcp connections between 2 apps of a same machine...
I am creating module for video management. I researched everythingand know how to do that, but coped with strange problem. I will use standard Media Capabilities of orchard. I mean i click Media -> Add Media and choose file to upload to server. When i choose .wmv(and other not video formats) all works fine, but then i tried to upload .avi, .mp4, .flv it gives me - Error 101 (net::ERR_CONNECTION_RESET): The connection was reset. I have tried in different machines and different window(windows 7 and winows 8), in defferent browsers(firefox and chrome), but the same problem.
Please help.
Regards,
Dima.
Please raise the IIS size limit setting: http://msdn.microsoft.com/en-us/library/ms689462(v=VS.90).aspx
I have a vcf project. My problem is my service isn't playing wave sounds. When debugging vs2010 will play sounds, but if I use a web server (iis 7), the sound is not playing. I know it's an unusual request but this server is special and it is talking people. I am using system.media lib and my object is SoundPlayer.
You should be able to use Process to run a separate process with your sound player. I'm not at all sure that this is what you are looking for.
One of the projects I am working on includes a website that
is hosted on a cheap shared hosting server.
Whenever I upload to the server some updated files, they don't
necessarily become available immediately.
It can take from 15 to 30 minutes before the server actually
starts using the new files instead of the old ones and in some
cases I even need to re-re-upload the updated files.
Some more info:
- C# webforms files (.aspx and .aspx.cs)
- If there was no previous file with that name on the server
then the file always become immediately available
- But if I first delete the older file and refresh the page
I get immediately a "file not found" error but if I then upload
the newer file the "file not found error" stops immediately but I
get back the older file again.
I understand that the server isn't actually serving the .aspx
page but rather using the compiled to dll version that it has made
(right?) so maybe this is a compiling problem on the server somehow?
I'm not sure if this would be better on serverfault.com
but as a programmer SO is where I usually come.
Any idea why this is happenning and preferably some solution
on how to fix this behavior so that when I upload an updated page
we can start using it immediately?
Thank you.
Usually, touching your web.config file will recycle the web server - if you do that, you should flush any caches. Just upload a new web.config with a trivial change and see if that helps.
If you are using .NET 2.0 websites, you can have problems with the .dlls in the bin folder. Changing to a Web application should solve your problem permanently.
http://webproject.scottgu.com/
I have seen this behavior on one of my sites as well.
In my case the issues began just after the hosting provider had moved my site to their new SAN-solution.
It turned out that this new storage solution did not support "file system watchers".
And without it IIS would never receive any notification of when a file has been updated or not.
The workaround they introduced was to move the applications into new application pools with regular intervals. (This gives the symptoms you are describing with updates only being applied at regular intervals.)
The only solution I found was to move my sites to a different hosting provider.