Kharlis Zepp

The situation seems to have been resolved. Secondlife.com is available again, and I can login to the grid again. I wonder if the rolling restarts that occurred today were the result of that. Thanks everyone for their assistance. Learned a few more things about networking than I did before at least. Tracing route to secondlife.com [216.82.2.17] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 8 ms 7 ms 6 ms L100.CITY-VFTTP-21.verizon-gni.net [W.X.Y.Z] 3 12 ms 8 ms 7 ms G10-3-221.CITY-LCR-02.verizon-gni.net [130.81.139.234] 4 17 ms 22 ms 21 ms P15-0-0.CITY-LCR-01.verizon-gni.net [130.81.27.64] 5 16 ms 16 ms 15 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.248] 6 24 ms 21 ms 14 ms 0.ae1.BR1.IAD8.ALTER.NET [152.63.32.141] 7 18 ms 14 ms 28 ms ae17.edge1.washingtondc12.level3.net [4.68.62.137] 8 14 ms 17 ms 15 ms vlan51.ebr1.Washington12.Level3.net [4.69.146.190] 9 23 ms 27 ms 26 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105] 10 27 ms 24 ms 24 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241] 11 49 ms 46 ms 47 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21] 12 54 ms 51 ms 52 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133] 13 52 ms 302 ms 251 ms ae-11-60.car1.Dallas1.Level3.net [4.69.145.3] 14 95 ms 46 ms 47 ms LINDEN-RESE.car1.Dallas1.Level3.net [8.9.232.94] 15 50 ms 49 ms 51 ms sw-core1-73.dfw.lindenlab.com [216.82.7.174] 16 47 ms 47 ms 46 ms vip.www-dfw.secondlife.com [216.82.2.17] Trace complete. 

Well, to contact support would mean going to secondlife.com, which is out. I guess I'll have to take my laptop for a drive down to the local Starbucks or something. There are a number of people posting to the JIRA about this issue, which of course they're turning down, since it's not a bug. But that tells me that I'm certainly not the only one having this issue. I'd like to know if any of them are using anything other than Verizon FiOS. If that's the case that that rules out the ISP's involvement, maybe. Glad that I'm not a major sim owner, or provide a service or anything like that or I'd be just plain out of luck I guess. I do have a rental property that I guess I'll have to either let lapse or pay from another location till this gets resolved.

Fair enough, but I'd still like to point out that the secondlife.com website is also not responding. The WEB SITE on my web browser Firefox, is not responding. I can access this web site because it's not related in any way to secondlife.com. It doesn't work on any other computer I have in my house. Nor on my laptop that I have running Windows XP. The other comptuers run Windows 7. And again it's also the only site I go to that isn't working at the moment. Yahoo, google, Woot!, Newegg, you name it. Everything works. Just not secondlife the website, the grid, what have you. I've tried logging into another region. I've tried using an alternate login server. I've tried logging into a whole different account. Nothing works.

That makes sense. Yeah you wouldn't be able to tracert on the other side of a DMZ if someone set one up. Anyway, just checked with JIRA. They're getting users complaining about this, but they say it's not a JIRA issue since it's not a bug. Best bet is to contact support and make a ticket, which I can NOT do since I cannot access secondlife.com right now. I guess that also means I can't suspend my account either and stop paying for a service I cannot get, so I'm forced to keep paying for it too. Interesting.

It's possible that the hosts on that end just don't respond to ICMP requests, but it's odd to do a tracert and not get a full list when you can do it with yahoo or google or microsoft or pretty much anyone else. The fact that it does time out around that area though pretty much makes me believe that I'm in the 'sucks to be me' category. But I'm quite convinced that there's something wrong on the LL side of things that's keeping the connection from working properly. The question is, how many users is it affecting for them to do anything about it.

I cleared the DNS cache when I changed the primary DNS server on my adapter. All the DNS servers seem to all point me in the same direction to nowhere. Also I thought about the mesh update putting a wrench in everything, but even that wouldn't explain why I also cannot access secondlife.com at all. Also remember that I can resolve the DNS address just fine. It's just not responding for some reason. Pinging vip.login.agni.lindenlab.com [216.82.2.9] with 32 bytes of data: Request timed out.  Pinging secondlife.com [216.82.2.17] with 32 bytes of data: Request timed out. And yes of course it could be set to drop ICMP packets, which it should. But it at least shows that I'm resolving the address. Anyway, I am absolutely baffled by this. It was working just fine last Friday. I was in a sim listening to a stream, the sim crashed but I kept listening to the stream for a few hours. Next day since then there's been no pulse to second life. ISP modem has been reset. DNS servers have been changed and flushed out. Every other website that I frequently go to loads just fine. But then again I don't see anyone else complaining about not being able to log on either. So I guess I'm the only one affected by this. Thankfully I've paid my rent on my rental plot through the next few weeks, because it seems like I'll be on hiatus for a while.

Opened up port 53 to TCP. Already open for UDP. Opened up for port 80 and 443 on TCP, no rule on it before. No rules on any of the other ports SL specifies. Still the same result. Can't load secondlife.com, can't get on the grid. Another computer in the house has the same symptoms. Think I'm the only one who can't login to SL at the moment!

Alright so far I've tried Google, Level 3, OpenDNS, Dyn, and I get the same results. It resolves the address, it just takes too long to respond. Ping always times out. All the public DNS servers try to route me through the same route too it seems. Washington to Atlanta the down to Dallas and it just dies shortly after that. Second life is the only online service that I seem to be having problems with too.

Haven't been able to log into Second Life for the last few days. I did a traceroute to the login server, and it seems to go south around the level3 part of the network. I believe I'd read somewhere that this meant this was an issue with Lindon Labs and not the user or the ISP. Could someone please tell me what's up, if there's a known issue, or maybe a workaround? I can't even access secondlife.com at all. Here's a copy of my traceroute to login.agni.secondlife.com Tracing route to vip.login.agni.lindenlab.com [216.82.2.9] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 8 ms 7 ms 6 ms L100.CITY-VFTTP-21.verizon-gni.net [w.x.y.z] 3 6 ms 7 ms 8 ms G10-3-221.CITY-LCR-02.verizon-gni.net [130.81.139.234] 4 15 ms 12 ms 11 ms P15-0-0.CITY-LCR-01.verizon-gni.net [130.81.27.64] 5 10 ms 14 ms 15 ms so-15-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.248] 6 14 ms 14 ms 14 ms 0.ae1.BR2.IAD8.ALTER.NET [152.63.34.21] 7 16 ms 14 ms 17 ms ae16.edge1.washingtondc12.level3.net [4.68.62.133] 8 14 ms 15 ms 14 ms vlan51.ebr1.Washington12.Level3.net [4.69.146.190] 9 28 ms 26 ms 27 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105] 10 27 ms 28 ms 27 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241] 11 * * * Request timed out. 12 53 ms 51 ms 52 ms ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169] 13 51 ms 52 ms 52 ms ae-41-90.car1.Dallas1.Level3.net [4.69.145.195] 14 * * * Request timed out. 15 47 ms 50 ms 49 ms sw-core1-73.dfw.lindenlab.com [216.82.7.174] 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.