Windows Routing Issue.

[pedro_oz]

Hi Folks,

I've got a problem that has me stumped.

I'm connecting to a network via an openvpn connection to a gateway machine that is translating traffic onto a network.

All the linux VM's seem to be working fine. Using tcp dump I can see the ping tests from my client (10.80.0.5) being rounted happily and replied to happily on the network.

The windows physical server on the other hand, gets the requests OK (using wireshark to test) but never tries to reply by the looks of things (rdp traffic vanishes as well).

I know this is probably NOT an openvpn issue, but I wonder if some one can give me some pointers.

I can see traffic coming into the windows nic as icmp from 10.80.0.5 -=> 10.80.2.80 but there is no reply.

I found there was no route back to the 10.80.0.0/24 network so trying to ping back the other way (from 10.80.2.80) was trying to go out the default gateway rather than via the lan nic (10.80.2.80) so I added a route

route add 10.80.0.0 mask 255.255.255.0 10.80.2.200 (this is the firewall hosting the opnevpn connection) and I could then ping from the windows box to the openvpn client, but still not the other way around.

What have I missed? It seems all of the traffic hitting the 10.80.2.80 nic just goes into the bit bucket somewhere.

Any ideas please?
Ta
Peter.

[pedro_oz]

Sorry. Please delete this topic.

I just turned off windows firewall to see what would happen, and guess what... it just worked.

Far out.

Now to work out the rules I need.

Peter.

[Pippin]

Hi,

It is somewhat known that some Windows installs block traffic from outside it's own subnet.

I'll leave it for now unless you object.
.