|
Sierra Sugar
Registered User
Join date: 14 Mar 2005
Posts: 10
|
10-06-2007 18:35
This didn't used to be problem. But I've noticed the past couple of weeks that if I have SAM broadcaster running and actively connected to a stream streaming music I cannot log into SL. So, if SL crashes in the middle of a show I cannot log back in UNLESS I stop the stream, log in, and then reconnect. Anyone else having this problem? And is there a solution? Its not always an option to disconnect the stream just to be able to log in, especially with SL's notorious instability.
|
|
Sierra Sugar
Registered User
Join date: 14 Mar 2005
Posts: 10
|
10-08-2007 02:37
Does no one have any information on this? I've been looking and looking and can't seem to figure out the problem.
|
|
Malia Writer
Unemployed in paradise
Join date: 20 Aug 2007
Posts: 2,026
|
10-08-2007 09:21
Have you tried alternate SL clients, such as the Nicholaz viewer? These can be less of a memory hog so might help...
|
|
Talon Brown
Slacker Punk
Join date: 17 May 2006
Posts: 352
|
10-08-2007 11:14
Yeah, I'd agree with Malia. Sounds like SAM and SL are fighting for either the same bandwidth or computer resources. Given that you're running a stream I'd check into how much of your upload bandwidth SAM is using, it could be that the SL client isn't able to get enough data through to login.
|
|
Sierra Sugar
Registered User
Join date: 14 Mar 2005
Posts: 10
|
10-08-2007 11:28
But why would it suddenly be an issue now? I've used SAM and SL together for 2 years without a problem. And with the radio station I don't have a choice but to use SAM while streaming due to station scripts and such that are written to work in conjunction with SAM for the DJs. Like i said, this was never an issue up until a couple weeks ago.
|
|
Talon Brown
Slacker Punk
Join date: 17 May 2006
Posts: 352
|
10-08-2007 12:21
Hmm, I'm not sure why it would suddenly be an issue. Has anything about the system configuration changed? One other possible suspect, SP2 for Windows XP severely limited the number of concurrent TCP/IP connections to 10 which can cause all sorts of problems, including apps being unable to properly connect to servers. You can check to see if this is your problem by accessing the System Log in the Event Viewer. (Control Panel/Performance and Maintenance/Administrative Tools/Event Viewer, if you didn't already know where to find it.) Look for any Warnings regarding Tcpip event 4226.
If you find those warnings, either your normal programs are suddenly hitting this limit and are unable to properly connect (not always with any warning either) or you've gotten some type of virus/trojan trying to call home and hitting the limit, causing the same issue.
|