It has two NICs, one on our internal LAN, one on a segment with our ISDN
router for internet access.
We want to be able to "access the internet" from our workstations on the
LAN, I would like to know the best method of achieving this. Proxy Server
is doing Winsock and Web proxying fine.
However, if I ping from my workstation an external site, the server does
not route it. We have the correct default gateway and I have done a
Network Monitor trace confirming that the ICMP packets are making it around
the LAN, but not coming out the other card in the server. The server
functions fine with it's external link, it just does not seem to think it's
supposed to route IP.
What is the general consensus? That the majority of internet type
applications are Web or based or support Winsock Proxying? From a personal
point of view I would still like to be able to ping from my workstation for
testing purposes etc.
Another curiosity. If from my workstation, I ping the the *internal*
address of one of our client sites, RRAS will initiate a dial on demand
connection (the internal address of our client site is configured in RRAS
as a dial on deman interface).. My ping returns "request timed out" as
though it thinks it should have a route. If I ping the same address from
the server, the dial on demand connection is established and then I *do*
get a response.
Documentation I have read says that RRAS enables routing by default and
that you have to apply packet filtering to lock it down. This is not
working for us, there is a little note in the RRAS Installation Guide about
not changing the "Enable IP Routing" check box in TCP/IP properties. We
have not touched this, do we perhaps need to?
There are no filters configured in Proxy Server 2.0 either. If someone
could possibly come up with a few guidelines on getting NT routing to work
I would be most appreciative. Pls respond via email to:
Thanks!
---
Michael Harrod (mha...@clear.net.nz)
"You fight today, you fight to die..." - This Mortal Coil
---