I have recently set up a new server running SBS 2011 and everything has gone wonderfully till this point. There are four computers at the moment that I have installed the connector on via http://
"server name"/connector. One of these computers shows up just fine, I am able to schedule backups and all of it. The other three all show up as offline and all detail shows unavailable. I have searched and searched for a solution to no avail. The computers are running Windows 7 x64 Pro and have all updates etc.
When looking through the event viewer there were two items coming up:
Faulting application name: SMSvcHost.exe, version: 4.0.30319.449, time stamp: 0x4d92dcc1
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xe58
Faulting application start time: 0x01cd7c9a90d17073
Faulting application path: C:\Windows\Microsoft.NET\F
Faulting module path: C:\Windows\SYSTEM32\ntdll.
Report Id: f857c65a-e88d-11e1-98cc-50
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0000000180009E4B
upon looking through the logs to try and pinpoint something i found where the error occurs when the connector tries to talk with the server and it tells me:
EndOpen indicated that the connection attempt failed: (EndpointNotFoundException
) Could not connect to net.tcp://"computer-name
egistry. The connection attempt lasted for a time span of 00:00:02.0013084. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.1.12:6602. ==> (SocketException) No connection could be made because the target machine actively refused it 192.168.1.12:6602
I have completely uninstalled any antivirus software/firewall software, disabled the windows firewall, opened up the firewall in my soekris device and nothing seems to work.
It seems to be a problem with .net but an sfc /scannow does not solve the issue. ran the .net verification tool from ms and all of the .net platforms checked out okay.