• Resolved flashingcurser

    (@flashingcurser)


    Yes this has been asked before and No it hasn’t been answered.

    Anyone found a way to access/admin the blog from a local network? Or a workaround? Anything?

    Thanks

    dan

Viewing 8 replies - 1 through 8 (of 8 total)
  • Can you better elaborate your question, or link to a previous discussion on the matter?

    Thread Starter flashingcurser

    (@flashingcurser)

    The webserver on my network resides in a local network. I use portforwarding from my router so that the outside world can access it. WordPress does not like to be accessed from the local network— http://192.168.5.50 as an example. If you try– it will show a couple of links (no theme or any thing) that if clicked on will give a 404. It can only be accessed correctly from my fqdn– http://mysite.org on a browser outside my local network. The problem is that if you type in http://mysite.org to a web brouser within my local network– I get my router admin.

    (A router cannot forward from inside back to inside– once dns tranlates the fqdn then your browser only knows the address– that address from inside the network is simply the router.)

    A search for “local network” will give many unanswered posts.

    http://wordpress.org/support/topic.php?id=29602

    Thanks

    dan

    I don’t think there is a way to administer your WordPress locally using a different URL, because WP stores the blog and site URL with in it’s database.

    This is an intriguing problem which no potential recourse but to hack WP.

    Regards

    Thread Starter flashingcurser

    (@flashingcurser)

    Anyone setup bind to resolve http://mysite.org to 192.168.5.50?

    How about an internet proxy?

    Anyone using either to solve this?

    You need to create on your workstation a host file entry, mapping the public DNS name of your server to the local IP address.

    If you’re using GNU/Linux (OSX, too?), edit /etc/hosts and add a line like this:
    192.168.5.50 mysite.org

    If you’re using Windows XP, edit C:\Windows\System32\Drivers\Etc\Hosts like this:
    192.168.5.50 mysite.org

    Windows 2000 uses C:\Winnt\System32\Drivers\Etc\Hosts.
    192.168.5.50 mysite.org

    The existence of that line in your hosts file tells your workstation to use the specific IP address when trying to connect to the named host. This avoids the DNS lookup, and will allow you to do everything you need to do.

    Thread Starter flashingcurser

    (@flashingcurser)

    The win2k box seems to be ignoring the host file… I’ll explore that some more. (Come to think of it, it may be antispyware doing something to the host file.)

    Thanks

    dan

    Sometimes you need to reboot Windows boxes to make them honor host file entries.

    Thread Starter flashingcurser

    (@flashingcurser)

    I dual boot with slackware– maybe I just need to forget windows. I have been gaming alot lately though….

    Thanks

    dan

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Admin from local network’ is closed to new replies.