admin wrote:Benf wrote:I'll try repeating this with a Windows 8 and 7 PC with a file share and see if I get the same results ( but I'd have thought you should be able to replicate this easily ? )
on windows7/8 has no this issue, can you setup an test account on your centos os for us? send a private message to me.
OK, spent the evening testing this out with two Windows 8 boxes - one wired to an AP, and then to the iPad ( different subnets ) and the other a laptop on the same wireless network as the iPad with Win 8.1, the laptop again having the same large content directory. Both are navigable and accessible from other Windows / Linux boxes without issues.
Test 1 : Navigating to the new wired share : I setup the new wired host ( IP address, login credentials ) and then select it. I then have ~30 seconds showing 'Receiving' before 'Network error'
Test 2: To laptop with shares, wireless. : Laptop appears under 'auto discovery' and I'm prompted for credentials. Login, and then can see the contents of the directory ( here 118GB, 700+ files ). Select a file to play ( total filesize 60MB ) and after a ~20 second wait the app crashes completely and takes me back to the desktop.
Test 3: As 2, but instead of playing file from large directory, head into subdirectory and then play ( sucessfully ) a file from there.
To help you fix this, I've got Wireshark captures of Test 2 and 3 taken from the laptop hosting the shares.
For test 2 you can see Oplayer sequentially request all the details of the files in the directory ( which is the reason why I it takes a long time to load ..? ) and for test 2 at the time the app crashes there are some Reset packets coming back.
For test 3 : Same as 2 but instead of loading a file from the large directory, I go to a subdirectory and start to play a file there. I stop the capture a few seconds into the stream when all is well.
Do you have a FTP server I can drop the Wireshark .pcap files off for you to investigate further?