• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry
whs2011help

Connector Install Fail Xp 32 & Success For Win 7 64

8 posts in this topic

*****UPDATE*******

Excellent Info Here: http://social.technet.microsoft.com/wiki/contents/articles/3887.aspx

Event Logs were useless found info: On XP machines the log files are located in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs connectcomputer.log

Service issue for me with Net.Tcp Port Sharing, it will not start, generates an error. Reg points to correct location, can not find info, will need help with this.

Other good information: http://social.technet.microsoft.com/wiki/contents/articles/3941.aspx and great info regarding file permissions and fat 32 to ntfs problems.

New WHS 2011 build. Install went smooth. IP address for Server is static, assigned from router with DHCP. Upnp is on in the router. I installed connector no problem on windows 7 64 machine. On two XP Pro SP3 and one XP Media Center 2005 all 32 bit, connector fails at about 95% every time. The computers will show up in WHS, but connector software does not install correctly. I can RDP into WHS just fine. If I ping "server name" it responds, if I ping "IP number" it responds. I can access shared folders fine.

What I have tried.

Changing DNS (from assigned 8.8.8.8 to obtain automatically)

Opening required ports in router (win 7 machine worked with just Upnp)

Turning Firewall off in router and clients

Turning Ip6 off on WHS

Assigning Static IP address to adapter in WHS (changing it as opposed to having router assign it).

I have checked services IIS on WHS, it is on.

I have Workgroup assigned correctly.

I made WHS the master browser.

....and who knows what else I've tried and forgot about already.

Please HELP.....I built this for the client backups and now I seem to just have a file server like the machine it's going to replace.

PS, everything is up to date....clients, router, WHS, bios, etc.....

Yes, time zone is correct, time is set properly on all machines.

I also uninstalled and re-installed .net and tried the find my serevr tool. I have googled for 12 hours and really need help.

Thanks for any and all input.

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

Do you have .NET Framework 4 installed on the XP machine?

Share this post


Link to post
Share on other sites

Yes .NET 4 and all updates have been installed...and removed and installed and updated.

Net.TCP Port Sharing Service ....I still can not get running.

Had a caution in .NET install logs about Internet Information Sharing service (IIS).

found info that Net.TCP Port Sharing Service required that.

I was able to install IIS and get it running, but Net.TCP Port Sharing still does not start properly , just hangs "starting".

Have tried another install this morning, will check logs, but think it's going to point me back to the Net.TCP service.....Thanks for help and suggestions.

Do you have .NET Framework 4 installed on the XP machine?

Share this post


Link to post
Share on other sites

*******SOLVED*******

I hope this helps someone else...If you know of a better place to post so Microsoft fixes this please repost.

It was definitely a the Net.TCP Port Sharing Service issue for me, first identified in the logs.

I was able to restart the service by replacing the SMSvcHost.exe file and the SMSvcHost.exe.config files found in C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 with the files found in C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.

I have done this on one of the XP machines. I have three more to try it on.

After Net.TCP Port Sharing Service was started I ran the connector program again. IT WORKED!!!

I will update post when it works on other machines...Looking for feedback and for others to call this to Microsoft's attention.

********Update*********

I have sucessfully connected 3 more xp pro client machines with this same fix that would not connect prior to it.

Share this post


Link to post
Share on other sites

Glad you found a solution. If you haven't already, please post your "bug" and solution on the Connect website.

Share this post


Link to post
Share on other sites

Thank you Thank you Thank you! I've tried many of the other "fixes" and yours worked. I found TCP.net was trying to start but wouldn't. My son's computer also boots faster because the service is no longer hanging.

*******SOLVED*******

I hope this helps someone else...If you know of a better place to post so Microsoft fixes this please repost.

It was definitely a the Net.TCP Port Sharing Service issue for me, first identified in the logs.

I was able to restart the service by replacing the SMSvcHost.exe file and the SMSvcHost.exe.config files found in C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 with the files found in C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.

I have done this on one of the XP machines. I have three more to try it on.

After Net.TCP Port Sharing Service was started I ran the connector program again. IT WORKED!!!

I will update post when it works on other machines...Looking for feedback and for others to call this to Microsoft's attention.

********Update*********

I have sucessfully connected 3 more xp pro client machines with this same fix that would not connect prior to it.

Share this post


Link to post
Share on other sites

For all those impacted by this, can you tell me if you had any of the following installed:

a. Acronis

b. Quickbooks

c. Forefront a/v

d. Microsoft security essentials?

Share this post


Link to post
Share on other sites

NEW SOLUTION FOR THIS ISSUE:

The Connector has encountered an unexpected error

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:

1 person likes this

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • Hi - I'm now on Lights-Out 2, but the problem persists. Today 3 client computers suddenly shut down after a Lights-Out backup, whilst they were in use (but the users were away from the keyboard so never saw the warning message). All 3 computers had missed their previous backup (scheduled during Friday night). The 3 computers were automatically backed up during the day today, Monday (their next scheduled backup was set for Monday night). At the end of the backup they shut down & the users lost work. I'm trying to create a situation where... Each evening, the client computers are put to Sleep. During the night, the server wakes up the clients in turn, runs a Lights-Out backup, then shuts down the clients. When all the backups are done, Lights-Out puts the server to Sleep. In the morning the clients are re-started, the server wakes up, and the day begins as normal (I like the idea of the clients being restarted regularly). If one of the client computers can't be woken up during the night (the user had accidentally shut it down at the end of the day, or took it home with them), I don't mind what happens next: either a 'normal' Windows server backup during the day; or nothing happens until the next scheduled night-time backup. But these unexpected daytime shutdowns are making me increasingly unpopular - is there any way to avoid them during the daytime when everyone is trying to work normally? many thanks, Simon
    • Please contact support@green-it-software.com and I can send you a copy.
    • Hi, I am looking for these drivers HpMssServiceSetup_v1.0.6 but the dowmload link is dead. Does anyone have a working link please. Thank you.
    • That guide is for installing Exchange on a Server Essentials network, not necessarily installing both services on the same server, which isn't a good idea at all to do (as SBS with Exchange 2007/2010 was a good example of how poorly both AD and Exchange run when both are on the same server), nor is it supported by Microsoft.  Exchange 2016 initially had compatibility issues when installed on Server 2016 until Microsoft's server team came up with KB3206632 and the Exchange team released December 2016's quarterly update (CU3 or 4). Your IIS Reverse proxy will only (currently) be supported on Windows Server 2012/R2, as you've no doubt discovered, the Application Request Routing version and update only support 2012/R2. I know it works for 2012 R2 because I'm running Exchange 2016 CU4 on Server 2012 R2 on my domain that also includes a Server Standard with Essentials Role installed (5 VMs:  2 Domain Controllers, Exchange 2016 CU4, Server Essentials and a Reverse Proxy server all running 2012 R2 using ARR 2.5 -- the ARR Reverse Proxy allows me to share Exchange, Essentials RWA and my QNAP on 443), but thus far, I haven't seen anything for Windows Server 2016.  ARR 3.0 might work with Server 2016, or your other alternative is to deploy another server running 2012/R2 and use ARR 2.5.
  • Popular Contributors