I got a question
I recently needed to add a static route into a windows server for it to communicate with an specific infrastructure environment. I have always added static routes without any issues previously, but somehow this one made the server to disconnect and no longer communicate (remote desktop was no longer available and the application hosted on the server was not communicating as well, so in other words the network communication was broken)
the server had the ip "10.250.115.21" and I added the static route
"route add -p 10.196.12.12 mask 255.255.255.0 10.250.115.1"
(route add -p "ip address" mask "- "gateway")
and right after I entered this route, the server froze and I was no longer able to connect through remote desktop, and the network communication was broken.
so...my question is: can a static route make this happen?
I know that by deleting a static route may cause this (if the wrong is deleted)
but may this occur by just "adding" the wrong static route?
since I always thought that the worst thing that could happen when adding the wrong static route is to receive a message that the syntax is incorrect or that the scope is not supported by the specific network environment.
please let me know if I was the one who screwed the communication of the server by adding the wrong static route or if it was just coincidence that happened