Re: portforwarding question

Ralf, That takes of this issue then. I added a port of my choosing to the /etc/services and everything is working as expected. Yesterday I did the same trial with forwarding port 80 to the internal service. It was successful for me though, (of course my real site was gone). Are you asking for

Re: portforwarding question

Hi Bill, On Tue, 09 Mar 1999 13:59:19 -0600, [EMAIL PROTECTED] wrote: >You are correct in the assumption of using port 8080 below. That is >exactly what I am doing now, (it works great BTW!). Is 8080 the Nice for you. I also tried to forward port 80 to an internal host, but I wasn't as succes

Re: portforwarding question

Hello again Ralf, You are correct in the assumption of using port 8080 below. That is exactly what I am doing now, (it works great BTW!). Is 8080 the correct port to use? Now that 8080 will be in use, can I just start pulling ports out of the air for other web services, (that is if I had any ot

Re: portforwarding question

On Tue, 09 Mar 1999 09:31:04 -0600, [EMAIL PROTECTED] wrote: >> I have a web site on my Debian box visible to the >> world. Of course this is using xxx.xxx.xxx.xxx:80. >> >> I also have an internal web site visible to the world >> using portforwarding xxx.xxx.xxx.xxx:. >> >> Question 1- Which p

Re: portforwarding question

Anyone? I will try one more post with these questions. Thanks, -Bill > Hello again, > > I have a web site on my Debian box visible to the > world. Of course this is using xxx.xxx.xxx.xxx:80. > > I also have an internal web site visible to the world > using portforwarding xxx.xxx.xxx.xxx:. > >

portforwarding question

Hello again, I have a web site on my Debian box visible to the world. Of course this is using xxx.xxx.xxx.xxx:80. I also have an internal web site visible to the world using portforwarding xxx.xxx.xxx.xxx:. Question 1- Which port(s) should I forward to allow this visibility and not overrun my r