None of these are running on port 1433, both server are running SQL Browser under NT Authority\Local Service
It's not mandatory thing to run SQL services to listen on port# 1433, seems the ports are customized in your case, which is good in security point of view. Also, SQL Browser service is not necessary if you have fixed port for SQL Service (named instance) and you are mentioning that port in connection i.e. hostname,1499
Ping of just the NetBIOS name works just fine, ping -a resolves the FQDN
I think you should also tried, telnet SQLServer-0 1499 to confirm that the SQL Service is listening on particular port and that is not blocked by firewall, these steps may help for further troubleshooting
Windows Failover cluster for SQL AG testing
In this case, you need also to check on Endpoint ports not only the SQL ports. To get configured end points SELECT type_desc, port FROM sys.TCP_endpoints