>

SBS 2008 / 2011 connect computer program wizard doesn’t work

When you try to connect a client computer to your Small Business Server 2008 or 2011 network via the http://connect you get “Internet Explorer cannot display the webpage” or the wizard stops with error: “An error occurred during the download of Connect Computer. Please go to http://connect and try again.”

Both problems had to do with DNS issues. In my case I had configured the client with static TCP/IP settings (IP address and DNS) instead of using the dhcp settings. To solve the problem I had to enter the sbs domain name in my network settings properties on the DNS tab, to append the DNS suffix like below.

After adding this, the connect computer program worked fine.

Posted in Blog, SBS 2008, SBS 2011 by ronnypot at February 22nd, 2011.
Tags: ,

28 Responses to “SBS 2008 / 2011 connect computer program wizard doesn’t work”

  1. Susan says:

    By any chance is the dhcp on your router? I’ve seen connect not work properly if dhcp is on the router not on the server. If dhcp/dns is set on the server then it should work.

  2. ronnypot says:

    Hi Susan,
    Thanks for your reply, but as written there was no dhcp at all, only manual configuration. Dns was pointing to the SBS server but it still didn’t work. The solution was to add the append these dns suffixes, after adding this it works fine!

  3. Salamat says:

    Thank you! iT WORKS!!! :))

  4. Letoine says:

    Hi Ronnypot !

    Thank you a lot !!! No no no not just that : A LOT !
    It worked on 2K8-R2 to SBS2K11.

    Got defined the DNS suffixe.

    Another (and last) thank to you for the share 😉

    Toine

  5. Richard says:

    excellent! worked first time on SBS 2011 new install on old SBS 2003 network, moving client from old to new server;

  6. Zu@rT says:

    I just find your post thanks for the relief and thanks GooglE too !!!

  7. dave gilham says:

    That solved my initial problem – thx

  8. Joe V says:

    Thanks for posting this – it solved my issue..!

  9. James says:

    This worked to resolve the connect URL, however when the computer went to join the domain, it failed on the Connecting to Network step, with “The specified domain either does not exist or could not be contacted” I put the system back on DCHP from the server, removed this fix and got the same error.

    • ronnypot says:

      And you are sure the dns is pointing to the SBS server? Ofcourse it is best practice to just use DHCP, or is there any specific reason to do not use DHCP if it is to give the client a static ip address I would advice to do a reservation via the DHCP server.

  10. Peter says:

    Thanks so much for this info! I needed to connect a branch office workstation to an SBS 2011 network across a site-to-site VPN and the DNS settings did the trick.

    In order to get the whole thing started I also needed to add an entry to the hosts file for “connect” so it could find the SBS server by that name.

  11. albert says:

    Thanks For this tip , i hadd the problem like Peter adding a computer accross a VPn , even though it had DNS configured to be the SBS server for some reason it would not run the connect program until I followed your instructions….

    Cheers…

  12. Johnathan Bravo says:

    Thanks so much. This tip is awesome. Worked a charm first time.

  13. TeeC says:

    I experienced a similar problem on SBS2011 Standard. The ConnectComputer. DUring the Verify Computer Components process on a Win7 desktop, the Connect Computer process stops working. DHCP is enabled on the server and the DNS is working.
    I tried adding the DNS server and DNS suffix manually but it didn’t work; still looking for a solution.

    • ronnypot says:

      sorry for the delay I was on a vacation. Did you solve the problem already or still not working? If not working is the client you are trying to add on the same location as the server or remote via vpn? Second is this a Windows 7 machine and do you have the problem with only one computer or with more? Last where during the process does the wizard crash?

  14. Lac says:

    Thanks for posting this! It solved my first issue.

    Now I am coming up against the folllowing when trying to join win7 client to SBS 2011-

    Problem Event Name: CLR20r3
    Problem Signature 01: connectcomputer.exe
    Problem Signature 02: 6.1.7900.0
    Problem Signature 03: 4cd854c3
    Problem Signature 04: mscorlib
    Problem Signature 05: 4.0.0.0
    Problem Signature 06: 4ee9d7cd
    Problem Signature 07: 41f7
    Problem Signature 08: 5df
    Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 2057
    Additional Information 1: 116d
    Additional Information 2: 116dfc12b64de2e5043d30371f4b25c5
    Additional Information 3: db17
    Additional Information 4: db170dc01e4d0d53cb3ae8937457a16f

    I’ve tried connecting the client computer through the web and copying the program to portable media with the same error occuring.

    Any ideas on how to resolve this? Any help would be really appreciated

    • ronnypot says:

      Never seen this problem, and so on the first also no idea what this could cause. I would suggest posting the question on the Microsoft Technet SBS support forum there are a lot of IT professionals helping out other people so maybe someone that knows this problem and have a solution.

      If you found a solution please post the resolution so others can use it in the future.

  15. Sahalu says:

    Thanks for being such a prolific contributor ronnypot. I had an issue but as soon as I disabled DHCP on the router, the sever took over and assigned me an IP address and I was able to successfully run http://connect. I also had to install .Net Framework 4.0. Your tip is handy though, just in case, I am filing it away in my tools.

  16. pete says:

    A more elegant/easier solution is the to flush the dns cache. Just go to a command prompt and type in ipconfig/flushdns and run it a couple times. Works for me all of the time. No reboot required. Have fun!

    • ronnypot says:

      Thanks for the additional option, this might work when you get the DHCP from the SBS server. Although it is not normal to run ipconfig /flushdns a couple of times.

      When you do not use DHCP from your SBS server you have to configure the setting as described in this post.

  17. Marcel says:

    Hello Ronny and all the others 🙂
    I followed all the steps as mentioned but with dhcp and static setting http://connect will not run.
    I tried to flush dns, several computers (all win7 pro) etc.
    When trying at the server eveything is working.
    DHCP scope option 6 = DNS server 192.168.1.5
    ROUTER scope option 3 = Gateway 192.168.1.1
    WS is saying DHCP IPv4 192.l168.1.12 / DNS 192.168.1.5 / Gateway 192.168.1.1
    Help….

  18. Marcel says:

    Owk guys and girls…. I think i found the answer which helped to solve my problem. 🙂

    Only when you are aware of dhcp, dns etc. and already have setup all correctly. (DHCP options and scope settings etc.)

    When still having trouble (DNS) and everything (internet and http://connect) is working at the server but not at the client try the following regedit from microsoft: http://support.microsoft.com/kb/968372

    Good luck!

    • ronnypot says:

      Thanks for the additional information, hope this will help others.

    • googlinit says:

      Thank you all for your valuable input.

      Marcel’s reply resolved my issue: what I did was simply clear the DNS server cache and restart the service. Problem was immediately solved!

  19. Fran says:

    Ronny, thank you very much for sharing…
    You described exactly my situation, and solution.

  20. Vlt says:

    Had the same issue here. This solved the problem, tks

  21. James says:

    I had a similar problem but just couldnt get it to work and solved it by deactivating ip 6 completely and everything worked fine. Since SbS 2008 only want to run on ip 4, and for some wierd reason having both ip 4 and 6 activated at the same time it tried to run on 6 which wont allow the client to install or you will recive a network failure during installation.
    Hope this helps

Leave a Reply to albert

Sharing Buttons by Linksku