Hi Jason, This has not been fixed in trunk yet. I was planning on rolling this into the RFC 42 - Remove Support Servers work.
Thanks, Trevor -----Original Message----- From: Jason Birch [mailto:[EMAIL PROTECTED] Sent: Monday, December 24, 2007 1:03 PM To: MapGuide Users Mail List Subject: RE: [mapguide-users] MapGuide 1.2 login error I think that it may have already been fixed in the 1.2.x branch. http://trac.osgeo.org/mapguide/changeset/2509 I can't find where/if this change got applied to current 2.0.x trunk... Jason -----Original Message----- From: uXuf Subject: Re: [mapguide-users] MapGuide 1.2 login error Okay so the real culprit appears to be the Wireless Access Point assigning "new" IP address to the system whenever it comes out of stand-by. It seems that MG 1.2 picks up the actual IP address of the system when it initializes the service on system boot-up, while MG 1.1 used localhost (or 127.0.0.1) all along. So with 1.2 whenever the system gets a new IP, the service refuses to connect. Figures that Studio connects through all this mess, because I usually use localhost as the server to connect to. Couldn't really see that this would get fixed anytime soon, but really hope that it does because as far as I see it would be a rather simple fix. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
