Client login probblem
|
Petaris Hightower
Registered User
Join date: 15 Feb 2006
Posts: 6
|
06-05-2006 10:46
Version: SL 1.10.1 (0) OS: Debian testing Info: After hitting "connect" I get this in the terminal window:
2006-06-05T17:40:41Z INFO: Attempting login as: Petaris Hightower 2006-06-05T17:40:41Z INFO: Current Directories: 2006-06-05T17:40:41Z INFO: CurPath: /home/petaris/apps/SecondLife 2006-06-05T17:40:41Z INFO: AppName: SecondLife 2006-06-05T17:40:41Z INFO: ExecutableFilename: secondlife-bin 2006-06-05T17:40:41Z INFO: ExecutableDir: /home/petaris/apps/SecondLife/bin 2006-06-05T17:40:41Z INFO: ExecutablePathAndName: /home/petaris/apps/SecondLife/bin/secondlife-bin 2006-06-05T17:40:41Z INFO: WorkingDir: /home/petaris/apps/SecondLife/bin 2006-06-05T17:40:41Z INFO: AppRODataDir: /home/petaris/apps/SecondLife 2006-06-05T17:40:41Z INFO: OSUserDir: /home/petaris/apps/SecondLife 2006-06-05T17:40:41Z INFO: OSUserAppDir: /home/petaris/apps/SecondLife/SecondLife 2006-06-05T17:40:41Z INFO: LindenUserDir: /home/petaris/apps/SecondLife/SecondLife/Petaris_Hightower 2006-06-05T17:40:41Z INFO: TempDir: /tmp 2006-06-05T17:40:41Z INFO: CAFile: /home/petaris/apps/SecondLife/app_settings/CA.pem 2006-06-05T17:40:41Z INFO: SkinDir: 2006-06-05T17:40:41Z INFO: LLControlGroup::loadFromFile unable to open. 2006-06-05T17:40:41Z INFO: Resolving Agni userserver domain name userserver.agni.lindenlab.com 2006-06-05T17:40:41Z INFO: ...Userserver resolved to 66.150.244.151:12036 2006-06-05T17:40:41Z INFO: Verifying message template... 2006-06-05T17:40:41Z WARNING: LLCircuitData::checkCircuitTimeout for 66.150.244.151:12036 last ping 151.373 seconds ago. 2006-06-05T17:40:41Z WARNING: LLCircuitData::checkCircuitTimeout for 66.150.244.151:12036 still dead, dropping. 2006-06-05T17:40:41Z INFO: LLCircuit::removeCircuitData for 66.150.244.151:12036 2006-06-05T17:40:46Z INFO: Resending on timeout 2006-06-05T17:40:47Z INFO: LLCircuit::addCircuitData for 66.150.244.151:12036 2006-06-05T17:40:47Z INFO: Verifying message template... 2006-06-05T17:40:52Z INFO: Resending on timeout 2006-06-05T17:40:52Z INFO: Verifying message template... 2006-06-05T17:40:57Z INFO: Resending on timeout 2006-06-05T17:40:57Z INFO: Verifying message template... 2006-06-05T17:41:02Z INFO: Resending on timeout 2006-06-05T17:41:02Z INFO: Verifying message template...
and this popup:
Unable to connect to Second Life. The system may be down. Please try again in a few minutes, or click Help for advice and a link to the system status web page. ------ OK ---- Help -------
If I click help I get this in the terminal window:
load_url: /home/petaris/apps/SecondLife/help/unable_to_connect.html
But nothing happens, if I open it manually and click on the server status link the page states that second life is open.
Any help would be appreciated.
|
Petaris Hightower
Registered User
Join date: 15 Feb 2006
Posts: 6
|
06-06-2006 10:36
Is Second Life expecting a perticular port to be open for communication with the server?
I am thinking that maybe my firewall is blocking something.
Thanks,
_____________________
- Petaris
"The World is Open. Are You?"
|
Petaris Hightower
Registered User
Join date: 15 Feb 2006
Posts: 6
|
06-06-2006 10:50
Ok, I found the firewall requirments and have adjusted the rules accordingly but it still doesn't let me login. Just to be sure here are my firewall rules: (for a shorewall based firewall box)
ACCEPT net loc:172.20.5.11 tcp https ACCEPT net loc:172.20.5.11 udp 12035:12036 ACCEPT net loc:172.20.5.11 udp 13000:13050
This should be correct right? I am assuming the faq would have said if port forwaring was required.
Thanks,
_____________________
- Petaris
"The World is Open. Are You?"
|
Darkside Eldrich
Registered User
Join date: 10 Feb 2006
Posts: 200
|
06-06-2006 14:55
Strange, my firewall isn't preventing anything, SL-wise, and it's mostly defaults (+ssh and svn forwarded to my machine).
|
Petaris Hightower
Registered User
Join date: 15 Feb 2006
Posts: 6
|
06-07-2006 08:59
I'm fairly sure that my firewall is not the problem as I did open those ports (out) but I could be wrong. When logging in on the client I get the "Verifying Protocol Version" screen for a few momments then the error message:
Unable to connect to Second Life. The system may be down. Please try again in a few minutes, or click Help for advice and a link to the system status web page. ------ OK ---- Help -------
Still always with this in the terminal at that point:
2006-06-05T17:40:47Z INFO: Verifying message template... 2006-06-05T17:40:52Z INFO: Resending on timeout 2006-06-05T17:40:52Z INFO: Verifying message template... 2006-06-05T17:40:57Z INFO: Resending on timeout 2006-06-05T17:40:57Z INFO: Verifying message template... 2006-06-05T17:41:02Z INFO: Resending on timeout 2006-06-05T17:41:02Z INFO: Verifying message template...
_____________________
- Petaris
"The World is Open. Are You?"
|
Merrick Moose
Registered User
Join date: 20 Oct 2005
Posts: 191
|
06-07-2006 09:02
From: Petaris Hightower I'm fairly sure that my firewall is not the problem as I did open those ports (out) but I could be wrong. When logging in on the client I get the "Verifying Protocol Version" screen for a few momments then the error message:
Solve the problem really quick. Remove the firewall completely, easily done if it is a hardware based one. Try to log on. If it works then the firewall is the problem, if it still errors give your findings here.
|
Petaris Hightower
Registered User
Join date: 15 Feb 2006
Posts: 6
|
06-07-2006 10:02
Unfortunatly removing the firewall is not an option, I would loose all connection to the router.
_____________________
- Petaris
"The World is Open. Are You?"
|
Merrick Moose
Registered User
Join date: 20 Oct 2005
Posts: 191
|
06-07-2006 10:25
From: Petaris Hightower Unfortunatly removing the firewall is not an option, I would loose all connection to the router. The connection (host look up to IP) is done with TCP, though once the SL tries to get going with UDP it looks like it is dying. Your router or firewall is stopping UDP packets from what it looks like. It's the best guess I have for you with out knowing any more details than you have posted. High traffic routers drop UDP in favor of TCP, or the firewall and/or router don't forward them for your network.
|
Petaris Hightower
Registered User
Join date: 15 Feb 2006
Posts: 6
|
06-07-2006 11:00
Fixed! I had allowed those ports in instead of out. Duh! Thanks for your help! 
_____________________
- Petaris
"The World is Open. Are You?"
|
Stevex Janus
Registered User
Join date: 27 May 2007
Posts: 3
|
Firewall settings
05-27-2007 02:37
It looks like the client allows you to specify which UDP port that it uses for communications with the servers. If you click on the Preferences button, and then "Network" you can select "Custom Port Connection"
It starts at 13000. But recently something changed and you even though you select 13000 data goes in/out on port 13001.
If you don't use this setting, every time the client starts up you will have to find out which port it will use, and update your firewall settings all the time.
Max
|