One can do a basic test of TCP using Putty. UDP is another matter, one must have a server process and a sender. I found the simple sender and server written in Powershell here:
cloudbrothers.info/en/test-udp-connection-powershell/
to be excellent. In addition, if you want to know the identity of the process listening on a port, run this:
Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess
100 Kbps is more than enough.
https://github.com/billziss-gh/sshfs-win
CLI command:
net use X: \\sshfs\login@hostname.fqdn
To set a Windows NIC to full DHCP via netsh, do this, replacing “Local Area Connection” to the name of the NIC if it’s not the same:
netsh interface ip set address "Local Area Connection" dhcp
netsh interface ip set dns "Local Area Connection" dhcp
netsh interface ip set wins "Local Area Connection" dhcp
Sometimes, if WINS is set static, you have to do this before WINS can be set DHCP:
netsh interface ip set wins "Local Area Connection" static none
To learn what is going on NetBIOS-wise on your LAN, in Windows, do this:
NBTSTAT -r
This will get you something like the below. If you have WINS active — which is essential for NetBIOS and group policy over a VPN if you don’t do IPv6 — you will see the names resolved by name server as below. If not, if names are resolved by broadcast, you don’t have WINS, and NetBIOS will not work across VPN.
NetBIOS Names Resolution and Registration Statistics
----------------------------------------------------
Resolved By Broadcast = 0
Resolved By Name Server = 1187
Registered By Broadcast = 0
Registered By Name Server = 6