You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
HI, I believe I have a work-around/solution or the reason for the recent problem of being disconnected while trying to Teleport. What I have done ...and so far it hasn't failed yet... is to use a different DNS Server address. Not "Obtain DNS Server Address Automatically" but "Use The Following DNS Server Address". I'm not sure, but I think the problem has something to do with being able to look up the new address of the place you are going to TP to. Something about "Obtain DNS Server Address Automatically" isn't working with Second Life and Teleports. I don't know if it's a problem with a person's ISP or with LL, but using different DNS servers ( I have been using 68.94.156.1 and 68.94.157.1) has stopped the Teleport Disconnect problem. I hope this is the right place to post this. I didn't know of another way to tell LL what I think I've found out. I hope this helps. Thank you, Danraka Resident
Possible Work-Around/Solution or Reason for "Darn Teleport Disconnects"
Type
Bug
Priority
Unset
Status
Closed
Resolution
Duplicate
Reporter
Danraka (danraka)
Created at
2019-04-14T17:03:07Z
Updated at
2019-04-18T18:05:11Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Simulator',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'HI, I believe I have a work-around/solution or the reason for the recent problem of being disconnected while trying to Teleport. What I have done ...and so far it hasn\'t failed yet... is to use a different DNS Server address. Not "Obtain DNS Server Address Automatically" but "Use The Following DNS Server Address". I\'m not sure, but I think the problem has something to do with being able to look up the new address of the place you are going to TP to. Something about "Obtain DNS Server Address Automatically" isn\'t working with Second Life and Teleports. I don\'t know if it\'s a problem with a person\'s ISP or with LL, but using different DNS servers ( I have been using 68.94.156.1 and 68.94.157.1) has stopped the Teleport Disconnect problem. I hope this is the right place to post this. I didn\'t know of another way to tell LL what I think I\'ve found out. I hope this helps. Thank you, Danraka Resident',
'What were you doing when it happened?': 'Teleporting',
'What were you expecting to happen instead?': 'Teleport and stay connected',
'Where': 'Any Teleport to any Sim.',
}
The text was updated successfully, but these errors were encountered:
Hi again...Well maybe I should make this a bit more clear. I don't think this is a "DNS Problem" per-say but rather a problem with the "Obtain DNS Server Address Automatically" operation and Second Life Teleports and Boundary crossings. In the LL blog post " Darn Teleport Disconnects" they wrote "(it seems to be a timing-sensitive failure in the hand-off between one simulator and the next)." I think it's possible that using "Obtain DNS Server Address Automatically" can create a "timing-sensitive failure" and that using your own, set, DNS servers is more direct, faster and timing-sensitive.
A bit of history...
In the past I was using a slow WIFI connection and would often be disconnected trying to Teleport. (Exactly what is going on now.) I thought that maybe using different, fixed DNS servers ( "Use The Following DNS Server Address" ) might speed up my internet a bit, in general. I wasn't even thinking about Teleport Disconnects at the time, or trying to fix it. I just wanted a little quicker Internet. Well... I then started to notice that I was never being disconnected trying to TP. Well this is interesting, so I went back to "Obtain DNS Server Address Automatically" and the Teleport Disconnects came back...Just like before. So, I return to using "Use The Following DNS Server Address", and again, never being disconnected trying to Teleport.
Fast Forward (Teleport) to today...
I have recently gotten a Fiber Optic internet connection (1000mbps... OH thank God!... lol) And thinking that with this new high speed, super fast connection, I shouldn't have any problems what so ever. So... I changed it back to "Obtain DNS Server Address Automatically" and guess what started to happen?.... Yep, I was getting disconnected trying to Teleport, just like everybody else...Just the same way in the past. So...I returned to "Use The Following DNS Server Address" and guess what?... Yep, I haven't been disconnected Teleporting yet....Just like in the past...Just Saying 😜
So... once again, I don't think this is a "DNS Problem" per-say but rather a problem with the "Obtain DNS Server Address Automatically" operation and Second Life Teleports and Boundary crossings.
What just happened?
HI, I believe I have a work-around/solution or the reason for the recent problem of being disconnected while trying to Teleport. What I have done ...and so far it hasn't failed yet... is to use a different DNS Server address. Not "Obtain DNS Server Address Automatically" but "Use The Following DNS Server Address". I'm not sure, but I think the problem has something to do with being able to look up the new address of the place you are going to TP to. Something about "Obtain DNS Server Address Automatically" isn't working with Second Life and Teleports. I don't know if it's a problem with a person's ISP or with LL, but using different DNS servers ( I have been using 68.94.156.1 and 68.94.157.1) has stopped the Teleport Disconnect problem. I hope this is the right place to post this. I didn't know of another way to tell LL what I think I've found out. I hope this helps. Thank you, Danraka Resident
What were you doing when it happened?
Teleporting
What were you expecting to happen instead?
Teleport and stay connected
Other information
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: