|
|
|
[
Permlink
| « Hide
]
Ford Dharnen added a comment - 21/Apr/08 02:45 PM
I'm having the exact same issue with SL crashing either my LinkSys router or my Netgear wireless adapter. Usually when I log in my connection speed it 54Mbps, but after res'ing my speed drops to 1Mbps before outright crashing. I usually have to reset both the router and or the PC but when I try to log in it does it again. Once I close SL my adapter resumes connection to the router at the exact same connection speed as before it crashed. I'm also using AVG 7.5 firewall, which is configured to allow all traffic for SL. The router is configured to allow all outgoing/incoming as long as logged in. Unfortunately I don't recall all my specs on the router as it's been a bit since I last had to modify it, and the adapter is on channel 6. I've not messed with the ports as since I can log into Guild Wars with no connectivity issues, that would seem redundant.
Per the Second Life System Requirements page - http://secondlife.com/corporate/sysreqs.php
"* Second Life is not compatible with dial-up internet, satellite internet, and some wireless internet services." Misfiled / resolved?!
My computer meets this requirements easily. I have been online for more than one year and did not change anything. The same is true for Ford Dhahem: SL does not work any more for us. I went through the system specs link posted and my computer meets all of those. The computer in question is running Windows XP Professional with 2 gigabytes of memory, has a GForce 4800 graphics card with 128 megs on card memory. I had initially got that card for use of rendering AutoCad designs at decent speed. The computer itself is at least a P3, and in the case of available hard disk space (for in case that gets brought up) I think 98 gigs should be sufficient. I went through all the preferences in the game, and even went as far as to set the cache size to maximum. I've been using the same wireless adapter on this computer for 2 years, the router has been configured and set for 4 so far, the router is a cable modem/router, and the computer I'm using is 1 room away.
In the case of this issue being listed as resolved/misfiled, could you please specify how that can be? I would guess from Rita's post, she knows what she is doing in configuration as well. I did ISP support for two years for a national chain, and dealt with DSL, dial-up, and direct link technical support. From how the software runs on my system I would say it's a software/driver/process conflict error, and would like to know how to resolve that so I might be able to get online for longer than a whole, at best, 3 minutes. Ford Can you please clarify what happens when you connect the computer directly to the router, without using the wireless adapter?
Changed priority to "Critical" – "Showstopper" is ONLY if it's confirmed to affect a lot of Residents. Sorry to hear you're having problems with this, but the cause (whether it's SL-specific or something else) needs to be determined.
As Thurston asked, please be sure to try without your router. I've been having this problem for a week now. I haven't changed anything about my computer or router, but suddenly whenever I start SL, my internet connection is killed and the only thing that fixes it is a restart of my computer.
Grimace, please see these articles in Knowledge Base How can I improve performance ?
This article will show you how to get detailed information about the performance of your computer and the Second Life world Statistics Bar Guide Please try the latest RC Viewer which can be downloaded from here Release Candidate Test Viewers If this is still an issue please post a Ticket with Support Thank you : ) Since April 16, I have been dealing with this very same problem: logging into SL resets/crashes my Netgear CBVG834G modem-router. The problem arose out of the blue: I personally changed no system or modem-router settings. It would be interesting to read if the issue has been resolved for the people who commented on it in the past, and, when affirmative, through what means.
sorry to hear that!
For me it is resolved since long. I have a Netgear WNR 834 B. You can try to use the very lastest Netgear driver, but I bet the reason for the problem is the SL software again. What increases the stability per se is a quick connection. Rita Thanks for your comment Rita.
As I report in thread Quote from my comment in above mentioned thread "While it is a fact that Netgear appears to be cited in most all occurrences of these modem-router resets-crashes, and that this as such certainly seems to point to a brand sensibility, it is not clear to me whether the problem started occcurring because of a bug in a daily firmware update from my Internet Provider or because of a change in the protocol of handling the voice chat data transmission on the side of Linden Labs." As for your comment on the quick connection and the software quality, I have an ethernet 30MB cable connection, which for as much as I can appreciate, should be able to deal the cards just fine. How interesting!
I have dissabled voice chat as well. All the time. It just was enabled long ago - once by an upgrade of SL, which had this as default setting. 300 MB... pretty quick. I think, that 300 MB really should be enough for a computer game! What I am not happy at all are the comments of the Lindens in this thread: Rita Hi.
Current configuration: Processor: Intel Pentium IV Prescott 3.4Gghz (Hyperthreading) This problem only came up when i installed the router. Before that i had a Thomson THG540 Cable Modem. Both router and Modem are VoIP enabled. That's where i get my telephone service. With the Thomson modem, this problem never happened, now i can't use SL Voice. From all the testing i could do it seems to be some sort of incopatibility between the router and SL's Voice module. I also tested it on a diferent computer, and the same problem arised. I think that the anwer of "The problem is with the customer's hardware, or usage, or even connection" is not a good answer, after all i do Pay good money to play this game, wich, so far hasn't given me too much trouble. I was hoping that i could still enjoy SL in it's full extent. thank you everyone. I can now certify that the cause of the problem lies with the Netgear CBVG834G modem. After a hassle, my Internet Provider agreed to exchange it for a CastleNet modem, and, lo and behold, the problem was instantly solved. On an ironic note, thanks again to Linden Labs support for providing us with accurate problemshooting information. Take note of the fact that in all similar occurrences, a Netgear modem is cited.
Hi Gatekeeper,
i could try to hassle (big time) with my provider, but unfortunately, even if they agreed to change my gateway, they couldn't because they do not have any other equipment of this type to provide me with. After all, their answer would be: "This router works perfectly with everything but Second Life Voice, so off course we are not going to change the equipment." In my real life work i solve my customers internet access problems, in most cases i have complete management of the customer's routers, after all they are provided and maintained by my company. If a customer calls me complaining that his SL Voice does not work with the router we installed, we try to solve the problem by all means we can, but we do not exchange the router because there is nothing in the contract that specifies SL Voice working. What we could do, and that is just to provide a good service is try to figure out some sort of solution with the folks at Linde Labs. So my point is this: I Pay Linden Labs to play Second Life with voice, my router and computer meets up with every specification asked, so if SL Voice is not working, then Linden Lab has the obligation to his customers to fix this situation. After all i am paying to use everything in SL, including Voice, and i am not doing so because of some deffect in the software. Ficcionista - For technical support please contact support at http://secondlife.com/support
Hi Ficcionista,
Point taken. Neverhteless, consider this: (in my particular case) WITH the NetGear modem, Second Life ran normally (voice chat included) between January 21 and April 16. This fact, plus the fact that changing the modem solved the problem, indicates that EITHER a change in Linden Labs software (voice or other) OR a firmware update from the Internet Provider (I've been told my IP has daily updates), in combination with a vulnerability in the NetGear modem were the cause of the problem. Hi Gatekeeper,
i've been investigating the situation with the router. apparently this router is not sold as a residential product, Netgear provides this equipment directly to ISP's worldwide, and it often has a specific firmware created by the ISP. According to what i have learned from some forums and people i've talked to about this situation, the router does have some issues. It seems that it misinterprets some kinds of protocols as a DoS and shuts down because of it. But that only occurs when the router's firewall fuctions are active. In my case i have them all turned of. The router is currently only receiving the cable signal, converting/encaplusating it TCP/IP and sending it to two computer via UTP cable. I agree that there is something in the router's firmware or routing procedures that crashes whenever i enable SL Voice on any of my computers. However, there is also something in the source code or codecs used by Vivox (SL's voice module) that causes the router to reboot by overload, DoS, Flooding, or something of the sorts. Since it is a VoIP enablied router, it could well be some sort of conflicit between Vivox and the router's VoIP. Whatever the problem may be, SL Voice and the usage of Vivox is a responsability of Linden Labs and not of Netgear or my ISP. P.S: - I just opened a ticket in the Support Center. Let's see what answers come from there. :o) Ficcionista Pessoa,
it is well known that the Netgear CBVG834G issues are related to the firmware and Zon, Portugal cable network provider, is working on a fix for that (since long it is true!) I don't think Vivox or Linden have any responsability on this matter, because the roots of the problem have been clearly identified. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||