Streamerp2p Forum

I upgraded all my machines to the new 1.44 version. It seemed quick and painless on my broadcast machine, as it kept the bconfig and went right back to broadcasting... two stations that had been connected right before I shut down, immediately reconnected.

BUT I cannot connect on either of my two other machines on my LAN. My station never seems to leave the "recently online" category. I can connect to other stations that are online however.

Perhaps this will fix itself when other users/stations upgrade, but I do not know. I checked into the lobby and asked if anyone else is having problems and one guy says it's eating up his bandwidth...

I'll try some more things and see what I can find...

Thanks for all the struggles, guys... troubleshooting is a female dog.

Kevin

I did a fresh install and then recopied the bconfig from back up... As well as fresh installs on the other two machines. I also had to reset up the firewall/no proxy and FINALLY I got it going... I can now listen on my LAN machines... sort of.

When I try it again after letting it set... it's sometimes having trouble again. It seems to connect but then goes into "Buffering 0%". Sometimes if I let it set long enough, it'll finally start playing. But other stations in the "Online" category connect right away. I don't get it. I've also noticed that if I DO finally get connected, when I DISconnect, it may take 30 seconds for the connection to disappear over on the broadcast machine, but not always. That seems much longer than before.

So what I did may have nothing to do with it. I'm starting to think it must be the network getting straightened out as I said in the last post... I'll leave it alone and see how it is tomorrow.


Kevin

I posted this elsewhere but I'll post it again. The private lan prioritization code has not been perfected yet and as a result, you will have intermittent success at listening to your own broadcast on your own private subnet at this time. Your listners outside on the public network should not be having the same issues as they are on a different network.

If you only want to monitor your stream you can connect your player to the audio port configured in streamer (default port 8000).
for example:
http://localhost:8000/streamer.mp3
http://localhost:8000/streamer.ogg
http://localhost:8000/streamer.aac
http://localhost:8000/streamer.nsv

Or replace the 'localhost' with your lan ip.

KMeat: I've never read that before... thanks.

D-Tracks: I have a second MP3 server anyway, but thanks... good info.

A listener sent me a screen capture of the Streamer list saying I had 51 listeners... ???????? That obviously can't be true, so wondering if that is something needs reporting.

thanks,

Kevin

i'm using version 44 a few days now and i get only troubles
as soon as i start streamer
all my other lan users cant internet anymore
with the old versions all went smooth i could stream and even have a other copy running for monitoring and also other user on my net could internet without having time outs

all of a sudden my modem cant cope it anymore
:hmm:

sounds like a problem with the router. Not that its damaged but most home office routers have a connection limit (max open tcp/udp connections). Since p2p applications open many connections the routing table gets full and no other connections are possible. Check this out. Just a guess... Look if there is a way to increase the connection limit or to set a lower timeout (time until the router drops the routing information). Read the support forums for your router and look for problems with file sharing applications. Mostly the same problem

thanks d-tracks i copy with you wrote
searched abit on google and couldn't find a tweak for the sitecom dc-214 modem

but i found a solution for my problem
i solved it by using a other version of streamer
everything runs like it was ...bye bye timeouts