Thanks so much Fred, your explanation was exactly what I needed to configure the Windows Loopback Adapter. I will remove the line in the Hosts file and configure the Adapter and see if that helps me.
A question. Do I need to do anything to the Etherneth connection? I mean right now I had configured it so that this PC got a static internal IP 192.168.2.10. Do I leave it alone and do nothing to it and just configure the windows loopback adapter? On Wed, Oct 21, 2015 at 10:42 PM, Fred Beckhusen <[email protected]> wrote: > I would not use the Hosts file 'trick' on a server that also has the > viewer. The fact that you need to edit hosts file indicates that the > router cannot loopback. I use the Microsoft Loopback Adapter. > > What happens is that the server broadcasts your public DNS name to clients > not as a name, but as an address. The server first does a DNS lookup and > via hosts, finds the 127.0.0.1 loopback. It will broadcast this 127.0.0.1 > address to a remote WAN client, and they cannot connect. Yet it works > for you. But without loopback, you cannot connect. > > On Windows, you can add a software loopback adapter for the Public Port to > loopback the public IP to the server, which allows the server to send the > public IP to clients. > > Installation instructions: > https://technet.microsoft.com/en-us/library/cc708322(v=ws.10).aspx > > Once it is installed you have to set it up. It will be in the Control > Panel->Network Connections, as "NAT Loopback". Its just like an Ethernet > driver. Open it, and find Internet Protocol Version 4 (TCP/IPv4) and > change its properties. I click "Use the following IP address" and enter my > PUBLIC IP in the IP Address box. No Gateway is needed. Under DNS, I used > my routers IP address so it can do the DNS lookups. Or you can use > Googles super DNS of 8.8.8.8. and 8.8.4.4 > > Once enabled, this will make any reference to the Public IP address route > right back to the system itself, just as the router should do. And WAN > users get the correct Public IP sent to them, instead of 127.0.0.1 > > > Ferd Frederix > http://www.outworldz.com > > > On 2015-10-21 11:31 AM, [email protected] wrote: > >> Today's Topics: >> >> 1. Re: HG - Not able to teleport back home (Isis Ophelia) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Wed, 21 Oct 2015 17:54:13 +0200 >> From: Isis Ophelia <[email protected]> >> To: [email protected] >> Subject: Re: [Opensim-users] HG - Not able to teleport back home >> Message-ID: >> <CAN5TJuReDxagLKBbrCzyByfL=9_Xw7= >> [email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> Thank you Garmin. I have configured my internet connection to be a static >> internal IP which is 192.168.2.10. Following your suggestion I replaced >> the >> 0.0.0.0 with that IP. >> Result is: The console shows: >> 17:48:30 - [SCENE]: Region Arcana Welcome authenticated and authorized >> incoming >> root agent Isis Ophelia 1b77be9b-248e-400b-a4ca-499d0aa06d77 (circuit code >> 40308 >> 2697) >> >> And the viewer tells me: We are having problems connecting. There might be >> a problem with your internet connection or the Arcana World Grid. >> So pity this does not help :( >> Thank so much though :) >> >> On Wed, Oct 21, 2015 at 4:24 PM, GarminKawaguichi < >> [email protected]> wrote: >> >> > _______________________________________________ > Opensim-users mailing list > [email protected] > http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users >
_______________________________________________ Opensim-users mailing list [email protected] http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
