In mirrored network mode, the adb devices command will be blocked

Nobody has claimed this yet.

### Windows Version

Microsoft Windows [Version 10.0.22631.3296]

### WSL Version

2.1.5.0

### Are you using WSL 1 or WSL 2?

- [X] WSL 2
- [ ] WSL 1

### Kernel Version

5.15.146.1-2

### Distro Version

Ubuntu 22.04

### Other Software

adb version:
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
Installed as /usr/lib/android-sdk/platform-tools/adb

adb.exe version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
Installed as D:\Program Files (x86)\Android\SDK\platform-tools\adb.exe


### Repro Steps

1. Turn on the computer, start wsl2
2. Use the `adb devices` command, it will be blocked
3. Use the` adb.exe devices` command, you can get the machine list
4. Use the `wsl --shutdown` command, kill wsl2
5. Reopen wsl2, use the `adb devices` command, you can get the machine list

Why do you have to restart once before you can use the adb devices command?

### Expected Behavior

the first time use `adb devices` ， you can get the machine list

### Actual Behavior

the first time use `adb devices` ， you can get the machine list

### Diagnostic Logs

_No response_
```[tasklist]
### Tasks
```

Start by reproducing the reported WSL 2 mirrored-network behavior with `adb devices` and `adb.exe devices`, following the listed startup and `wsl --shutdown` steps. Compare the first-run behavior before and after shutdown; done means `adb devices` lists the machines on the initial WSL launch, without requiring a restart.

Written by the indexing model from the issue text.