Using the Routing and Remote Access Service to create a lan Routing and Remote Access Service function is not nonsense here. the reason for writing this note is that rras is usually used for vpn and nat. but in a virtualized environment, sometimes you have to split your network, but you do not have to divide it into many VLANs, or you want to perform simple isolation in the vlan. therefore, using windows server as a simple lan route to connect your two networks is also a very convenient method. the Static Routing rules under rras are a little different from those of common routing devices. here is a simple record. 1. install Routing and Remote Access Services. 2. when selecting a function, you only need to select a lan route. 3. in ipv4 --- General, add two network interfaces for connecting the two networks. 4. add a static route to the two networks. static route setting rules: for example, I now have two networks: 172.16.0.0/16192.168.80.0/24. The IP addresses connecting to the two networks on my windows server are: Nic 1: 172.16.80.1/16 Nic 2: for 192.168.80.1/24, the static route to 192.168.80.0 is: interface: Nic 2 destination: 192.168.80.0 network mask: 255.255.255.0 Gateway: 192.168.80.1 hops: 1 to 172.16.0.0 the static route is: interface: nic 1 destination: 172.16.0.0 network mask: 255.255.0.0 Gateway: 172.16.80.1 hops: 1 I always configured wrong, because the next address is usually configured When configuring the router. some people simply configure two rras servers to connect two network segments. in fact, we do not understand it correctly here. the router itself is connected to two CIDR blocks. you can set two IP addresses for a vro to connect the two networks. you do not need to set static routes. why does rras need to be set here, because you can bind multiple network interfaces to lan routes under rras. the Static Routing here is for the server itself. I want to go to the 192.168.80.0/24 CIDR block, so I will use the network card 1 with the IP address 192.168.80.1/24 on this server to send data.