I was hopeful - but no. Antivirus IS off on the server. On Wed, Dec 1, 2010 at 9:41 AM, Fleep Tuque <[email protected]> wrote:
> Is there any anti-virus software installed on the machine? I had a similar > nightmare install and kept checking and re-checking my network settings and > in the end it turned out the virus protection "active scanning" stuff was > causing the problem. (In my case it was Avast). Turned that off then > suddenly everything worked like magic. > > Good luck! > > - Fleep > > > Chris M. Collins (SL: Fleep Tuque) > Project Manager, UC Second Life > Second Life Ambassador, Ohio Learning Network > UCit Instructional & Research Computing > University of Cincinnati > 406E Zimmer Hall > PO Box 210088 > Cincinnati, OH 45221-0088 > (513)556-3018 > [email protected] > > UC Second Life: http://homepages.uc.edu/secondlife > OLN Second Life: http://www.oln.org/emerging_technologies/emtech.php > > > > On Wed, Dec 1, 2010 at 10:21 AM, iSkye Silverweb < > [email protected]> wrote: > >> He has a Windows XP machine that is running the Diva distro. Here's our >> current setup: >> >> We have a standalone Diva distro 0.7.0 on a Windows XP computer in the UK, >> with two other computers inside that network; two external computers outside >> the UK. Broadband provider is Sky. >> >> On router (Sagem f...@st 2504 firmware version 2.8Sky): >> Port 9000 for TCP/UDP and ports 9001-9003 for UDP >> >> Windows firewall disabled on both computers inside the network >> >> regions.ini file: >> external IP is our-grid.dyndns-server.com (note: when we change the >> external IP to the actual internal IP, 192.168.0.9, for the machine running >> our grid, our UK guy can log in from inside his network, but the 2 outside >> computers can't get past handshake) >> internal IP is 0.0.0.0 >> >> hosts file on the client the UK guy is trying to login from: >> 192.168.0.9 our-grid.dyndns-server.com >> >> uPnP and DMZ are both off, disabled (we've tried both ways) >> >> >> On Wed, Dec 1, 2010 at 10:14 AM, Jeroen van Veen <[email protected]>wrote: >> >>> Did you check the iptables(if on linux) script? I used it succesfully to >>> have >>> both internal and external access to the sims. >>> >>> kind regards, >>> >>> Jeroen >>> >>> On Wednesday 01 December 2010 14:45:52 iSkye Silverweb wrote: >>> > I'm sorry if we are testing some people's patience on this. All the >>> help >>> > thus far is much appreciated. We have a lot to do, just as we're sure >>> > everyone here on this list is also very busy. We would REALLY like to >>> get >>> > this solved. >>> > >>> > Initially, we followed the steps of installing the Diva distribution, >>> and >>> > the result was that our UK guy could log in from the LAN, but the two >>> > external users could not get past the handshake. Then, the going round >>> in >>> > circles started. >>> > >>> > Let me give a recap of all we've checked, just so we're clear: >>> > >>> > Yes, we did look at the various websites like the one at the link you >>> gave, >>> > Diva, when installing the distro, and we followed the instructions, and >>> we >>> > have since checked and rechecked several times as the only help we seem >>> to >>> > be getting is links to the ports issue. >>> > >>> > YES, port 9000 is open on the server machine for TCP and UDP >>> > YES, ports 9001 to 9003 are open for UDP >>> > We have used a port checker which confirmed this, and >>> > YES, they are open on the firewall and directed to the server machine. >>> > We have checked with port checkers both from inside and outside the >>> > network. >>> > >>> > YES, all address references in the myworld.ini and regions files point >>> to >>> > the DYNDNS address >>> > YES, we have changed all the inside-LAN clients' hostfiles to point to >>> the >>> > DYNDNS address to the server >>> > >>> > We even bought a new router, since we learned the previous one was an >>> older >>> > model that did not support NAT loopback, after attempting multiple >>> > (fruitless) firmware updates. The new router is a Sagem f...@st 2504 >>> with >>> > firmware version 2.8Sky (our broadband provider is Sky), which >>> supposedly >>> > does support NAT loopback. >>> > >>> > As a result: >>> > EXTERNAL users can now get in, past the handshake and inworld, but >>> > INTERNAL users fail at handshake. >>> > >>> > As we have said, the only way we we seem to get internal users in is by >>> > adding an entry in the hosts file of the SERVER machine, which then >>> > prevents people from outside getting in until that entry is removed >>> from >>> > the hosts file on the server machine. This is kludgy and not a good >>> > permanent solution, but it enables us to work together. >>> > >>> > I hope this has made our problem more clear and that there is a >>> solution >>> > other than to keep checking the same information we have already looked >>> at >>> > and tried. All your help is very much appreciated, and we've learned >>> an >>> > enormous amount thus far, but we are still stymied by this last bit. >>> > >>> > On Tue, Nov 30, 2010 at 9:37 PM, Diva Canto <[email protected]> >>> wrote: >>> > > These issues are explained in several places, here's one: >>> > > https://github.com/diva/d2/wiki/DNS >>> _______________________________________________ >>> Opensim-users mailing list >>> [email protected] >>> https://lists.berlios.de/mailman/listinfo/opensim-users >>> >> >> >> _______________________________________________ >> Opensim-users mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/opensim-users >> >> > > _______________________________________________ > Opensim-users mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-users > >
_______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
