[Canned]

<span style='font-size:12pt;line-height:100%'>as some lame-ass-semi-warez-kiddie-groups releasing xbmc cvs compiles and linking here in their nfo´s i wanted to make sure you know what we, the xbmc team think about them....
pretty please, visit this link befor you do anything else!</span>



for those of you having troubles getting the samba shares working with windows 2003 servers set as domain controllers, here's the fix:

as an administrator on the win2k3 server, go to your administrative tools (on start menu) and pick "domain controller security policy". goto "security settings" and then "local policies" and finally, "security options". find the setting entitled "microsoft network server: digitally sign communications (always)" and disable it. then you're all set.

the problem here is that microsoft defaultly forces all data sent over the network to be encrypted and thus unreadable by the samba system at this point (supposidly the new samba services allow support for the encryption). this explains why other windows systems are able to see the network shares while xbmc is not. disabling this will set your server to allow unencrypted data to be sent to clients who do not support the encryption. your server will, however, continue to send encrypted data to clients which support it (your windows systems).

hope this helps anyone with the problem.

canned.

[tslayer]

so, i did a quick test to see why people were having issues setting up their windows machine for smb.

here are the quick steps i took.

note! please remember that the username and password can not have a space in it (for the shares xbox/xbmc account)!

1) right mouse-click on the folder you want to share and click sharing.  for example, c:\movies
2) set the share name.  for example: movies
3) edit the xboxmediacenter.xml that has a path with the following format: smb://username:password@windowsip/sharename

for example:

<bookmark>
 <name>smb</name>
 <path>smb://tslayer:[email protected]/movies</path>
</bookmark>

where tslayer is the username and password is the password that i use to login to windows.
(again, you must remember that the username and password can not have a space in it!

192.168.0.1 is my windows machine's ip address.

movies is the share name i mapped in step 2).

hope this helps anybody wanting to use smb shares in windows.


and to add to that, the same format works on linux using samba v3:
smb://guest:[email protected]/mp3            (note! on my linux box it only allows guest user account)

ts

[rebelpeon]

i posted this in the xbmp forums as well, but have changed it a little to reflect the differences in the xml files between xbmp and xbmc.

ok, since it took me a few hours, and there's no definitive place to look this info up, i thought i'd make one   the reason that smb shares have a hard time with win2k3 is that win2k3 expects the password to be encrypted.  however, since xbmp doesn't send the password encrypted, win2k3 denies access.  this guide will cover scenarios in which the win2k3 box is part of a domain or not.

not in a domain:
if your win2k3 box is not in a domain, you can do one of two things.  the preferred way of doing it is to open up your machine's local policy (start->run, then input "gpedit.msc").  under local computer policy, computer configuration, windows settings, security settings, local policies, security options, change the  "microsoft network server: digitally sign communications (always)" key to disabled.  you will then need to reboot your machine in order for this setting to be enforced.  since the machine is not part of a domain, there should be no group policies that would override the local machines settings.  if for some strange reason you have a group policies running and you're not in a domain, see the section about connecting to win2k3 machines in the domain.  the unpreferred way is to open up the registry (start->run, type in "regedit"), and navigate to hklm\system\currentcontrolset\services\lanmanserver\parameters and change the "requiresecuritysignature" dword value to "0."  after doing this you will either need to restart your machine, or stop and start the srv services and all it's dependencies.

in a domain:
because you're in a domain, group policies will override the local policy if you were to change it as in the above.  if your machine is the domain controller (as was the case for me), you need to edit the domain controller security policy.  it can be found in the administrative tools.  under security settings, local policies, security options, change the "microsoft network server: digitally sign communications (always)" key to disabled.  then get to the command prompt and type in "gpupdate."  this will automatically update your machine(s) with the new domain controller security policy that you edited.  if your machine is not the domain controller, but just a normal workstation/server, then you need to edit the domain security policy.  if you are able to log into the domain controller, this is located under the administrative tools.  otherwise, you will have to use the active directory users and computers snap-in.  go to start->run and type in "dsa.msc", right click on your domain (in my case it's rebelpeon.com), and got to properties.  go to the group policy tab, select "default domain policy" and hit the edit button.  under default domain policy, computer configuration, windows settings, security settings, local policies, security options, change the "microsoft network server: digitally sign communications (always)" key to disabled.  on the machine that you want to share stuff out, go to a command line and type "gpupdate" to instantly update the group policy.

