Sincerely,
Niels
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" <anon...@discussions.microsoft.com> wrote in
message
>news:2d09201c46975$1eee4b80$a301...@phx.gbl...
>.
>