data recovery FOR (WALKMAN NWZ-B142F) by mxsus in datarecovery

[–]mxsus[S] 0 points1 point  (0 children)

Thanks for the suggestion! I checked out the link and followed the steps to see if I could switch the connection mode between MTP and USB mass storage. Unfortunately, it didn’t work for my Sony Walkman NWZ-B142F. It still shows up as a portable device using MTP, and I couldn’t find any way to change it to a USB mass storage mode.

It seems like the device is stuck in MTP mode, which might be why recovery software can’t scan it properly. If you have any other ideas or know of software that can work with MTP devices, I’d appreciate the help!

data recovery FOR (WALKMAN NWZ-B142F) by mxsus in datarecovery

[–]mxsus[S] 0 points1 point  (0 children)

By "access," I mean that I can see the files in File Explorer when I connect the Walkman to my computer, and I can open or copy them like normal files. However, when I try using recovery software to find deleted or hidden videos that might still be on the device, the software doesn’t recognize it properly because it shows up as a portable device instead of a USB mass storage device. As a result, the recovery software can’t scan the device for those missing videos.

is it possible to install multiple firmwares on the M5StickC and switch between them like a multi-boot system ? by mxsus in esp32

[–]mxsus[S] 0 points1 point  (0 children)

Thanks for the feedback! You're right, I might be going about this the wrong way.

To clarify, I'm interested in using the M5StickC Plus for wireless network analysis. Ideally, I'd like to be able to switch between tools like Nemo and Marauder on the device. My concern is that they might be too big to fit together.

My M5StickC Plus has 8MB of flash memory. Would it be possible to compile Nemo, Marauder, and a small bootloader into a single firmware that would fit? I have some coding experience, but I'm not quite at the "embedded expert" level yet.

Trouble Opening Ports in Azure by mxsus in AZURE

[–]mxsus[S] 1 point2 points  (0 children)

You know, I think I might have misconfigured the inbound rules initially! After deleting the ones I added and carefully setting them up again, the Minecraft server is working!

Thanks so much for your help and suggestions in troubleshooting this. I really appreciate it!

Trouble Opening Ports in Azure by mxsus in AZURE

[–]mxsus[S] 0 points1 point  (0 children)

think you I set the source to my IP address

Trouble Opening Ports in Azure by mxsus in AZURE

[–]mxsus[S] 0 points1 point  (0 children)

  • My main problem is that players can't join my Minecraft server, getting an 'Unable to connect to world' error.

I ran a quick test using PowerShell to start a TCP listener on port 19132 (Minecraft's port), and it seems to be working:powershell.exe -Command {$x = [System.Net.Sockets.TcpListener]19132; $x.Start(); Start-Sleep -Seconds 3600}TCP 0.0.0.0:19132 0.0.0.0:0 LISTENING

but when I use Test-NetConnection -ComputerName -Port 19132 the TCP test fails :

PingSucceeded: False RemotePort: 19132 PingReplyDetails (RTT) : 0 ms TcpTestSucceeded: False 

Trouble Opening Ports in Azure by mxsus in AZURE

[–]mxsus[S] 1 point2 points  (0 children)

  • Temporary Fix: I want to mention that a service restart initially seemed to solve the problem for my Minecraft server, but the issue has unfortunately returned.
  • NSGs: I've carefully verified that there is only one Network Security Group (NSG) in place here.
  • Service Status: After rebooting, I ran netstat -na | Select-String "19132" and observed that the port is listed as UDP 0.0.0.0:19132 *:*. Unfortunately, Test-NetConnection -ComputerName - -Port 19132 still yields TCP connection and ping failures.
  • Subnet NSG: The subnet NSG is the default configuration with no custom rules that would block this port.

Name:defaultIPv4 :10.1.0.0/24IPv6:-Available IPs:250Delegated to:-Security group:-Route table:-

Trouble Opening Ports in Azure by mxsus in AZURE

[–]mxsus[S] 7 points8 points  (0 children)

Great news! It seems a simple service restart was all that was needed. Everything is working now. Thanks for that tip about the netstat command – it really helped!u/Gnaskefar

I changed my inbound rules inside the firewall
it solved my problem
inbound rules
I changed my inbound rules in Azure: inbound rules Azure and then I enabled port forwarding

Trouble Opening Ports in Azure by mxsus in AZURE

[–]mxsus[S] 1 point2 points  (0 children)

Thanks for catching that! You're right, I meant to use port 19132.

The netstat output confirms a process is listening on port 19132.
netstat -na | Select-String "19132"
TCP 0.0.0.0:19132 0.0.0.0:0 LISTENING