Good news. Weird thing happened. I am okay with the access. It seems like even with the DNS service such as no-ip.org still requires the users to access via abc.no-ip.org:8000 instead of abc.no- ip.org.
But I thought I had tried abc.no-ip.org:8000 already yesterday. Thank you, Sam. On Jun 6, 1:19 am, Sam Lai <samuel....@gmail.com> wrote: > Does it work from another machine on the same local network? > > This is definitely possible though; I've done it before. > > On 6 June 2010 14:35, John Yeukhon Wong <gokoproj...@gmail.com> wrote: > > > I just disabled the FW, but no luck with any trials. > > > Yeah. Security isn't my concern because only a few people (including > > myself) will learn about this project. They will only see the > > interfaces at certain stages when I give out notifications. > > I am sure in Linux there isn't any problem with overriding the > > restriction. > > It's so weird with XP. > > > Hahaha > > > Thanks > > > On Jun 5, 11:55 pm, Sam Lai <samuel....@gmail.com> wrote: > >> Oops. Seems like you've tried that already. > > >> Have you checked your Windows firewall settings? > > >> On 6 June 2010 13:53, Sam Lai <samuel....@gmail.com> wrote: > > >> > By default, the Django development server does not allow hosts to > >> > connect unless it is localhost (127.0.0.1) or a local IP > >> > (192.168.1.101 in your case). > > >> > Doing this is a *bad idea*, as indicated by the docs - > >> >http://docs.djangoproject.com/en/1.2/ref/django-admin/#djadmin-runserver > > >> > If you really do want to override it, start the server like this - > > >> > python manage.py runserver 0.0.0.0:8000 > > >> > That tells the dev server to accept any IP. > > >> > If I were you, I'd just set up IIS/Apache. There's no advantage of > >> > accessing your dev server from elsewhere anyway, because you can't see > >> > the debug messages. > > >> > On 6 June 2010 10:32, John Yeukhon Wong <gokoproj...@gmail.com> wrote: > >> >> For my home purpose, currently I am running Windows XP. > > >> >> I have everything ready. Django, Python are all good. > > >> >> If I let the runserver (I am using the django-development server) to > >> >> be 127.0.0.1:8000 or 192.168.1.101:8000 they all worked. > > >> >> Let say abc.no-ip.org is a FREE DNS service I use to access > >> >> externally. > > >> >> In the past when I did this in debian or ubuntu, there was no access > >> >> issue except the fact that I enabled either multi-cast or NET > >> >> Redirection in my router firewall setting. > > >> >> I checked my router setting so many times and nothing suspicious. > > >> >> I even tried like 192.168.1.101:8080 0.0.0.0:8080 in the runserver > >> >> command and no luck. > > >> >> I still cannot access to abc.no-ip.org > > >> >> How come? > > >> >> Thanks. > > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups "Django users" group. > >> >> To post to this group, send email to django-us...@googlegroups.com. > >> >> To unsubscribe from this group, send email to > >> >> django-users+unsubscr...@googlegroups.com. > >> >> For more options, visit this group > >> >> athttp://groups.google.com/group/django-users?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
