Page 1 of 1

continuous network usige After Accessing network shares

Posted: Wed Nov 21, 2007 9:06 pm
by AmIdYfReAk
this has had me baffeled for a littlebit now, when i am on my lappy, i can only use ~40% of 802.11G, so banwith it rather important when i am streaming movies and jazz..

But latly, after i navigate to the network share, and start the movie file in my local player ( media player classic/VLC ) it will play with no problems, untill it gets about ~3-4 mins in.
then the Video will become choppy and Audio will skip.

i will close the Player and my networkusige is pegged at 40%, i've left it for up to 15-20 mins and it continues to stay spiked. most of the movies are ~120mb, and it would have fully tranfired in less then 5 mins.

i've scanned for virii/spyware/grayware/etc and came up empty handed.

Any ideas?

Re: Continuis network usige After Accessing network shares

Posted: Fri Nov 23, 2007 3:35 am
by AmIdYfReAk
kinda a funny side note, if i get the SMB share path, then kill explorer and play the movie, it will play flawless and only use ~4-9% wile its at it..

kinda weird yet funny at the same time. :)

Re: continuous network usige After Accessing network shares

Posted: Fri Nov 23, 2007 5:13 am
by creep
Wish I had an answer for you. Windows is odd.

Re: continuous network usige After Accessing network shares

Posted: Fri Nov 23, 2007 6:48 am
by AmIdYfReAk
indeed it is, i am just tossing it out there..

i think its some wierd glitch with SMB..

Re: continuous network usige After Accessing network shares

Posted: Sat Nov 24, 2007 6:53 pm
by Hr.O
The other days when i was testing my network setup I found out that sometimes when i started a d-load and canceled it halfway the bugger kept on d-loading the whole file.

Re: continuous network usige After Accessing network shares

Posted: Sun Nov 25, 2007 5:07 am
by AmIdYfReAk
yea, this is basically the same idea, but its like its stuck in a loop... explorer that is..


its a wierd thing, and i only get it on this lappy.

the more i look, the more i think its somthing closer to a freekshow of an issue, i may end up reporting it as a bug, though i am not sure yet.