Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
No more connections can be made to this remote computer.

Answered No more connections can be made to this remote computer.

  • Monday, January 04, 2010 3:40 PM
     
     
    Sign In to Vote
    0
    I cannot use my deployment toolkit because I cannot log into the share.

    Whenever I attempt to log into the Deployment Toolkit share, I get this error:

    * Invalid credentials: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.

    I had been getting this error with the last version of the Deployment Toolkit, and the error persisted upon upgrading to the latest version.  In the past, I was able to work around this problem because I created a local user account that I used to log into the share.  The issue appears to be with using domain accounts.  By using a local user account, I was able to bypass the domain user authentication that appears to be the problem.    However, that server was recently made into a backup domain controller (since it was sitting idle 99.99% of the time), and I can no longer use local accounts.

    Does anyone have a clue of how to fix this?
     

All Replies

  • Monday, January 04, 2010 5:53 PM
     
     
    Sign In to Vote
    0
    Did you applied the updated ztiutility.vbs?
    All info on Microsoft Deployment Toolkit Team Blog .

    This post on the-d-spot can also be helpful.


    • Marked As Answer by Tim MintnerModerator Monday, January 04, 2010 6:51 PM
    • Unmarked As Answer by Dan Ball Tuesday, January 05, 2010 1:12 PM
    •  
     
  • Tuesday, January 05, 2010 1:14 PM
     
     
    Sign In to Vote
    0
    Unfortunately, that is not the problem.  I cannot even attach to the share in the first place, so the script cannot be accessed, so any modifications to it will have no effect.  I have tried mapping the drive manually before and it gives the same error.
     
  • Tuesday, January 05, 2010 1:27 PM
     
     
    Sign In to Vote
    0
    Additional info:

    When mapping to the distribution share from the command line, I get this error:
    ------------------------------------
    System error 71 has occurred.

    No more connections can be made to this remote computer at this time because there are already as many connections as the comptuer can accept.
    ------------------------------------


    I can connect hundreds of computers to this same share from other computers, but cannot connect from the WinPE deployment client. 

     
  • Tuesday, January 05, 2010 6:02 PM
    Moderator
     
     
    Sign In to Vote
    0
    It sounds like your NIC driver isn't quite correct?  What model of computer is this?
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com
     
  • Tuesday, January 05, 2010 9:45 PM
    Moderator
     
     
    Sign In to Vote
    0

    Basic Question: Have you reached the limits on your Server License?

    Keith Garner (KeithGa.com) - Deployment Consultant - http://deployment.XtremeConsulting.com
     
  • Wednesday, January 06, 2010 12:11 PM
     
     
    Sign In to Vote
    0
    It sounds like your NIC driver isn't quite correct?  What model of computer is this?
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com

    I've tried it on several different models of the HP line.  I don't think it is the NIC driver though, as I can map drives to any server that is "not" a domain controller.
     
  • Wednesday, January 06, 2010 12:12 PM
     
     
    Sign In to Vote
    0

    Basic Question: Have you reached the limits on your Server License?

    Keith Garner (KeithGa.com) - Deployment Consultant - http://deployment.XtremeConsulting.com

    Nope, I can (and do daily) connect up to a thousand people at a time to these same servers, this issue only shows up from the WinPE deployment client.
     
  • Wednesday, January 06, 2010 12:28 PM
     
     
    Sign In to Vote
    0
    Check your share sessions and see if you don't have files in use because if of your previous attempts to access the share

    For me this is a Server or NTFS issue, this has nothing to see with winpe
    http://nicosienaert.blogspot.com/
     
  • Wednesday, January 06, 2010 4:39 PM
     
     
    Sign In to Vote
    0
    I checked and there are no open files, which makes sense because WinPE cannot authenticate to the server. 

    I will agree that it probably is a server issue, but it relates directly to WinPE because Windows XP, Vista, 7, 2003, 2003R2, 2008 "can" authenticate, but WinPE cannot.  I am surprised no-one else has encountered this yet (or at least reported it).


     
  • Wednesday, January 06, 2010 4:41 PM
    Moderator
     
     
    Sign In to Vote
    0
    You might want to get a network trace on this.  Could be a firewall rule or some security policy such as NTLM authentication settings or something like that
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com
     
  • Wednesday, January 06, 2010 7:28 PM
     
     
    Sign In to Vote
    0
    Hmmmmm, I added a 2008 R2 server in as a domain controller and I can map drives to that one.  Maybe I'll just upgrade all my domain controllers to R2 and give that a shot, it's gotta be a lot easier than figuring out this mess!  *grin*

     
  • Thursday, January 07, 2010 3:52 PM
     
     Answered
    Sign In to Vote
    1
    I had the same issue. I think it had to do with the WINS not getting recognized. I changed my Deployment share settings to point to the IP address instead of the \\ServerName\DepShare$ it points to \\192.169.140.1\Depshare$... This has worked without issue since.
     
  • Thursday, January 07, 2010 5:19 PM
     
     
    Sign In to Vote
    0
    Never thought to try the IP, that seems to work.  I don't think that is a permanent solution, but it is a good work-around!  
     
  • Friday, January 08, 2010 8:06 PM
     
     Answered
    Sign In to Vote
    0
    My solution:  Installed 2008 R2 server, made it a domain controller, installed MDT 2010 on that server, updated PXE boot to use new server.

    • Marked As Answer by Dan Ball Friday, January 08, 2010 8:06 PM
    •  
     
  • Friday, November 02, 2012 10:09 AM
     
     
    Sign In to Vote
    0

    I also had exactly the same message. After some digging around I noticed the System Clock was 5 minutes out!!!

    N:\>w32tm /query /source
    Free-running System Clock

    N:\>w32tm /config /manualpeerlist:time-a.nist.gov,time.nist.gov
    The command completed successfully.

    N:\>net stop w32time
    The Windows Time service is stopping.
    The Windows Time service was stopped successfully.

    N:\>net start w32time
    The Windows Time service is starting.
    The Windows Time service was started successfully.

    N:\>w32tm /query /source
    Local CMOS Clock

    N:\>w32tm /query /source
    time-a.nist.gov,time.nist.gov