a) The :8000 (port)option, wouldn=E2=80=99t that requ= ire 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.
Maybe set up port forwardin= g on your router for an arbitrary port, say, 8000, and access from the outsi= de like this http://<your-ip>:8000 and all traffic to this port gets f= orwarded to 192.168.1.135 or whatever...
Or you could set up some sort of dyndns on the privare comp= uter and acess it that way.
Obviously I don't know your specifics, but this might be a general= path to explore. Hope it helps.
= --Apple-Mail-EF609E83-D97A-4E36-BCBD-4F3D8020692B--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-EF609E83-D97A-4E36-BCBD-4F3D8020692B Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Palle- You don't have to do that. Like Dan said, just assign a public IP to your private server, then setup yo= ur firewall to port forward requests for port 80 from that public IP to the p= rivate IP of the internal server. Are you using WebDNA server of FastCGI? Yo= u might consider using FastCGI for the internal server as the setup will be e= asier. 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
w= rote: >=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 b= e 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, 8= 000, and access from the outside like this http://:8000 and all tra= ffic 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 t= o explore. Hope it helps. >>=20 >> -Dan Strong >> http://DanStrong.com >>=20 >>> 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 runn= ing fine. >>>=20 >>> On the local network NAT=E2=80=99ed behind the public fixed IP I have an= other physical server with webdna with a privat fixed IP, which is not acces= sible from the outside. >>>=20 >>> Is there any WebDNA way I can access the server on the private network f= rom 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 Reporti= ng: support@webdna.us >=20 > --------------------------------------------------------- This message is s= ent 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-EF609E83-D97A-4E36-BCBD-4F3D8020692B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Palle-
You do= n't have to do that.
Like Dan said, just assign a p= ublic IP to your private server, then setup your firewall to port forward re= quests for port 80 from that public IP to the private IP of the internal ser= ver. Are you using WebDNA server of FastCGI? You might consider using FastCG= I for the internal server as the setup will be easier.
<= div>Cheers,