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

    • Like I said, you won't get the combined (aggregate) bandwidth to a single destination.   Torrenting makes multiple outgoing and can receive multiple incoming connections to and from multiple seeders and leechers (behaving more like the load-balanced scenario) in the best-case scenario, so it's one of the few applications that scale fairly well with WAN load-balancing, and if you're just downloading data, the torrent application can reassemble the whole torrent from the randomly received chunks from each seeder.  Torrent was almost designed to benefit from WAN load-balancing because of the way the P2P network was conceived. ...but that wouldn't work for streaming media or online gaming or VoIP where there's no mechanism to deal with out-of-order packets being sent and received, or the fact that it's still asymmetrically routed -- in that instance, you're still limited to the bandwidth of a single connection, you can just make more of them at a time on different paths.   802.3ad or LACP (Dynamic Link Aggregation) requires switching and routing hardware that's also LACP-compliant in order for it to work, but in that case, would be more like the aforementioned ISP IMUX connection than WAN load-balancing.   Your SpeedTest results are probably from burstable traffic over one connection, because a single SpeedTest run will only use one connection during the course of that test run, which is why it only shows a single public IP address. Sustained bandwidth testing with something like iPerf will show a more accurate picture.   Speedify would pretty much have to be tunneling all traffic as the "first hop" and reassembling traffic before going back out to the public Internet so that their VPN endpoint becomes your new public IP address out on the Internet; in essence becoming an ISP over an ISP -- if that's what it's actually doing.  While that may solve one issue, it would probably cause a drastic increase in latency to do so, and I doubt it would support streaming media very well.
    • Hi, Thanks for the reply. I understand what you mean but then that's like having 2 DC's having DHCP to issue IP in case one goes down, so both DHCP scopes would have to issue same IP address to same client or they would run out of addresses. But anyway thanks for clarifying, I was getting really frustrated about not being able to solve this because I was understanding that the clients would not leave the network when the DC is down and authentication takes place at RODC. Thanks a lot.
    • Well your right and wrong at the same time, i tested the idea using a tp-link loadbalancer and while kt didnt work on websites, for torrents/netflex it worked perefctly simple messirment's of speeds on speedtest.net got me the combined speeds as well and thats without using the 802.3ad protocol which from what i been reading makes it works perfectly long story short, even if i am not able to use the "full pipe" in all applications, it make hell of a diffrance from the plain single connection   note: i think that adding a vpn layer will even solve the multipath problem, thats what speedify and others are doing to get the combined speed
    • Yeah, mine stopped working also, but this time the communicator would allow connection to the server.
      But the automated backups were not occurring. I had to re-setup the folders associated with the computer "Customize Backup For This Computer" and then the automated backups worked again. Apparently there is an option for an anniversary clean install. Then install the connector.
      I think that would be the best option. But definitely a pain in the butt. Let us know how it goes.
      Shane
      Sydney, Australia      
    • Depends on what your storage requirements are going to be.   I personally favor RAID-10 (mirrored stripe) arrays because of the lack of a need for parity, but it's not particularly storage efficient, and with your current setup, you'd have only 4TBs (3.63TiBs) of storage space available (half of an 8TB stripe due to mirroring), in which a minimum 160GBs of that 4TBs is used for the C: drive if you partition the volume during installation. WIth 4 disks, you could do RAID-5, which would give you 6TBs (5.4TiBs) of storage space (because 2TBs is used for RAID stripe parity), but then there's the parity performance penalty and the higher risk of an unrecoverable read error (URE) killing your array and losing your data if you're not using enterprise drives.   ...or you could try Storage Spaces, I guess.
  • Popular Contributors