Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

078274121, info0a ip, should prodicers of software_based services be held liable or not liable for economic injuries, should producers of soft ware based services such as ATMs be held liable for economic injuries suffered when their systems fail?, nisc wwwxxx, wwwxxx0cm, should producers of software-based services, such as atms, be held liable for economic injuries suffered when their systems fail?, wwwxxx0cm, www.webdp.net, Event 9 IIS log failed to write entry

Links

XODOX
Impressum

#1: (Yet Another) Newbie Question about servers within a private network

Posted on 2008-04-15 23:46:50 by Marten Kemp

I have the following:

enthusiasts.dyn-o-saur.com
=> dyndns.com
=> home IP address
=> router virtual server for port 80
=> 192.168.2.200
=> "production" webserver

All this works perfectly. However, a link to a page
hosted on my test server (dingbat at 192.168.2.102)
fails when I try it from outside my network. I know
that the 192.168 range is private but there should
be some way to do this.

I've groveled through the Fine Manuals but there
seems to be something that I'm missing. Probably
intuitively obvious to the most casual observer.

--
-- Marten Kemp
(Fix name and ISP to reply)

Report this message

#2: Re: (Yet Another) Newbie Question about servers within a private network

Posted on 2008-04-16 00:16:54 by spam

"Marten Kemp" <marten.kemp@thisplanet-link.net> wrote in message
news:fu37o7$jnb$1@aioe.org...
> I have the following:
>
> enthusiasts.dyn-o-saur.com
> => dyndns.com
> => home IP address
> => router virtual server for port 80
> => 192.168.2.200
> => "production" webserver
>
> All this works perfectly. However, a link to a page
> hosted on my test server (dingbat at 192.168.2.102)
> fails when I try it from outside my network. I know
> that the 192.168 range is private but there should
> be some way to do this.
>
> I've groveled through the Fine Manuals but there
> seems to be something that I'm missing. Probably
> intuitively obvious to the most casual observer.

Your problem has NOTHING to do with apache. (Note the follow-up group I've
selected)

That's because you're using the wrong IP address at dyndns.com. What needs
to be listed there is the dynamic address you get from your provider for
your dial-up or DSL line. Then, at your router, you need to forward port 80
to your local IP.

Even with all that, it still may not work. Your ISP may block port 80 as
customers (without business accounts that have static IPs) aren't supposed
to be running servers at home.

Report this message