CompterConnector: Enable to connect the computer to the server

Hi!

I’m trying to connect computers from my network to the server, but in all cases the software failed after given the server password, with this error:

Cannot connect this computer to the Network

An unexpected error has ocurred. For more information, see Troubleshoot connecting computers to the server.

I had seach in google for this error and i already read a lot of postings about it, but nothing seems to resolve.

this is my ClientDeploy.log file:

====================================================================================

[308] 130322.144303.9303: ClientSetup: Start of ClientDeploy
[308] 130322.144304.1024: General: Initializing…C:\Windows\Temp\Client Deployment Files\ClientDeploy.exe
[308] 130322.144304.1104: ClientSetup: Loading Wizard Data
[308] 130322.144305.2816: ClientSetup: Current DeploymentStatus=Running
[308] 130322.144306.1004: ClientSetup: Showing the Client Deployment Wizard
[308] 130322.144306.2135: ClientSetup: Adding Server Info data in the Product Registry
[308] 130322.144306.2436: ClientSetup: Set the Deployment Sync Event
[8620] 130322.144313.7731: ClientSetup: Running ValidateUser Tasks at WizardPage HomeServerCred
[8620] 130322.144313.7791: ClientSetup: Entering ConnectorWizardForm.RunTasks
[8620] 130322.144313.7791: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
[8620] 130322.144313.7841: ClientSetup: Entering ValidateUserTask.Run
[8620] 130322.144313.8292: ClientSetup: Install root cert to local trusted store
[8620] 130322.144313.8362: ClientSetup: Validating User
[8620] 130322.144313.8372: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[8620] 130322.144333.6880: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus
 em Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
 em Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[8620] 130322.144333.6880: ClientSetup: Exiting ValidateUserTask.Run
[8620] 130322.144333.6880: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
[8620] 130322.144333.6880: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[8620] 130322.144333.6880: ClientSetup: Exting ConnectorWizardForm.RunTasks
[308] 130322.144333.6920: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
[308] 130322.144335.5268: ClientSetup: Back from the Client Deployment Wizard
[308] 130322.144335.5549: ClientSetup: Saving Wizard Data
[308] 130322.144335.5569: ClientSetup: End of ClientDeploy: ErrorCode=1603

====================================================================================

For me and as i can understant the problem is on the server, cause all computers i had try i have the same problem.

Any help would be very appreciated.

Thanks in advanced.

Look like a cert mismatch

http://support.microsoft.com/kb/2686291

and

http://social.microsoft.com/Forums/en-US/whshardware/thread/ec737eb7-10f2-48ef-aad5-3de6f6dea28b

These say sbs 2011 and whs 2011, but all 3 are the same codebase including WSSE

(same answers as the thread below, can’t log into dashboard)

Thanks Gramps for the contribute,

I already had seen this links and check every single step… and had the same problem connecting the clients computers.

I think the problem is associated to the acess to the Certificate file, cause i receive this warning when i test the certificate:

The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <computer_name>$ has Read access to the physical path. Then test these settings again.

Anyone nows how to deal with this issue?

I inserted some pics but it may take a while for them to show up, but I have the same error you mention, but mine works, so I don’t think that is the issue

Also check your app pools for the corect version of dot net.  should be 4.0

PS:  Just figured out why it takes a while for pictures to show up :confounded:

They say waiting for aproval.  So a person has to get around to looking at them before they can be seen.

I can see the print screens!

Yes this is what i see in my server. Thought the issue was that… if it’s not, what’s going wrong…

Really needing to resolve this issue, cause at the moment i do not have any computer connected to the WDDX4000, so i do not make any backup from the clients computers.

Thanks for trying helping me.

All checked!

All 4.0 dot net framework!

Thanks for helping me.

Sorry to be so slow in my reply.  I got 3 emails from here in a row and the 3rd one said he fixed it.  I did not notice it was 2 diff threads.

Hvae you installed anything on the server?  Run the connect to the inet wizzard?  Done anything you should not do :slight_smile:

Let me do some more looking.

Are your clients XP?

If you receive an error that says “The Connector has encountered an unexpected error” please also check if the NetTCPPortSharing service is in starting status but not successfully started. In some situations, NetTCPPortSharing service fail to start on XP client with .NET 4.0 installed. That may caused by several reasons including

1.LocalService account does not have proper access rights to the root of the C: drive
2.LocalService account does not have proper access rights to the C:\Windows\Microsoft.NET\Framework\V4.0.30319\SMSvcHost.exe.Config file 3. “The disk on which the C: Volume exists is a Dynamic disk”

