Adding an "any" rule causes client to randomly lose gateway
I have 2 networks, LAN and MANAGEMENT, both on different subnets, vlans etc. I need one particular client on LAN to access the resources on MANAGEMENT. When I add a rule to allow access the client will randomly "lose" its default gateway. Windows won't at first catch the problem but eventually it'll give an error. Resetting the eth adapter on the client fixes the problem temporarily. How can I permanently fix this?
EDIT: It was a NIC issue. I had it plugged into a unTagallbutPvid port on the switch and the crappy display port ethernet NIC would switch between the vlan I selected and vlan 0 (nothing).
No possible way adding that rule can affect the client like that. Look elsewhere.
And if your client is on LAN, adding a rule on MANAGEMENT has no bearing on whether the LAN client can access it or not.
I've seen this when.
Check to make sure you have allowed traffic to access both interfaces, not just one way.
| quote: "When I add a rule to allow access the client will randomly "lose" its default gateway"
Where / what on windows does this? More info on the setup / error.
This client network setup on Windows should not be any different than any other LAN client.