F5F Stay Refreshed Power Users Networks TCP on port 3000 PPP

TCP on port 3000 PPP

TCP on port 3000 PPP

R
RauloMenino
Member
Find
224
08-23-2016, 08:49 PM
#1
Hi, everyone. I’ve been experiencing this problem a few days after rebooting. As a developer, I usually work with localhost servers on TCP port 3000. It seems like the system is now forcing me to pick random ephemeral ports when launching my test server, even though port 3000 appears to have a service running. The netstat command shows no processes on tcp/3000, and nmap reports it as closed with a PPP service. I can’t connect to the port, and there’s nothing unusual running on my machine—Windows 10 2004 build 19041:450. I’m using WSL2 and Docker Desktop, which should handle localhost 3000, but I’m still stuck. I’ve never installed anything suspicious, and I haven’t downloaded any unknown software. Recently, I used balenaEtcher to flash a Raspberry Pi OS onto a flash drive around this time. I’m trying to stay cautious and want to make sure this isn’t some accidental activity before assuming malware. Have anyone encountered a similar issue?
Reply
Reply
R
RauloMenino
08-23-2016, 08:49 PM #1

Hi, everyone. I’ve been experiencing this problem a few days after rebooting. As a developer, I usually work with localhost servers on TCP port 3000. It seems like the system is now forcing me to pick random ephemeral ports when launching my test server, even though port 3000 appears to have a service running. The netstat command shows no processes on tcp/3000, and nmap reports it as closed with a PPP service. I can’t connect to the port, and there’s nothing unusual running on my machine—Windows 10 2004 build 19041:450. I’m using WSL2 and Docker Desktop, which should handle localhost 3000, but I’m still stuck. I’ve never installed anything suspicious, and I haven’t downloaded any unknown software. Recently, I used balenaEtcher to flash a Raspberry Pi OS onto a flash drive around this time. I’m trying to stay cautious and want to make sure this isn’t some accidental activity before assuming malware. Have anyone encountered a similar issue?

Reply
Reply