Controlling a KD Connection Server Session
Once the remote session has been started, the smart client can be used as if it were debugging the target computer from the computer where the KD connection server is running. All commands will behave as they would in this situation, except that paths are relative to the smart client's computer.
After WinDbg is started as a smart client for a KD connection server, you can use the Debug | Stop Debugging command to end the debugging session. At that point, WinDbg will enter dormant mode and will no longer be connected to the KD connection server. All subsequent debugging will be done on the computer where WinDbg is running. You cannot reattach to the KD connection serve by using File | Kernel Debug -- this can only be done from the command line.
KD or WinDbg can exit or end the debugging session in the normal fashion. See Ending a Debugging Session in WinDbg
for details. The KD connection server will remain in operation and can be re-used as many times as desired. (It can also be used by for any number of simultaneous debugging sessions.)
The KD connection server can be terminated from either computer. To terminate it from the smart client, use the .endpsrv (End Process Server) command. To terminate the KD connection server from the computer it is running on, use Task Manager to end the kdsrv.exe process.