Debugging over an Ethernet network has the following advantages compared to debugging over other types of cable:. The computer that runs the debugger is called the host computer , and the computer that is being debugged is called the target computer.
The host computer must be running Windows XP or later, and the target computer must be running Windows 8 or later. The host computer can use any wired or wireless network adapter, but the target computer must use a network adapter that is supported by Debugging Tools for Windows. Connect the network adapter of the target computer to a network hub or switch using and appropriate network cable. Connect the network adapter of the host computer to a network hub or switch using a standard cable or a wireless connection.
Begin configuring your host and target computers as described in Provision a computer for driver deployment and testing WDK 8. On the host computer, in Visual Studio, when you come to the Computer Configuration dialog box, select Provision computer and choose debugger settings.
For Port Number , accept the default value or fill in a value of your choice. You can choose any number from through The port that you choose will be opened for exclusive access by the debugger running on the host computer. Take care to choose a port number that is not used by any other applications that run on the host computer. Note The range of port numbers that can be used for network debugging might be limited by your company's network policy. There is no way to tell from the host computer what the limitations are.
To determine whether your company's policy limits the range of ports that can be used for network debugging, check with your network administrators. For Key , we strongly recommend that you use the automatically generated default value.
However, you can enter your own key if you prefer. You can also start a session with WinDbg by opening a Command Prompt window and entering the following command, where n is your port number and MyKey is the key that was automatically generated by bcdedit when you set up the target computer:. If you are prompted about allowing WinDbg to access the port through the firewall, allow WinDbg to access the port for all three of the different network types. On the host computer, open a Command Prompt window.
Enter the following command, where n is your port number and MyKey is the key that was automatically generated by bcdedit when you set up the target computer:.
Once the debugger is connected, and waiting to connect, reboot the target computer. One way to do restart the PC is to use this command, from an administrator's command prompt. After connecting to the target on the host, hit break on your debugger and you can start debugging. When you first attempt to establish a network debugging connection, you might be prompted to allow the debugging application WinDbg or KD access through the firewall. Client versions of Windows display the prompt, but Server versions of Windows do not display the prompt.
You should respond to the prompt by checking the boxes for all three network types: domain, private, and public. If you do not get the prompt, or if you did not check the boxes when the prompt was available, you must use Control Panel to allow access through the firewall. Use the check boxes to allow those two applications through the firewall. Restart your debugging application WinDbg or KD.
To keep the target computer secure, packets that travel between the host and target computers must be encrypted. We strongly recommend that you use an automatically generated encryption key provided by bcdedit when you configure the target computer.
Network debugging uses a bit key that is specified as four bit values, in base 36, separated by periods. Each bit value is specified by using up to 13 characters. Valid characters are the letters a through z and the digits 0 through 9. Special characters are not allowed. To specify your own key, open an elevated Command Prompt window on the target computer. Enter the following command, where w.
Scroll down and select OK , to save the firewall changes. Restart the debugger. The range of port numbers that can be used for network debugging might be limited by your company's network policy.
To determine whether your company's policy limits the range of ports that can be used for network debugging, check with your network administrator. The output will be similar to this. In the preceding output, the value of port is If the value of port lies outside the range allowed by your network administrator, enter the following command, where w.
After changing the target machine debugger settings, rerun the debugger on the host machine with the new port setting, and then reboot the target computer. The recommended range is between and The port that you choose will be opened for exclusive access by the debugger running on the host computer. Note The range of port numbers that can be used for network debugging might be limited by your company's network policy. To determine whether your company's policy limits the range of ports that can be used for network debugging, check with your network administrators.
If "Network debugging is not supported on any of the NICs in this machine" is displayed when you run kdnet.
The host computer can use any network adapter, but the target computer must use a network adapter that is supported by Debugging Tools for Windows. Begining with Windows 10 October Update 20H2 , the following options are supported to enable four types of debugging.
Use Device Manager on the target computer to determine the PCI bus, device, and function numbers for the adapter you want to use for debugging. For bus parameters, enter b. These values are displayed in Device Manager under Location on the General tab. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
Contents Exit focus mode. Please rate your experience Yes No. Routers are usually set up as DHCP servers. This setting lets computers join a network automatically. Select a network and click Properties. Under IP Settings , click Edit. Your network problems could be caused by your system. If that is the case, Windows could have possibly released a fix.
Try updating your Windows machine to the latest release. Click Check for Updates. If there are updates available, Windows will download and install them.
0コメント