Thanks Karen.
Tried it. I no longer get the "getaddrinfo failed" error message. I'm now able to access the server as localhost or 127.0.0.1 but no 192.168.1.117. There's got to be something simple I'm missing. This looks like it's designed behavior. There must be a setting somewhere. _____ From: django-users@googlegroups.com [mailto:django-us...@googlegroups.com] On Behalf Of Karen Tracey Sent: Wednesday, March 04, 2009 3:00 PM To: django-users@googlegroups.com Subject: Re: Accessing the development server from another machine. On Wed, Mar 4, 2009 at 4:51 PM, Joe Goldthwaite <j...@goldthwaites.com> wrote: Thanks Alex. That did something. Now I'm getting this; >c:\DjangoProjects\FiscalCalendar>manage.py runserver 0:8000 >Validating models... >0 errors found > >Django version 1.0.2 final, using settings 'FiscalCalendar.settings' >Development server is running at http://0:8000/ >Quit the server with CTRL-BREAK. >Error: (11001, 'getaddrinfo failed') Try 0.0.0.0:8000 Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
