By default, kind uses docker to create the network subnet that will be used by it's containers. Docker's default network range has 172.{30,31}.XX.XX in the list and if your network overlaps with that, you will run into interesting issues of not being able to reach your intranet systems.
The alternate would be to create a docker network for kind and ask it to use that instead of creating a default subnet from it's pool.
docker network create --subnet 192.168.80.0/16 --gateway 192.168.80.1 -d=bridge -o com.docker.network.bridge.enable_ip_masquerade=true kind