DSC error while pushing to win 2008 r2 node

Question

Hello,
I'm starting to "play" with Powershell DSC. 
Right now I'm testing the push mode: I created a basic configuration with a few resources to test (file, script, package, etc.). Push to a win 2012 R2 node is working without any problem. Push to a win 2008 r2 node gives me the error:
The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL.
    + CategoryInfo          : ResourceBusy: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : HRESULT 0x80338112
    + PSComputerName        : servername
Node is win 2008 r2, all updates, wmf 4.0. "Enter-PSSession" is working, WinRS is working.
I'm not sure what to look for so any help would be appreciated.
Regards,
JP

Answer 1

No error on the remote node.
On the server I have those errors in Windows Remote Management:
The WinRM protocol operation failed due to the following error: The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP
URL..
and
WSMan operation Get failed, error code 2150859026
I also noticed this informational event:
WSMan operation Invoke started with resourceUri
http://schemas.microsoft.com/wbem/wsman/1/config/service
Does it means the remote node needs to access this URL?
That is a good question.  Many schema reesources are located locally so they do not need to be retrieved.
THat is pretty explicit.  Are you on a different subnet?  Is the firewall open for all remote management and WinRM
Are you going through a proxy?  Are you using an netbios name or an FQDN.  Note that an IP address might not work here.
¯\_(ツ)_/¯
Yes, server and node are on a different subnet, but in the same domain. network firewall is temporary wide open between the 2 servers. There is no internal proxy, however external access uses one. I'm using the FQDN.
For the record here is the MOF file for the node (some info obfuscated):
@TargetNode='myserver.mydomain.org'
@GeneratedBy=my_domain_admin_account
@GenerationDate=11/27/2014 11:00:14
@GenerationHost=MDC-DSC01
instance of MSFT_FileDirectoryConfiguration as $MSFT_FileDirectoryConfiguration1ref
ResourceID = "[File]FirstTest";
 Ensure = "Present";
 Contents = "This is a Test";
 DestinationPath = "c:\\temp\\FirstTest\\File.txt";
 ModuleName = "PSDesiredStateConfiguration";
 SourceInfo = "C:\\DSC\\firsttest.ps1::6::3::File";
 ModuleVersion = "1.0";
instance of OMI_ConfigurationDocument
 Version="1.0.0";
 Author="Me";
 GenerationDate="11/27/2014 11:00:14";
 GenerationHost="MDC-DSC01";