Have been using Vuze on Windows server for 4+ years, quite fine.
Peerblock blocks Vuze incoming UDP/TCP ports when executing.
Using Vuze works fine for a weeks. Then noticed that Peerblock wasn't running.
Started Peerblock and Vuze was immediately blocked. Test when Vuze not working.
Added two ports used on Vuze to Peerblock Port settings page, although never
needed these before. Did another test on Vuze Port/Firewall test after
restarting Vuze/Peerblock but still not working.
Updated to Peerblock 1.2 (r693). Don't know if it was the version that was
previously on it, but still blocked.
OS Name Microsoft Windows Server 2012 Standard
Version 6.2.9200 Build 9200
Other OS Description Not Available
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 4
Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1908, 14/03/2013
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume4
Locale United Kingdom
Hardware Abstraction Layer Version = "6.2.9200.16442"
User Name
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 12.9 GB
Total Virtual Memory 18.2 GB
Available Virtual Memory 14.9 GB
Page File Space 2.25 GB
Page File F:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Original issue reported on code.google.com by Bob.G.Wa...@googlemail.com on 13 Apr 2014 at 12:32
Original issue reported on code.google.com by
Bob.G.Wa...@googlemail.comon 13 Apr 2014 at 12:32