Re: [WebDNA] Privat IP website behind a public IP website

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111764
interpreted = N
texte = --Apple-Mail=_C832C0CB-AB15-4954-88F9-EFF8B9ED8F4F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Will As the discussion opens my awareness widens. Basically I only have one public IP and that is my dilemma. NAT is turned on on my router/firewall and I am able to make a Port = Forward rule. So maybe mu challenge is the ONE PUBLIC IP. And IF it is; is it hen at = all possible to have the one server on a public IP hosting http and = another on the local network hosting http as well and both being = accessed from the outside. PS. Sagemcom /Palle > On 12/12/2014, at 23.06, WJ Starck, DDS wrote: >=20 > Right >=20 > So you should be able to set up your firewall so that http (port 80) = requests are handled like this >=20 > Requests to www.mypublicserver.com = (let's say its public IP is 63.x.x.74) get pointed to your public server=20= >=20 > Then you'll need a second public IP, say 63.x.x.75, that gets pointed = (port forwarded) to your internal server, say 192.168.1.75. You'll need = NAT turned on in your firewall. You probably don't want DNS setup for = the private host (I'm guessing) so you'd just access it with = http://63.x.x.75 >=20 > What firewall are you running (feel free to email me off list at = wjs@webdna.us if you don't want to say publicly)? >=20 > Cheers, >=20 > Will >=20 >=20 > --- > William J. Starck, DDS > Big Idea Software, LLC > 15305 Dallas Parkway Suite 300 > Addison, TX 75001 > 817-800-9634 > http://www.bigideasoft.com >=20 > On Dec 12, 2014, at 3:41 PM, Palle Bo Nielsen = > wrote: >=20 >> Yes, but I need to server HTTP request from both the public server = (63.x.x.x) and the private server (192.168.x.x) >>=20 >> PS. I use FastCGI on both >>=20 >> /Palle >>=20 >>=20 >>> On 12/12/2014, at 22.19, WJ Starck, DDS > wrote: >>>=20 >>> Palle- >>>=20 >>> You don't have to do that. >>>=20 >>> Like Dan said, just assign a public IP to your private server, then = setup your firewall to port forward requests for port 80 from that = public IP to the private IP of the internal server. Are you using WebDNA = server of FastCGI? You might consider using FastCGI for the internal = server as the setup will be easier. >>>=20 >>> Cheers, >>>=20 >>> Will >>>=20 >>>=20 >>> --- >>> William J. Starck, DDS >>> Big Idea Software, LLC >>> 15305 Dallas Parkway Suite 300 >>> Addison, TX 75001 >>> 817-800-9634 >>> http://www.bigideasoft.com >>>=20 >>> On Dec 12, 2014, at 1:42 PM, Palle Bo Nielsen = > wrote: >>>=20 >>>> a) The :8000 (port)option, wouldn=E2=80=99t that require that all = links on the privat ip also has :8000 (the port attached) ? The port = routing would be easy. >>>>=20 >>>> b) How would I do this? I am a bit blank here. >>>>=20 >>>> /Palle >>>>=20 >>>>=20 >>>>=20 >>>>> On 12/12/2014, at 19.45, Dan Strong > wrote: >>>>>=20 >>>>> Maybe set up port forwarding on your router for an arbitrary port, = say, 8000, and access from the outside like this http://:8000 = and all traffic to this port gets forwarded to 192.168.1.135 or = whatever... >>>>>=20 >>>>> Or you could set up some sort of dyndns on the privare computer = and acess it that way. >>>>>=20 >>>>> Obviously I don't know your specifics, but this might be a general = path to explore. Hope it helps. >>>>>=20 >>>>> -Dan Strong >>>>> http://DanStrong.com >>>>> On Fri, Dec 12, 2014 at 10:08 AM, Palle Bo Nielsen = > wrote: >>>>> HI >>>>>=20 >>>>> I have a network with a public fixed IP on which a webdna website = i running fine. >>>>>=20 >>>>> On the local network NAT=E2=80=99ed behind the public fixed IP I = have another physical server with webdna with a privat fixed IP, which = is not accessible from the outside. >>>>>=20 >>>>> Is there any WebDNA way I can access the server on the private = network from the outside, possible using the Publicly available WebDNA = server? >>>>>=20 >>>>> /Palle--------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list >. >>>>> To unsubscribe, E-mail to: > >>>>> archives: http://mail.webdna.us/list/talk@webdna.us = >>>>> Bug Reporting: support@webdna.us >>>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- This message is sent to you because you are subscribed to the = mailing list . To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- This message is sent to you because you are subscribed to the = mailing list . To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail=_C832C0CB-AB15-4954-88F9-EFF8B9ED8F4F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi Will

As the discussion opens my awareness = widens.

Basically I only have one public IP and = that is my dilemma.

NAT is turned on on my router/firewall and I am able to make a Port Forward rule.

So maybe mu challenge is = the ONE PUBLIC IP. And IF it is; is it hen at all possible to have the = one server on a public IP hosting http and another on the local network = hosting http as well and both being accessed from the outside.

PS. Sagemcom

/Palle


On 12/12/2014, at 23.06, WJ = Starck, DDS <wjs@bigideasoft.com> wrote:

Right

So you should be able to = set up your firewall so that http (port 80) requests are handled like = this

Requests = to www.mypublicserver.com (let's say its public IP is = 63.x.x.74) get pointed to your public server 

Then you'll need a = second public IP, say 63.x.x.75, that gets pointed (port forwarded) to = your internal server, say 192.168.1.75. You'll need NAT turned on in = your firewall. You probably don't want DNS setup for the private host = (I'm guessing) so you'd just access it with http://63.x.x.75

What firewall are you running (feel = free to email me off list at wjs@webdna.us if you don't want to say = publicly)?

Cheers,

Will


---
William J. Starck, = DDS
Big Idea Software, = LLC
15305 Dallas Parkway Suite = 300
Addison, TX 75001
817-800-9634
http://www.bigideasoft.com

On Dec 12, 2014, at 3:41 PM, Palle Bo Nielsen = <powerpalle@powerpalle.dk> wrote:

Yes, but I = need to server HTTP request from both the public server (63.x.x.x) and = the private server (192.168.x.x)

PS. I use FastCGI on both

/Palle


On 12/12/2014, at 22.19, WJ = Starck, DDS <wjs@bigideasoft.com> wrote:

Palle-

You don't have to do = that.

Like Dan = said, just assign a public IP to your private server, then setup your = firewall to port forward requests for port 80 from that public IP to the = private IP of the internal server. Are you using WebDNA server of = FastCGI? You might consider using FastCGI for the internal server as the = setup will be easier.

Cheers,

Will


---
William J. Starck, = DDS
Big Idea Software, = LLC
15305 Dallas Parkway Suite = 300
Addison, TX 75001
817-800-9634
http://www.bigideasoft.com

On Dec 12, 2014, at 1:42 PM, Palle Bo Nielsen = <powerpalle@powerpalle.dk> wrote:

a) The :8000 (port)option, = wouldn=E2=80=99t that require that all links on the privat ip also has = :8000 (the port attached) ? The port routing would be easy.

b) How would I do this? = I am a bit blank here.

/Palle



On = 12/12/2014, at 19.45, Dan Strong <dan@danstrong.com> wrote:

Maybe set up port forwarding on your router for an arbitrary = port, say, 8000, and access from the outside like this = http://<your-ip>:8000 and all traffic to this port gets forwarded = to 192.168.1.135 or whatever...

Or you could set up some sort of dyndns on the privare = computer and acess it that way.

Obviously I don't know your specifics, = but this might be a general path to explore. Hope it = helps.

-Dan Strong
http://DanStrong.com

On Fri, Dec 12, 2014 at 10:08 = AM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:
HI

I have a network with a public fixed IP on which a webdna website i = running fine.

On the local network NAT=E2=80=99ed behind the public fixed IP I have = another physical server with webdna with a privat fixed IP, which is not = accessible from the outside.

Is there any WebDNA way I can access the server on the private network = from the outside, possible using the Publicly available WebDNA = server?

/Palle---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

= --Apple-Mail=_C832C0CB-AB15-4954-88F9-EFF8B9ED8F4F-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Privat IP website behind a public IP website ("WJ Starck, DDS" 2014)
  2. Re: [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
  3. Re: [WebDNA] Privat IP website behind a public IP website ("WJ Starck, DDS" 2014)
  4. Re: [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
  5. Re: [WebDNA] Privat IP website behind a public IP website ("WJ Starck, DDS" 2014)
  6. Re: [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
  7. Re: [WebDNA] Privat IP website behind a public IP website (Dan Strong 2014)
  8. [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
--Apple-Mail=_C832C0CB-AB15-4954-88F9-EFF8B9ED8F4F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Will As the discussion opens my awareness widens. Basically I only have one public IP and that is my dilemma. NAT is turned on on my router/firewall and I am able to make a Port = Forward rule. So maybe mu challenge is the ONE PUBLIC IP. And IF it is; is it hen at = all possible to have the one server on a public IP hosting http and = another on the local network hosting http as well and both being = accessed from the outside. PS. Sagemcom /Palle > On 12/12/2014, at 23.06, WJ Starck, DDS wrote: >=20 > Right >=20 > So you should be able to set up your firewall so that http (port 80) = requests are handled like this >=20 > Requests to www.mypublicserver.com = (let's say its public IP is 63.x.x.74) get pointed to your public server=20= >=20 > Then you'll need a second public IP, say 63.x.x.75, that gets pointed = (port forwarded) to your internal server, say 192.168.1.75. You'll need = NAT turned on in your firewall. You probably don't want DNS setup for = the private host (I'm guessing) so you'd just access it with = http://63.x.x.75 >=20 > What firewall are you running (feel free to email me off list at = wjs@webdna.us if you don't want to say publicly)? >=20 > Cheers, >=20 > Will >=20 >=20 > --- > William J. Starck, DDS > Big Idea Software, LLC > 15305 Dallas Parkway Suite 300 > Addison, TX 75001 > 817-800-9634 > http://www.bigideasoft.com >=20 > On Dec 12, 2014, at 3:41 PM, Palle Bo Nielsen = > wrote: >=20 >> Yes, but I need to server HTTP request from both the public server = (63.x.x.x) and the private server (192.168.x.x) >>=20 >> PS. I use FastCGI on both >>=20 >> /Palle >>=20 >>=20 >>> On 12/12/2014, at 22.19, WJ Starck, DDS > wrote: >>>=20 >>> Palle- >>>=20 >>> You don't have to do that. >>>=20 >>> Like Dan said, just assign a public IP to your private server, then = setup your firewall to port forward requests for port 80 from that = public IP to the private IP of the internal server. Are you using WebDNA = server of FastCGI? You might consider using FastCGI for the internal = server as the setup will be easier. >>>=20 >>> Cheers, >>>=20 >>> Will >>>=20 >>>=20 >>> --- >>> William J. Starck, DDS >>> Big Idea Software, LLC >>> 15305 Dallas Parkway Suite 300 >>> Addison, TX 75001 >>> 817-800-9634 >>> http://www.bigideasoft.com >>>=20 >>> On Dec 12, 2014, at 1:42 PM, Palle Bo Nielsen = > wrote: >>>=20 >>>> a) The :8000 (port)option, wouldn=E2=80=99t that require that all = links on the privat ip also has :8000 (the port attached) ? The port = routing would be easy. >>>>=20 >>>> b) How would I do this? I am a bit blank here. >>>>=20 >>>> /Palle >>>>=20 >>>>=20 >>>>=20 >>>>> On 12/12/2014, at 19.45, Dan Strong > wrote: >>>>>=20 >>>>> Maybe set up port forwarding on your router for an arbitrary port, = say, 8000, and access from the outside like this http://:8000 = and all traffic to this port gets forwarded to 192.168.1.135 or = whatever... >>>>>=20 >>>>> Or you could set up some sort of dyndns on the privare computer = and acess it that way. >>>>>=20 >>>>> Obviously I don't know your specifics, but this might be a general = path to explore. Hope it helps. >>>>>=20 >>>>> -Dan Strong >>>>> http://DanStrong.com >>>>> On Fri, Dec 12, 2014 at 10:08 AM, Palle Bo Nielsen = > wrote: >>>>> HI >>>>>=20 >>>>> I have a network with a public fixed IP on which a webdna website = i running fine. >>>>>=20 >>>>> On the local network NAT=E2=80=99ed behind the public fixed IP I = have another physical server with webdna with a privat fixed IP, which = is not accessible from the outside. >>>>>=20 >>>>> Is there any WebDNA way I can access the server on the private = network from the outside, possible using the Publicly available WebDNA = server? >>>>>=20 >>>>> /Palle--------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list >. >>>>> To unsubscribe, E-mail to: > >>>>> archives: http://mail.webdna.us/list/talk@webdna.us = >>>>> Bug Reporting: support@webdna.us >>>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- This message is sent to you because you are subscribed to the = mailing list . To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us >> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us = Bug Reporting: = support@webdna.us = ------------------------------------------------= --------- This message is sent to you because you are subscribed to the = mailing list . To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us --Apple-Mail=_C832C0CB-AB15-4954-88F9-EFF8B9ED8F4F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi Will

As the discussion opens my awareness = widens.

Basically I only have one public IP and = that is my dilemma.

NAT is turned on on my router/firewall and I am able to make a Port Forward rule.

So maybe mu challenge is = the ONE PUBLIC IP. And IF it is; is it hen at all possible to have the = one server on a public IP hosting http and another on the local network = hosting http as well and both being accessed from the outside.

PS. Sagemcom

/Palle


On 12/12/2014, at 23.06, WJ = Starck, DDS <wjs@bigideasoft.com> wrote:

Right

So you should be able to = set up your firewall so that http (port 80) requests are handled like = this

Requests = to www.mypublicserver.com (let's say its public IP is = 63.x.x.74) get pointed to your public server 

Then you'll need a = second public IP, say 63.x.x.75, that gets pointed (port forwarded) to = your internal server, say 192.168.1.75. You'll need NAT turned on in = your firewall. You probably don't want DNS setup for the private host = (I'm guessing) so you'd just access it with http://63.x.x.75

What firewall are you running (feel = free to email me off list at wjs@webdna.us if you don't want to say = publicly)?

Cheers,

Will


---
William J. Starck, = DDS
Big Idea Software, = LLC
15305 Dallas Parkway Suite = 300
Addison, TX 75001
817-800-9634
http://www.bigideasoft.com

On Dec 12, 2014, at 3:41 PM, Palle Bo Nielsen = <powerpalle@powerpalle.dk> wrote:

Yes, but I = need to server HTTP request from both the public server (63.x.x.x) and = the private server (192.168.x.x)

PS. I use FastCGI on both

/Palle


On 12/12/2014, at 22.19, WJ = Starck, DDS <wjs@bigideasoft.com> wrote:

Palle-

You don't have to do = that.

Like Dan = said, just assign a public IP to your private server, then setup your = firewall to port forward requests for port 80 from that public IP to the = private IP of the internal server. Are you using WebDNA server of = FastCGI? You might consider using FastCGI for the internal server as the = setup will be easier.

Cheers,

Will


---
William J. Starck, = DDS
Big Idea Software, = LLC
15305 Dallas Parkway Suite = 300
Addison, TX 75001
817-800-9634
http://www.bigideasoft.com

On Dec 12, 2014, at 1:42 PM, Palle Bo Nielsen = <powerpalle@powerpalle.dk> wrote:

a) The :8000 (port)option, = wouldn=E2=80=99t that require that all links on the privat ip also has = :8000 (the port attached) ? The port routing would be easy.

b) How would I do this? = I am a bit blank here.

/Palle



On = 12/12/2014, at 19.45, Dan Strong <dan@danstrong.com> wrote:

Maybe set up port forwarding on your router for an arbitrary = port, say, 8000, and access from the outside like this = http://<your-ip>:8000 and all traffic to this port gets forwarded = to 192.168.1.135 or whatever...

Or you could set up some sort of dyndns on the privare = computer and acess it that way.

Obviously I don't know your specifics, = but this might be a general path to explore. Hope it = helps.

-Dan Strong
http://DanStrong.com

On Fri, Dec 12, 2014 at 10:08 = AM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:
HI

I have a network with a public fixed IP on which a webdna website i = running fine.

On the local network NAT=E2=80=99ed behind the public fixed IP I have = another physical server with webdna with a privat fixed IP, which is not = accessible from the outside.

Is there any WebDNA way I can access the server on the private network = from the outside, possible using the Publicly available WebDNA = server?

/Palle---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
= --Apple-Mail=_C832C0CB-AB15-4954-88F9-EFF8B9ED8F4F-- Palle Bo Nielsen

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[OT] - CyberCash/Verisign (2001) Using Plug-In while running 1.6.1 (1997) Nav4 not specifying cart (1997) ImageMap (1997) Latin Characters (1998) My URL, Your URL (2002) Nested vs conditional (1997) Accepting credit cards (1997) What is WebDNA (1997) Wierd problem with 3.08 WIN Version (2000) setting HTTP response header (1998) ShowNext Context (2004) Quit revisited (1997) PhotoMill -> PhotoMaster (1997) webcat serving multiple copies of same db from ram (2000) webcat- multiple selection in input field (1997) WebCatalog and WebMerchant reviewed by InfoWorld (1997) Another Flash Question (2000) foreign languages, email, webcat (1998) 300% usage - Clint (2007)