Good question. Maybe this is the reason. It might well be that authentication from outside of the router works. But not inside (or behind) it. Is there a workaround? Opensim did it (with their authentication system) but not sure about the technical details of what they did. -paul
On Tue, Dec 9, 2008 at 2:34 PM, Ryan McDougall <[EMAIL PROTECTED]> wrote: > > On Tue, Dec 9, 2008 at 9:00 PM, Paul Fishwick <[EMAIL PROTECTED]> wrote: >> >> Can one of the developers please address this thread? Thank you. >> >> http://www.rexdeveloper.org/forum/viewtopic.php?f=3&t=131 >> > > From the link: > > 23:13:59 - [HTTPD]: Starting up HTTP Server > 23:13:59 - Enter help for a list of commands > 23:13:59 - Authentication# : > 23:13:59 - [HTTPD]: Starting http listener > 23:14:20 - [LOGIN]: Authenticating Test User > 23:14:20 - ------------------------------------------- > 23:14:20 - CLIENT LOGGIN IN TO SIM: [EMAIL PROTECTED]:9000 > 23:14:20 - ------------------------------------------- > 23:14:20 - [SimLoginChecker]: Failed to authenticate sim from > 192.168.1.1:2789 a > ddress corresponding to uid is 24.X.Y.Z > 23:14:20 - [SimLoginChecker]: No corresponding dns addresses found > 23:14:20 - [LOGIN]: server_ip_check failed > > Is this due to the anti-phishing feature which compares the address > the client thinks its logging in to the address that is actually > logging in to, where "actually" means the programmatic equivalent of > "ipconfig"? > > Is there a way to fix this without disabling phishing protection? > > Cheers, > > > > --~--~---------~--~----~------------~-------~--~----~ this list: http://groups.google.com/group/realxtend realXtend home page: http://www.realxtend.org/ -~----------~----~----~----~------~----~------~--~---
