Jump to content

Viewer 3.0.0 DNS host name error


You are about to reply to a thread that has been inactive for 4044 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

I cannot log-in to the SL viewer due to this error...

Unable to connect to Second Life.
DNS could not resolve the host name.
Please verify that you can connect to www.secondlife.com
web site. If you can, but continue to receive this error,
please go to the support section and and report this problem.

I've been looking for solutions for a few days now and none of them have resolved the error, including flushing the DNS cache, using OpenDNS or Google Public DNS, clearing SecondLife's cache, trying other viewers, other versions, and restarting the computer. I can log-in to the Second Life website, but not into the viewer.

This is the info copied from "About Second Life".
If anyone can tell me if there's something amiss with the viewer version, or possibly my (old) computer...I'd appreciate it!
I can also get the error report files if you tell me where they are usually located and what the file names are.

Second Life 3.0.0 (238864) Aug 18 2011 13:05:38 (Second Life Release)
Release Notes

CPU:               Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.15 MHz)
Memory: 512 MB
OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) compatibility mode. real ver: 6.0 (Build 2900)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce4 MX 440 with AGP8X/AGP/SSE2

Windows Graphics Driver Version: 6.14.0010.9371
OpenGL Version: 1.5.7

libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
J2C Decoder Version: KDU v6.4.1
Audio Driver Version: FMOD version 3.750000
Qt Webkit Version: 4.7.1 (version number hard-coded)
Voice Server Version: Not Connected
Built with MSVC version 1600

Link to comment
Share on other sites

I hope you can get more than 512 mb of Ram in that computer.

I'm keeping an eye on all this mysterious DNS stuff that's been happening with SL for a few months. Using Opendns settings fixed it for me, but I didn't need that in any other viewer besides Viewer 2. I'm expecting the next Firestorm will be the same way.

I don't know of a fix besides adding dns settings such as Google Dns and Opendns, but I'm going to subscribe to see if someone does have a fix for what is happening with your system.

 

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 4044 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...