NAT port forward to external IP address

I have a MS Server 2003 sitting behind a firewall that
lets through only communication on a certain port and
sends it to the server. I would like to know whether, I
can set up the server so that is simply forwards all
incoming traffic to an external server outside our
network. Our server has only one network device.
Under Linux this was not to hard too do. Is this possible
on a 2003 server?

Sincerely,
Niels

I think you'll need to provide a lot more detail as to what you're trying to
do...what is it you're trying to accomplish? Turn your server into a router?
Where will the traffic originate, if you can't control what's open on the
firewall?

Niels wrote:
> I have a MS Server 2003 sitting behind a firewall that
> lets through only communication on a certain port and
> sends it to the server. I would like to know whether, I
> can set up the server so that is simply forwards all
> incoming traffic to an external server outside our
> network. Our server has only one network device.
> Under Linux this was not to hard too do. Is this possible
> on a 2003 server?
>
> Sincerely,
> Niels

You need to be more clear. "Forwarding", contrary to the name, actually
goes "backward". Maybe it should be called "backwarding". The firewalls
forwards something it receives from the outside to something on the
inside,...not the otherway around.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Niels" <(E-Mail Removed)> wrote in message
news:2d09201c46975$1eee4b80$(E-Mail Removed)...
> I have a MS Server 2003 sitting behind a firewall that
> lets through only communication on a certain port and
> sends it to the server. I would like to know whether, I
> can set up the server so that is simply forwards all
> incoming traffic to an external server outside our
> network. Our server has only one network device.
> Under Linux this was not to hard too do. Is this possible
> on a 2003 server?
>
> Sincerely,
> Niels

Sorry, here the clearifications:

you are right "backwarding" would be a better term to
use. My windows server sits behind a hardware firewall
that is open on a certain port for traffic coming from
certain IP addresses. The firewall forwards the packages
to my windows server. I would now like the server to send
the traffic back to a specific server outside of our
network.

What we are trying to accomplish:
I am sharing a data service with some colleagues. If each
of us would connect the providing server directly we have
no access control. So if somebody forgets to log out he
blocks the service for all others and it is very
complicated to call people to check whether or not they
have logged out correctly.
So the solution I was thinking of is to route all traffic
through central server. Then one can monitor who is
logged on and if needed, we can cut somebody off to allow
access for others.
Of course it would also be possible to restrict the
access to the service not by the hardware firewall, but
by the firewall on the windows server. It might even be
easier to configure.

Hope this helps.
Thanks for your efforts so far!

Niels

>-----Originalnachricht-----
>You need to be more clear. "Forwarding", contrary to
the name, actually
>goes "backward". Maybe it should be
called "backwarding". The firewalls
>forwards something it receives from the outside to
something on the
>inside,...not the otherway around.
>
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>"Niels" <(E-Mail Removed)> wrote in
message
>news:2d09201c46975$1eee4b80$(E-Mail Removed)...
>> I have a MS Server 2003 sitting behind a firewall that
>> lets through only communication on a certain port and
>> sends it to the server. I would like to know whether, I
>> can set up the server so that is simply forwards all
>> incoming traffic to an external server outside our
>> network. Our server has only one network device.
>> Under Linux this was not to hard too do. Is this
possible
>> on a 2003 server?
>>
>> Sincerely,
>> Niels
>
>
>.
>

"Niels" <(E-Mail Removed)> wrote in message
news:2d6d201c46a41$ad540640$(E-Mail Removed)...
> certain IP addresses. The firewall forwards the packages
> to my windows server. I would now like the server to send
> the traffic back to a specific server outside of our network.

It should already be able to. That is the easy part, as long as your allowed
at the firewall the outbound type of traffic it uses, then it should already
be able to do that.

> I am sharing a data service with some colleagues. If each
> of us would connect the providing server directly we have
> no access control. So if somebody forgets to log out he
> blocks the service for all others and it is very
> complicated to call people to check whether or not they
> have logged out correctly.

The problem is the louse quality of the software (the "data service") that
is performing this task. The Software is responsible for accepting,
deniying, opening, and closing connections. You can not use firewalls or
additional servers to overcome bad programming of an application.

The solution is to fix or replace the software that makes up this "data
service".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com