You may be able to resolve this issue by perform the following steps:

1.Give LocalService account Read permission to C:\Windows\Microsoft.NET\Framework\V4.0.30319\SMSvcHost.exe.Config
2.OR Give LocalService Read and List Folder Contents permission to the root of C:          

Hi!

As i can remember i did not! Just joined the server to the local domain, and configure the acess to only a group, cause my domain users exceed the limit of 25 users.

Hi!

As i told before i can’t connect any computer. I try to connect 3 differents computers, 1 Vista OS, other 7 OS and other WinXP OS and was enable to connect all them. That’s why i suspect the problem is at first side in the server.

At this moment and after spending a long time with this issue, searching and reading in internet some issues like this, i really son’t know how to solve the problem…

Sorry you are having such a hard time.  I am still looking.

In the meantime for giggles, could you go through the domain wizzard and unjoin from the domain and try it?

Thanks Gramps for all your interest and help.

Ok! Will unjoin the domain and try the connector software install!

Will post here the results.

Once again, thanks.

Hi!

Had unjoined the server from the domain and pass the connector software again and unfortunately the result is the same, the connector software fails after entering the server password with the same error message “An unexpected error has ocurred. For more information, see Troubleshoot connecting computers to the server.”

Something had to be wrong in the server, but what?

Hi!

Looking at the ClientDeploy.log file it seems to have some problems with the user ID:

=======================================================================================

[6980] 130326.121002.3202: ClientSetup: Exiting ValidateUserTask.Run
[6980] 130326.121002.3202: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Retry
[6980] 130326.121002.3202: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[6980] 130326.121002.3202: ClientSetup: Exting ConnectorWizardForm.RunTasks
[6980] 130326.121034.9385: ClientSetup: Running ValidateUser Tasks at WizardPage HomeServerCred
[6980] 130326.121034.9385: ClientSetup: Entering ConnectorWizardForm.RunTasks
[6980] 130326.121034.9385: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
[6980] 130326.121034.9385: ClientSetup: Entering ValidateUserTask.Run
[6980] 130326.121034.9385: ClientSetup: Install root cert to local trusted store
[6980] 130326.121034.9415: ClientSetup: Validating User
[6980] 130326.121034.9425: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[6980] 130326.121049.1523: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus
   em Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
   em Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[6980] 130326.121049.1523: ClientSetup: Exiting ValidateUserTask.Run
[6980] 130326.121049.1523: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
[6980] 130326.121049.1523: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[6980] 130326.121049.1523: ClientSetup: Exting ConnectorWizardForm.RunTasks
[9172] 130326.121049.1553: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
[9172] 130326.121051.5625: ClientSetup: Back from the Client Deployment Wizard
[9172] 130326.121051.5655: ClientSetup: Saving Wizard Data
[9172] 130326.121051.5675: ClientSetup: End of ClientDeploy: ErrorCode=1603

=======================================================================================

The credentials use in the Client Connector Wizard are the password of the Administrator of the Server. The wizar don’t ask for the user only for the password, so it should assume that the user is the Server Administrator, but of course the user in client computer is not the administrator of the server, but a domain administrator user.

I had try to connect using a local user called “Administrador” and it still fails. I try using the domain admin password and the wizard inform that it’s not a valid password…

Anyone have and idea how to solve this issue?!

What domain are you joined to?  I do niot think this is the answer but you can look at it.

http://wdc.custhelp.com/app/answers/detail/a_id/6578/~/on-a-wd-sentinel-dx4000,-2003-active-directory-domain-users-can-not-be-seen

I have one joined to an SBS 2011 domain that has the administrator account disabled on the domain, but administrator still works on the local box.

Do you have a spare/clean desktop not joined to your domain you might try?  Or it may be simpler/quicker to just restore the server to new and start over?

i gave up on this issue. im glad i still got 30 days to return my product.

i endup resetting my unit to factory default, and still did not fix the issue, too much headache for me thats why i decided to return and exchange it with another one. now its working great! but have an issue with backing-up windows 8 pc’s.

I have been around this issue, for weeks… and until now i had not found solution for it.

I ask for help to WD Support Service. I received an email with a lot of questions about my network enviroment, but i were enable to reply the message, cause the sender address is always reject by the e-mail server.

I attach a PDF file with the answers to the question they make att the supoport id, hoping someone would see the file and message me with some ideas to solve this issue, but untill now no one e-mail me again.

I don’t want to gave up, but at moment i have no more ideas what to do.