- Network configuration results in 10 minute operating system load time.
- Two Windows 10 systems, latest updates
- connected directly with ethernet cable (non-crossover)
- Static IPs on both
- Windows Kernel Network Debugging is enabled
- Windows Firewall is disabled on target
- Host machine has two network interfaces
- How does crossover connections affect broadcast packets?
- Could the network switch store-and-forward table be responsible?
- the 10 minute boot time hang is at spinning windows boot splash
- I assume the KDNET filter is having a hard time...
- When I connect both PCs to a network switch, problem solved
- when I disable network debug, problem solved
Connected to target 169.254.78.132 on port 50008 on local IP 192.168.128.1prints in WinDbg on connection, with network switch or crossover cable
Connected to target 172.29.2.197 on port 50008 on local IP 172.29.13.140is when DHCP is enabled on target, connecting through primary network interface.
- Leaving WinDbg closed (no kernel debug session open), still slow
- List of IP addresses of target as per netadapter
IP ADDRESSES unicast ffffd206bfefb040 - 192.168.128.100 multicast ffffd206bfef2040 - 184.108.40.206 multicast ffffd206ccdd1040 - 220.127.116.11 multicast ffffd206ccddb040 - 18.104.22.168 multicast ffffd206cd375040 - 22.214.171.124 broadcast ffffd206bfef8040 - 255.255.255.255 broadcast ffffd206ccda9040 - 192.168.128.255