Monday, October 19, 2020

Subnets Can Only Ping and Traceroute via Static Route

Hello all, I have an issue at a customer's business when it comes to static routing. They recently installed a laser cutter which has its own subnet and router for all of the devices and machines that are network controlled. This network is 192.168.100.0/24. This is connected to the business's main network through a switch and is passed through the 192.168.1.0/24 network which is the main network for the rest of the buildings.

I have this configured so the port that faces the 192.168.1.0/24 network from the router in the laser has the IP of 192.168.1.50, and the port that faces the 192.168.100.0/24 network set as 192.168.100.200(which cannot change).

To connect the networks together, I have a static route from the 192.168.1.50 router sending all packets to 192.168.1.1 that are destined for the 192.168.1.0/24 network. On the 192.168.1.1 router I have a route sending all packets for the 192.168.100.0/24 network to 192.168.1.50. The 192.168.1.50 router also has a default route to 192.168.1.1.

All traffic seems to pass through fine with ping and trace route. The 192.168.1.50 IP will also show up on a IP scan along with the entire 192.168.100.0/24 network. It also seems to pass all the other traffic as the logs on the 192.168.1.1 router show other traffic such as tcp and udp can be seen from both networks. However, whenever I try any connection such as mapping a shared folder or remote desktop connection it will show the traffic on the 192.168.1.1 router as being passed through and not blocked but the termination is always "time-out" after passing a few packets.

The only thing the firewall currently blocks is connections to the internet for the 192.168.100.0/24 network. The firewall on the 192.168.1.50 router is entirely disabled.

192.168.1.1 router is palo alto

192.168.1.50 router is a bintec r232 router

Thanks For the help!



No comments:

Post a Comment