Looking at Windows VVR doc it seems very poor - it is better in UNIX - I'll explain futher:
The ports you have listed above are not for replication data, they are for other uses (heartbeat, vradmin communication, vxrsyncd communication and VEA GUI) - these are the exactly the same port numbers as UNIX, but the UNIX guide also tells you the default for VVR data which is UDP/TCP anonymous ports. I believe UDP/TCP anonymous ports are an O/S construct so VVR uses the "anonymous ports" as defined by the O/S. I don't know if VVR on Windows also uses "anonymous ports", but runnning "vrport data" might tell you - I say might as I have a feeling on UNIX that output is just blank. So on UNIX, if you have a firewall, then you have to use specfic ports using "vrport data" to specify the ports, so you will need to do this, unless the default for Windows (if vrdata port shows this) is a small range of ports that you can add to firewall "allowed ports"
If you run vrport by itself it should show you ALL ports - ones listed above and data, all of which you can change using vrport. VEA port is not a VVR port, it is for VEA GUI, but you can use CLI to control VVR.
Mike
