Re: What is using Android adb port 55555 and/or 5555 on Windows
Andrew <[email protected]> Sun, 21 Jul 2024 14:38:04 -0000 (UTC)
| Newsgroups | comp.mobile.android,alt.comp.os.windows-10,alt.comp.networking.connectivity |
|---|---|
| Organization | BWH Usenet Archive (https://usenet.blueworldhosting.com) |
| Message-ID | <[email protected]> |
Andy Burns wrote on Sun, 21 Jul 2024 14:44:01 +0100 : >> 2. netstat -anb | findstr 5555 >> 3. Which reported: >> TCP 127.0.0.1:55555 0.0.0.0:0 LISTENING > > Using findstr is not useful when using netstat -nb because the name of > executable is not on the same line of output as the port number you're > matching. Good point. If it were Linux and not Windows, it would be easier (as I learned UNIX well before Windows existed, like most of us here). Long ago I had a syntax-correct example in both Linux & Window for running grep/findstr that also did a cat/tail of a given number of lines *after* the match - but I've lost that syntax in the ensuing years. Looking it up, there are many people trying to reproduce grep on Windows, and yes, like everyone, I've used the CYGWIN & WSL Frankenstein shells. https://superuser.com/questions/300815/grep-equivalent-for-windows-7 Taking your kind & helpful advice into hand, what I'll do is pipe the standard out results to a file and then I can search using Vim (which is my default text editor since my finger memory has lasted for many decades). Much appreciated.