IP Block List Communication Problem?

Question

Hi,
Im trying to set up IP Block List Providers on a very simple Exchange environment consisting of two servers.
Server1 = Client Access and Mailbox roles (domain joined)
Server2 = Edge role (not domain joined) 
I Setup my Block Lists Providers on Server1 then run the PowerShell command "Get-IPBlockListProvider" which then returns the providers I setup. Now if I change to Server2 and run the same PowerShell command it does not list any
configuration. My first thought was that the AD LDS instance on the edge was not updated so I ran the command Start-EdgeSynchronization -ForceFullSync -Server Server1 -TargetServer Server2 to force an update on the edge, then Test-EdgeSynchronization –FullCompareMode
which reports everything as synchronized.
Why is the configuration not showing on the Edge? Could there be a communication issue or should I be adding the Block List Providers Directly on the Edge without being able to see the configuration from Server1?
The reason I suspect communication is because when I open the ECP on Server1 (FrontEnd) click Servers and double click the Edge (Server2) I get the following error message “An error occurred while accessing the registry on the server
"Server2.domain.local". The error that occurred is: "The network path was not found". Ive checked the DNS, im able to ping the DC and the front end (server1) from the edge. Im also able to map the C$ share of the DC and Front End. 
Appreciate any help on this. 

Answer 1

Hi,
Thanks for your reply. It looks like the IP Block lists are working when deployed directly on the edge. However the message from ECP – “An error occurred while accessing the registry on the server "server2.domain.local".
The error that occurred is: "Attempted to perform an unauthorized operation.” Still remains.
As described in the first suggestion attempted to use ldp to connect to the edge, it connects but it give me a server error, dont know if it’s supposed to be like that or not.
ld = ldap_open("server2.domain.local", 50636); Established connection to server2.domain.local. Retrieving base DSA information... Server error: <empty> Error<94>: ldap_parse_result failed: No result present in message
Server error: <empty> Getting 0 entries: ----------- Server error: <empty>
Mavis, thanks for your suggestion regarding the 137-139 and 445 ports. I opened these ports in the Windows firewall but again the problem remains. To make sure there is nothing blocking traffic between the front end and the edge, I completely
disabled the firewalls on the edge and front end, as well as any firewall between them while I tested but still the same error.
I also tried to do google some more and there are several mentions of the “Remote Registry Service” being disabled. This service was indeed stopped on both the front end and edge, starting the service made no difference. Since the thread
started I have also updated both servers to CU6 (first the front end then the edge) hoping that there was some fix in the latest updates from Microsoft, but unfortunately no. The strange thing is that now in the ECP console the edge is returning a lower build
version than the front end, but if I run a PowerShell command directly on the Edge it returns the correct build number. I suppose that the next step would be to run Wireshark or similar to see if the traffic is actually going through.