Problem is that one of our (remote) sites uses public internet adresses. I
want to prevent our mailserver (win2k server with exchange 5.5.) to send
129.x.x..x and 130.x.x.x traffic to the default gateway.
I have tried it with the route add command and select 0.0.0.0 or 127.0.0.1
as the gateway, however without much success.
Also via routing and remote access console it doesn't seem to work
(130.0.0.0 with mask 255.255.255.255 via gateway 127.0.0.1)
Because I want to have the entire 129 and 130 range 'blocked'.
Does anybody know a solution for this?

Thanks,

Rolf
Utrecht, Netherlands

You could configure an ipsec policy on that computer to manage network traffic
by using permit and bock filter actions similar to a firewall. See link below
for how to do that. --- Steve

http://www.securityfocus.com/infocus/1559
http://www.microsoft.com/windows2000...ipsecsteps.asp

"RW" <(E-Mail Removed)> wrote in message
news:3fba8899$0$249$(E-Mail Removed)...
> Problem is that one of our (remote) sites uses public internet adresses. I
> want to prevent our mailserver (win2k server with exchange 5.5.) to send
> 129.x.x..x and 130.x.x.x traffic to the default gateway.
> I have tried it with the route add command and select 0.0.0.0 or 127.0.0.1
> as the gateway, however without much success.
> Also via routing and remote access console it doesn't seem to work
> (130.0.0.0 with mask 255.255.255.255 via gateway 127.0.0.1)
> Because I want to have the entire 129 and 130 range 'blocked'.
> Does anybody know a solution for this?
>
> Thanks,
>
> Rolf
> Utrecht, Netherlands
>
>
>