Sitting on broken static routes on a saturday. Thanks Fortigate.

I wonder if I should restrain myself and avoid filling this post with the profanity filling my head, maybe you can help conquer some peace of mind. Because it's either you or booze, and it's just 1 PM in central Europe.

The scenario, branch office can't print from Remote Desktop over IPSec tunnels, printer are offline.Better yet: printer would be online, if the gateway (the same Fortigate managing VPN, Route and Policy on the RD-Site) wouldn't decide to actually play dice with the routes.

​

This is the connection from the RD-Source to Printer Nr. 1 on remote site

tracert 192.168.204.153

1 <1 ms <1 ms <1 ms 192.168.168.1 <-- hello gateway

2 33 ms 33 ms 33 ms 192.168.0.164 <-- hello VPN gateway on the opposite side

3 35 ms 37 ms 45 ms 192.168.204.153 <-- hello Printer Nr. 1

​

Now watch what happens if I try to ping Printer Nr. 2, sitting on the same table, attached to the same switch, served by the same router, on the same VPN.

tracert 192.168.204.154

1 <1 ms <1 ms <1 ms 192.168.168.1 <-- hello gateway

2 1 ms 1 ms 1 ms 192.168.100.1 <-- uuh..where are you going, that's the modem's default route

3 12 ms 11 ms 12 ms a81-*-*-*.net-*.co.uk [81.*.2*4.**1] <-- ..and my ping gon fuck himself on the internet.

​

Any clue before I lose my mind?