Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

'Verifying protocol version' / timeout / 'unable to connect'

Eddie Escher
Builder of things...
Join date: 11 Jul 2003
Posts: 461
10-17-2003 15:54
Last night and tonight I've not been able to get into SL. Its 11:30 GMT now, and when I log in, it only gets as far as 'verifying protocol version' for 20 seconds, then says 'unable to connect'. I was logged in earlier tonight (and last night) between 7 and 9pm.

Anyone else been getting this?

(I've sent a report)
_____________________
Eddie Escher
...apparently 3 out of 4 people make up 75% of the population here...

Eddie Escher Gadgets & Skins: Hotei and Seacliff
Bosozoku Kato
insurrectionist midget
Join date: 16 Jun 2003
Posts: 452
10-17-2003 16:06
Sounds like the network. Run a traceroute on "data.agni.lindenlab.com".

On the downloads page is a traceroute app that's available, as well there's others available on almost any file site. Or just use the one built into winblows.

For windows just start a command prompt (aka DOS) session, and type in:
tracert data.agni.lindenlab.com

If you're losing packets between you/your isp (first 1-5 or so hops typically), then contact your isp.

if losing packets between you/isp and the final hop (lindenlabs) it's a network problem, sometimes calling your isp can help, but don't hold your breath :)

If lindenlabs is the only hop that you can't reach, then it's linden's network/isp.

I suspect it's the network (middle area), which hopefully has cleared up for ya by the time you read this anyway.

Boso
Devlin Gallant
Thought Police
Join date: 18 Jun 2003
Posts: 5,948
Mr
10-18-2003 11:11
The only time I have ever had this particular error is when Sl is down/offline.
Eddie Escher
Builder of things...
Join date: 11 Jul 2003
Posts: 461
10-21-2003 08:58
Ty for the advice BK.
DG: SL's status page has consistently said it's open when I have this problem, so I knew it was something closer to my end.

Anyway, problem kinda solved...

It turns out to be the crappy cable modem - I have some friends who have the same model of NTL cable modem, and they say they have the same problems, but with other streaming data.

It seems that the modem can only handle so much data transfer per week before throwing a fit.

I have a flat ear from hanging on 'hold' when tring to ring NTL every night (only have 1 hour from getting home from work, and their support staff clocking off for the day, and after 3 nights I've still not go through) so I'm going to send multiple faxes every night instead I think.

NTL broadband = Not Terribly Likely
_____________________
Eddie Escher
...apparently 3 out of 4 people make up 75% of the population here...

Eddie Escher Gadgets & Skins: Hotei and Seacliff