oh yeah, once you have all that setup, you should be able to use the basic setup that is included in the config.xml file.  for me, my domain is rebelpeon.com and the netbios name for that is rebelpeon.  let's assume my server is rbl-dc-01, and that my share is music which allows users read access via the share permissions and it has default ntfs perms.  the user i'm using is xbox:user.  therefore in my config.xml file, it would look like....

<bookmark>
     <name>smb</name>
     <path>smb://xbox:user@rebelpeon/rbl-dc-01/music</path>
</bookmark>

also, remember, caps shouldn't matter except for the user and password.

hopefully that fixes everyone's problems if they were having it in win2k3.  i was pulling my hair out trying to get this working the other night.  thankfully there were enough posts here and there that i got it working.  i hope this will help by bringing all that info into one location.

[ToeCutter]

after reading what seems like countless support requests, i thought i would provide some basic information on smb and windows xp, as most are having difficulties with xp.

this post is by no means comprehensive, it's just a quick answer to all of the smb help requests i've read.

smb implementation changed significantly with windows xp. smb involves the use of two permission sets to allow access. these are share permissions, as well as ntfs permission. if you have not configured both correctly (or at all for that matter) you will be denied access to a given share.

the first thing to do when sharing files for xbmc is to disable “simple file sharing.” go to any open folder and click tools > folder options > view and remove the check from the “use simple file sharing” selection. click apply and ok.

warning: winxp home supports only simple file sharing. see below for info on ccxstreamgui.

share level access is pretty simple and what most configure to share a directory. simply right-click on a folder, click sharing and security, and click the “share this folder” radio button. add a share name and click apply. no need to worry about permissions, as winxp by default assigns the user group “everyone” read access to the share. now, the folder is shared on the network and everyone has read access, right? well, not quite.

even the folder is shared, there are still ntfs permissions that need to be applied. ntfs permissions apply to all users, remote or local. while you may not see a problem locally (because you’re logged in) you very well may have a problem when you try to access remotely. the network client (xbmc) must authenticate with the host (your pc with mp3s). unless the user is specified in both the xboxmediacenter.xml and your ntfs permissions, you will be denied.

the easiest way to do this is to allow the everyone group read access to the folder. to add a user (or group) to an ntfs folder, right click, click the security tab, and look to see if the “everyone” group is listed in the top pane. if it is, put a check in the read check box under allow and click apply. any user that is allowed access the host pc (logon to your pc) should be able to access the shared directory.

if the everyone group is not displayed, then you’ll have to add it. do the following:

