No Teleport

I'm running Suse 10.1 x86_64 and with the latest alfa I can't Teleport anymore, with the older version there where no problems.
Does anyone have also this problem..???
If I do a teleport the system says treansfering and then I get disconnected.

Please help.....


gr. Richard

No teleport at all. 1_13_2_11 client just disconnects me.

Tried from 2 different machines with different connections, tried searching a place, clicking on the map, even getting requested by a friend - it simply disconnects. Of course, I didnt have that problem with the previous version.

Help! I'm stuck!

-----update--------

I'm stuck!

I've tried also the mac OSX client (both normal and firstlook) to no avail

tried all the tricks in http://secondlife.com/knowledgebase/article.php?id=348 to no avail

of course, clicking, searching, using the map, getting a tp offer by friends do not work too.

The failure on both linux and mac seems to point at a problem with my account and not with the viewer. However, this contradict Aarons' success with windows (message 7). No win here, so I cannot test.

Help!

It's not as bad here, but lets just say teleporting seems to be a matter of luck. There seem to be "safe routes though. I cant teleport from most locations to Neverwhere, but teleporting from Absence to Neverwhere always works... And i hate the slowdowns i get with the new client. before i experienced them only when a friend went on or offline. now they happen every now and then seemingly without any reason at all.

-Asriazh

Tried teleporting with the new client. It crashed GNOME and now my mouse is sluggish. Can't seem to get it back

At the time, when I start the teleport, I get these messages:

2007-01-18T16:09:04Z WARNING: updateMeshTextures: invalid host for object: 58a884fc-0c56-4a77-8e02-fae61b3e1e3f
2007-01-18T16:09:04Z WARNING: updateMeshTextures: invalid host for object: e2122b46-2835-47bd-a322-a8e3ac07995f
2007-01-18T16:09:04Z WARNING: updateMeshTextures: invalid host for object: 748c1ea9-cea4-4bea-9d5b-36ad4aa5fd5c
2007-01-18T16:09:04Z WARNING: updateMeshTextures: invalid host for object: 260310df-0f41-4706-b226-e50732e631e5

Than the TP seems to stuck. Afterwards, I get logged out.

Please fix soon, no Windows around here...

That doesnt' seem to be a Linux-only problem. I've got the same problem on Windows, then every thing worked fine after clearing the cache... a little bit later, same problem again. Clearing the cache seems not to help anymore. Maybe didn't really helped earlier. Imho it seems to be a problem with the grid itself. So just buy some tea, sit down, relax, drink it and.... wait. ^^

I may add that at the same time in the same network and even on a same machine (but also on another) SL works fine in Windows XP and 2000.

Are you running a peer filtering program like Peer Guardian? I had several problems with TPing for a while and it turned out one of the addresses was being blocked. Disable the program if that is the case.

My tp problem was due to the firewall situation reported now in the blog:

» If your firewall is blocking outbound TCP port 12043, teleports will fail. This is a very rare occurrence.

you'll have to check also

http://secondlife.com/knowledgebase/article.php?id=355

In substance, before the <<Capabilities, also known as "Sim-Caps">>, as from http://blog.secondlife.com/2006/12/21/a-big-change-youll-barely-notice/, my network configuration was working; now not so anymore.

I had to modify my router's configuration - as a consequence, I'll have to redesign completely my home network... oh well.. At least I understand now.

Thanks to everyone that helped/tried to help!

SuSE 10.1 (x86) with Nvidia card, old-ish P4 2.66 GHz and 1GB RAM. Since the last mandatory upgrade I have no teleport whatsoever, and I can't cross region boundaries. Can't be a firewall issue - there is no local firewall, only one protecting the whole home network, and the rule have not changed in months; plus, my Windows laptop works fine from inside the same home network (OK, SL kills the wireless connection every hour or so, but that's another issue).

This happens with both 1.13.2 viewers as well as the latest FirstLook client