1. right click directory and click “properties”
2. click the “security” tab
3. click “add”
4. click “advanced”
5. click “find now”
6. select the “everyone” group in the bottom pane
7. click “ok”
8. click “ok” again
9. verify “everyone” group is listed in top pane.
10. select appropriate rights (in this case, put a check in the read checkbox under “allow”
11. click “ok”
12. done


but we’re still not done if you have directories (or files! inside the shared directory. you must set the share folder to pass on its permissions to the folders inside the share. confused yet?

any directories inside the shared folder do not acquire the permissions of the share folder unless you tell it to do so. example: i shared out a directory called share. i can access share just fine, but when i put a folder inside share called child, i can’t open child from my network. i can see it listed, but i simply can’t open it. this is because share and child have different ntfs permissions. like two different locks, they require two different keys. we can however, make child inherit share’s permissions automatically.

to enable inherited permissions, do the following:
1. right click directory and click “properties”
2. click the “security” tab
3. click “advanced”
4. at the bottom are two checkboxes, add a check the checkbox that reads “replace permission entries on all child objects with entries shown here that apply to child objects”
5. click “apply” and you might see a dialog box as the permissions are applied
6. click ok
7. done

now we’ve applied the same permissions to all the files and directories within the share folder. further more, any new directories or files that are added inherit the permission automatically.

as long as the remote user (xbmc) has an account on the pc, you should be able to access the shares just fine. remember to double check all these settings if you’re having problems. more times than not, a single setting may have been overlooked, resulting in access being denied.

for more info on winxp file sharing, go here: windows xp file sharing


“but toe, this sounds hard and complicated! is there any other way?!”

yes! there is a much better way! use ccxstreamgui and allow it to deal with all this silliness. simply drag and drop folders into the gui to share them! it takes about 3 minutes to setup multiple shares using ccxstreamgui.  

yes, it really is that easy. ccxstream uses the xbox media streaming protocol to do its magic. xbms is much more efficient than smb for media streaming. with smb, my cache was up and down like a roller coaster, probably due to some interference on the 802g network i use. with ccxstream, it is locked at 49%. it never budges. i can stream 9+ mbps mpeg2 with zero stuttering. i strongly suggest that folks try this method.

disclaimer: the toe doesn’t know it all, so if i have made some error, feel free to correct the post. and, because i don't know it all, i accept zero responsibility if you smoke gbs of mp3s on your pc by denying yourself access to them forever! do yourself a favor and test these instructions on "development" directories, not production ones!

[budwizer]

warning: winxp home supports only simple file sharing. see below for info on ccxstreamgui.

fyi - there are a couple of ways to get around the simple file sharing in winxp home.

first method (from ms xp security ng):
-download nt 4 security configuration manager
(http://www.microsoft.com/ntserver/nts/do...efault.asp)
- run the .exe and extract the file in a temporary directory
- select the "setup.inf" file and choose "install" context menu
- answer "no" if you are asked to overwrite esent.dll

the security tab is now active


second method involves booting into safe mode and making changes:

boot in safe mode.
right-click your file. (it should be in the shared documents folder.)
click properties and choose the security tab.
click the advanced button near the bottom.
make sure the "inherit from parent..." box is unchecked.
click ok twice.

[Papercut]

one more thing:

setting up an xbox username and whatnot is very nice, but you can also just use your regular xp login name and password.  then you don't have to worry about permissions, especially if your account is an administrator account.  (if xbmc logs in as you, it shouldn't have any trouble accessing all that you can access, including shares you've created.)

of course, then you have to put your password in plain text in your xboxmediacenter.xml, which might not be so good for some.  

also, just a note: simple sharing is fine, as long as you save all your files into the shared folder.  i, personally, hate that crap and would much rather share any folder any where when i want without moving it.  there.  i said it.  

another note:  relax works as well as ccxstream (with the gui), and the gui mixes both some nice functionality (virtual directories, for instance) with it's simplicity.  if you can't wrap your head around file sharing, though, you might want to stick with the ultra-simple ccxgui.  it is really easy.  really.

and don't worry.  you have to dig pretty deep in windows to lock your gbs of mp3s.  of course, nobody reads disclaimers anyway.  

now if only i could get smb shares to actually work with xbmc on my xbox...  it all works in theory...
-papercut

[neomotion]

okay, after searching my ass off for a simple tutorial for setting up shares through smb on this website and not getting anywhere, i decided to look further and found one. i thought more people could use this, so i'll post it here. might be a good idea to make this sticky? so here it is.

i just modded my xbox this week and found the files and tutorials here invaluable. i did not find much on smb shares for xbmc/xbmp so i thought i would post a quick tutorial. the following assumes you are running windows xp.

from the pc that has the directory your wish to share:

add a user

right click on my computer
choose manage
select local users and groups > users
right click in right window pane
choose new user
enter a user name, password, and confirm password
uncheck "user must change password..."
check "user cannot change password" and "password never expires"
select create
remember user name and password

enable sharing

open my computer
from tools > folder options > view, check the last option of "use simple file sharing"

find the directory you wish to share and right click, properties
choose sharing tab and check "share this folder ..."
type a share name
choose ok
remember this share name
repeat as needed for other shares (video, music, pictures etc.)

get the computer and workgroup name

right click on my computer
choose properties > computer name
remember the computer name and workgroup

add the share to xbmc

copy the xboxmediacenter.xml via ftp from your xbox to your pc

edit xboxmediacenter.xml
towards the bottom are sections "my picture shares", "my music shares" etc.
go to the section you wish to add a shared directory and edit the following line:

<path>smb://domain;username:pwd@mywindowsserver/movies/</path>

as follows:

<path>smb://workgroup;user name:password@computer name/share name/</path>

repeat as needed for other shares (video, music, pictures etc.)

save and ftp back to the xbox.

you should now be able to access the shared drive from your xbox.

add the share to xbmp

copy the config.xml via ftp from your xbox to your pc

edit config.xml

each share section starts with <pictures>, <music> etc.
go to the section you wish to add a shared directory and edit the following line:

<url>smb://username:password@workgroup/computer/share</url>

as follows:

<url>smb://user name:password@workgroup/computer name/share name</url>

repeat as needed for other shares (video, music, pictures etc.)

save and ftp back to the xbox.

you should now be able to access the shared drive from your xbox.

[ edited by bazzx on 2004/4/28 13:40 ]

needless to say after this tutorial i got everything to work. i am not dissing anyone here, but for the noobs it is hard enough to get things to work without everyone telling them to use the search function (which doesn't resolve anything, because it wasn't very well documented how to do it). i found this very helpfull setting things up. enjoy.

[nimbles]

i did this one for another forum i frequent, it's not by any means comprehensive- i don't use usernames and passwords- the only thing i can think this is useful for is hiding porn from the rest of the people on your network :d - i suck with html so didn't put in any pics but its reasonably straight forward and i have had some positive feedback from it

this is a guide to using samba share which is one of the streaming protocols used for several apps and emulators. this is not a diss at relax or xns, but i find that if one does the job and doesn't require any additional software to be installed on the pc side, then others aren't required- so please no flames

samba requires that the stuff you want to stream has to be in shareable folders so before i start i'll set out the pc requirements and settings.

----------------
pc/computer
to share a folder on your pc (i'm going to explain it for xp- i'm not sure if it is any different for 98 or me/2000) right click a folder containing stuff you want to share/stream and select "properties". choose sharing and then tick the "share this folder on the network". you are then given the option of changing the share name from what it's called on the pc- that bit's up to you. either way, you will need to note what that name is (the one that appears in the "shared name" box).

the other things you will need to know are your pc's "name" and the "workgroup" it belongs to (to find both of these out, right click "my computer", choose properties and select the "computer name" tab- the "name" is the what xp calls the "full computer name" (without the . at the end), the workgroup should be fairly evident).

some apps will also require the "username"- easiest way to find this out is to get up the task manager and check the users tab and see which one is active

for these examples i'm going to use the following values
workgroup- home
computer- my-computer
username- user

you may also need to know the ip address- i'll use 192.168.0.1 for the pc's ip: haven't come across an app that handles ip's only- and because i'm using dhcp i use the computer name rather than ip because the computer name is far less likely to change whereas the ip may change

the share names for the folders i'm going to share and a brief description of them are:
movies- movies on my-computer
pics- pictures on my-computer
music- music on my-computer
games- games (that i have the originals for) on my-computer- which contains different rom directories and an xbox folder
dvd- dvd-rom drive on my-computer (xp will give you a warning when you try and share a root directory- just ignore it-you can't delete things on a rom drive anyway)

these folders can have further subdirectories- unless you actively prevent subdirectories being shared.

if you decide for whatever reason to password protect these shared folders then also note the usernames and passwords
for the different folders- i personally don't bother, no xbox apps actually ask you for the password- they are in the samba path and therefore don't prevent anyone using your xbox accessing those folders- there is currently no way that i know of, for asking for the pass word when you try to connect.

----------------
xbmc
in this example i'll use a music share so scroll down the xboxmediacenter.xml and find the " <!-- my music shares !-->" line and below that look for the bit in the xml that looks like this:

find this excerpt

<bookmark>
<name>smb</name>
<!-- you can use the following formats: !-->
<!-- smb://domain;user: password@ip/share/directory/ !-->
<!-- smb://user: password@ip/share/ !-->
<!-- if guest/public access is enabled: !-->
<!-- smb://ip/ !-->
<path>smb://domain;username: pwd@mywindowsserver/movies/</path>
</bookmark>

with no username & password you can use the following:

<bookmark>
<name>music on my computer</name>
<path>smb://my-computer/music</path>
</bookmark>

it's that simple other ways to enable the share can be done as listed in the example above- but this is the simplest and works for me

now some people are having problems with playing cd's cos they haven't got a samsung drive- well remember how i made the dvd-rom drive shared? well this is why:

<bookmark>
<name>dvd-rom drive on pc</name>
<path>smb://my-computer/dvd</path>
</bookmark>

it will give you access to the pc's dvd drive. so now you can play all those avi's you burned on cd and vcd and svcd's from your pc drive. the only draw back is that xbmc can be made to autolaunch vcd's svcd's and audio cd's when inserted in the xbox drive- but as xbmc treats the pc drive over samba as a "folder" you will manually have to open up the dat files in a vcd-find the mpegav folder in the vcd and select the one or more dat files- if there are more than one dat files you can use the "stack" option on the left hand side of the file browser to make them play sequentially without stopping.

i would paste the dvd-rom samba share in all of the different media menus (e.g. my videos, my music) because xbmc has preset cache levels that are different for pics (low), music (medium) and video (high)- if you only do it in my pictures and then try and open avi, the video may not playback or may be very jerky.

note that the name of the bookmark doesn't have to be smb, it can be what ever you want- probably best to mention the fact its on the pc somewhere in the name- but the icon for a streamed folder is different to an xbox hd folder.

you can have as many samba shares as you want. i have 3 for videos, 3 for music and 2 for pics- one of each is a pc-
dvd-rom drive

pc tweaks
if you really want you can create "special folders which serve as links to the contents of another folder" using the this program.

you basically create a virtual folder that houses two or more separate folders- e.g. for the emulators maybe a c:\roms and d: (dvd-rom drive). it's your call, i personally don't bother- but would be interested to hear how well it works

[Gamester17]

are you experience error-messages or lost connections when streaming from a windows-based* computer?; here are a couple of tips:

- disable "allow the computer to turn off this device to save power" on your windows-based computers network-adapter/card from within windows.
  (control panel => system => hardware=> device manager => network adapters => properties (on your network-card) => power management).

- follow kb177078 (link) to create "irpstacksize" (if it doesn't already exist) and set it to 18 (as the default value 15 is sometimes not enough).

*windows-based meaning pc's running a operating-system from microsoft like windows 95/98/me/xp/2000/2003 (though 95/98/me are too old).

[wabidwoveren]

windows file sharing (also called samba, or smb). built into windows

great tutorial tslayer's favorite, and hosted by the xbox-scene forums
another great tutorial hosted on the xbmc online manual (wakka wakka)
general tutorial hosted by the xboxmediacenter forums

using windows xp home edition? then simple file sharing does not require a password.
using windows xp professional?

smb on windows seem a bit slow? some people reported success applying this patch.
smb on lunux/unix/osx seem a bit slow? some people reported success applying this patch.

if you can connect to winxp shares but you cannot browse the share then try following the troubleshooting tips in this guide:
http://www.techbuilder.org/recipes....le=true

[Metalmyth]

hi all

i have been using the latest cvs's for about a month and a half now and have been noticing really choppy performance when trying to play backed up dvd's from a network share (i use smb) i messed with the cache settings, renamed vob's to avi's, disabled antivirus client, forced the network speed on the pc (win xp pro) from auto/auto to 100/full etc etc nothing short of transferring these files directly to the xbox hd would work. last nite i had opened a remote desktop session to my pc from my laptop which hosts the backups.. and the dvd that was playing all of a sudden stopped being choppy  it made no sense to me either. after a lot of messing around and sheer luck i uninstalled the "qos packet scheduler" service from the tcp/ip stack on my pc (properties for local area connection on your pc) and now everything works like a dream. i had never thought of trying this before as i had already applied the qos tweak as documented here:

http://www.speedguide.net/read_articles.php?id=158

i am not saying this will work for everyone...all that i am saying is this is what i found and thought i would share the info

[pike]

how to link/map several folders from different partitions in one single share in windows xp/2000/2003 (ie using "symbolic links", a.k.a. "symlinks", a.k.a. "junctions"):

on my bootvolume c:\ i created a dir called !junctions!(donotdelete). this dir i shared, gave xbox user (a local user i created) permission and also gave xbox security permissions.

junction.exe

win2k's version of ntfs supports directory symbolic links, where a directory serves as a symbolic link to another directory on the computer. for example, if the directory d:\symlink specified c:\winnt\system32 as its target, then an application accessing d:\symlink\drivers would in reality be accessing c:\winnt\system32\drivers. directory symbolic links are known as ntfs junctions in win2k. unfortunately, win2k comes with no tools for creating junctions - you have to purchase the win2k resource kit, which comes the linkd program for creating junctions. i therefore decided to write my own junction-creating tool: junction. junction not only allows you to create ntfs junctions, it allows you to see if files or directories are actually reparse points. reparse points are the mechanism on which ntfs junctions are based, and they are used by win2k's remote storage service (rss), as well as volume mount points.

if you want to view reparse information, the usage for junction is the following:

usage: junction [-s] <directory or file name>

-s recurse subdirectories.



if you want to create or delete a junction, use junction like this:

usage: junction [-d] <junction directory> [<junction target>]

to delete a junction specify the -d switch and the junction name.

now, besides the info above, if you try and delete a junction the normal way you would delete a file,
all the shared files within are also deleted
so to put it bluntly: it's not n00b friendly
here is the dl link: >>>>>_<<<<<.

moving on.

inside my !junction! etc dir i made 3 subfolders. music, videos, pictures. you enter a commandprompt, cd into (ex) the music folder then type

junction d-mp3 d:/mp3

to create your first junction.
the "original" folder you targetted the junction at, may also require that you set "security permissions" to user xbox, there's no need to share this folder though.

using this method, there's no need to share whole drives to access everything.

the smb bookmark in xboxmediacenter.xml / my music then are:
<path>smb://xbox:[email protected]/junctions/music/</path>
and when u click on smb under "my music" it lists all the junctions you created under music

ps! there are alternatives to windows symbolic links (junctions), two of those alternatives are "link magic" and "winbolic link", both are third-party applications.

hope something of what i wrote above is helpful to someone / pike

[Gamester17]

are you experience slow throughput/load-times/browsing when streaming video/audio over wired or wireless-network?, here are some hints and tips:

general (both wired and wireless):

- disable samba-debug-logging in xboxmediacenter.xml, (logging takes many resourses, should only be used during active debugging):

  <samba>
<workgroup>whateverworkgroupname</workgroup>
      <winsserver>xxx.xxx.xxx.xxx</winsserver>
      <debuglevel>0</debuglevel>
  </samba>

- disable standard xbmc error-logging in xboxmediacenter.xml, (should only be used during active debugging/troubleshooting anyway):

  <loglevel>2</loglevel>

- if your computers operating-system is windows based (like 95/98/me/xp/2000/2003) then follow/perform this tweaks:
    * follow this tweakxp.com (link) register tweak to change the dir commad's buffer from 14000 to 65000 to raise the cache.
    * uninstalled or reconfigure the "qos packet scheduler" service from the tcp/ip stack under properties in local area connection;
       (alernative 1: in windows => control panel => network connections => local area connection => properties => uninstall).
       (alernative 2: lower or disable the amount of bandwith reserved for qos, do this by following the last article in this link).
    * tweak the dns errors caching in windows by following the first in this url (link)) to speedup/fix failed dns lookups .

- if your computers operating-system is unix based like linux or freebsd then follow/perform this tip to change transmission area window (link).

- in windows make you you 'unmount' (or disable) all virtual cd/dvd-rom drives (ex. from daemon-tools, alcohol 120%, clonedvd/clonecd, etc.).

- during smb streaming troubleshooting you should of course also (temporarly) try disabling any antivirus and firewall softwares on your computer.


wired specific tips:

- force from "auto-detect speed" to "100mbps/full-duplex" becuase it disables auto-negotiation which can sometimes slow network connections,
(in windows xp => control panel => network connections => local area connection properties => configure... => advanced => link speed...).


wireless specific tips:

- if your wireless access-point/router/adapters are 802.11b then upgrade (buy! all to 802.11g, 802.11g+ or 802.11a equipment instead.
  (802.11b real throughput is usually bellow 1mb/second which is too slow. if you want to get good wireless get 802.11g+ with mimo).

- disable wep/wpa encryption (as it increases overhead which lowers throughput), and enable mac-address filtering as security instead.


ps! if nothing of the above helps then test xbmsp/ccxstream/ccxgui (or alternativly xns) protocol and client instead of smb/samba as it have much less overhead :hmm:

[Aikinai]

i saw a lot of threads about people with choppy videos over smb shares and i just solved the same problem for myself so i thought i'd post it. it sounds like there are a variety of causes for the skipping so this might not work for you, but if your cache is always sitting at 0% it's worth a shot.
http://www.petri.co.il/speed_up_network_...ows_xp.htm
i just found this site which has some information on speeding up filesharing. i don't have a network card where i can change the interframe gap so i just added the registry key he has for a workaround. i think i just don't have a good network card because some videos can still have a cache struggling below 80%, but at least now it never goes to 0%.
i don't understand the problem or the solution so i can't help anyone with specifics, just wanted to let you know it worked for me.