Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2010 and Invalid cerdential issue

Unanswered MDT 2010 and Invalid cerdential issue

  • Thursday, September 27, 2012 10:16 AM
     
     
    Sign In to Vote
    0

    Hi Forum

    I have an issue, I was testing MDT 2010 earlier and have a deployment share on a local PC c:\

    I then run the MDT CD on the laptop and get to the Microsoft solution accelerator with a prompt for credentials.

    I put in our domain admin credentials and i get an error saying * Invalid credentials: The network path was not found.

    I click F8 to bring up the CMD Prompt and type:
    net use \\computername1\deploymentshare$ /user:mydomain\administrator
    I get:
    System error 53 has occurred.
    The Network Path was not found.

    I then type:
    net use \\ipAddressofComputer\deploymentshare$ /user:mydomain\administrator
    I get prompted for password, so therefore that works.

    Also another issue is I cannot change the UNC path to use the ip address, so im stuck for now. I have checked the DNS settings and the sharing settings and everything looks normal and correct.

    What issue am I facing here? and how can I resolve this?

    Thanks in advance.
    NN


     

All Replies

  • Thursday, September 27, 2012 11:53 AM
     
     
    Sign In to Vote
    0

    Obviously, the name resolution is not working correctly on your network.

    Some hints:

    • Check for typos in computername, password, domain name
    • try to use fully qualified domain name in your UNC path, ie. \\computer.domain.local\DeploymentShare$
    • If it's possible, use WINS on your network

     
  • Thursday, September 27, 2012 2:42 PM
     
     
    Sign In to Vote
    0

    Obviously, the name resolution is not working correctly on your network.

    Some hints:

    • Check for typos in computername, password, domain name
    • try to use fully qualified domain name in your UNC path, ie. \\computer.domain.local\DeploymentShare$
    • If it's possible, use WINS on your network


    Its definately a DNS issue, the above did not work though. I checked in the DNS, I have removed ipv6 addressing. I cannot ipconfig /flushdns on the laptop once in MDT2010 which makes this difficult. Is there another way?

     
  • Friday, September 28, 2012 7:40 AM
     
     
    Sign In to Vote
    0

    So let's recap...

    Your DistributionShare$ is on your laptop

    Is your laptop joined to domain?

    If it is it's IP should be registered in DNS.

    You may check it this way.

    Open CMD window and type

    nslookup MyLaptopName

    You should get back your IP address registered in DNS. Is it correct?

    If your address is not registered in DNS, you should find why it is not. Are you a DNS admin too in the place where you are trying to set up deployment network?

     
  • Friday, September 28, 2012 8:46 AM
     
     
    Sign In to Vote
    0

    Hi Les52

    nslookup brings back the correct details, there is nothing incorrect as far as I can see in the DNS.

    going back...
    When i ran MDT2010 i first noticed this issue, I sent a PING and recieved an ipv6 address, i went to my PC and removed ipv6 addressing and checked DNS to be correct. I was happy everything was as should be. I then ran MDT again on the laptop and tested.. same error, so pressed F8 and PINGed my PC, ipv4 addressing came back, that was better. I thought to ipconfig /flushdns but this failed. I tried logging into the laptop to flush the dns and start back up to MDT, same error's.

    MDT will not allow me to use the ip address but would prefer to use name addressing anyway and have this sorted.

    What else could I check?
    Thanks
    NN

     
  • Friday, September 28, 2012 8:51 AM
     
     
    Sign In to Vote
    0

    Right click on the Deployment share and Properties. On the General Page - Is the Network (UNC) path/share and the Local Path correct?

    If yes, then proceed to the Rules tab and click on Edit BootStrap.ini - What is the DeployRoot Property there? Is that correct?

    If you make any change, please make sure you update the deployment share. If this is a PXE boot, then you have to update the new boot wim in WDS. If Media boot, then update the new boot wim there.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Friday, September 28, 2012 9:24 AM
     
     
    Sign In to Vote
    0

    Hi Vik

    That is all correct. I have just booted in to the laptop im deploying to and added to the domain and changed hostname, i then boot into MDT and check hostname i get: minint-di9***, i then do a nslookup under this and obviously get nothing, i ipconfig and i see i have a vaild ip address and i can ping my deploymentshare computer.

    Whats going on?

    ======

    Ok, I have decided to wipe the deploymentshare and start everything from scratch and see if any changes.

    • Edited by Naked Nuts Friday, September 28, 2012 10:51 AM update...
    •  
     
  • Friday, September 28, 2012 11:19 AM
     
     
    Sign In to Vote
    0

    ======

    Ok, I have decided to wipe the deploymentshare and start everything from scratch and see if any changes.

    I got no change. This really makes no sense, I used a new deployment share and name and burned everything to a new disc.
    I also logged into the Laptop as Local admin and in the search box typed:
    \\mycomputername\deploymentshare$

    And it connected to my domain PC, this cannot be DNS still, this is something within MDT, I have managed to get MDT working once and I have built a very basic deployment share and have more trouble now.

    • Edited by Naked Nuts Friday, September 28, 2012 11:28 AM
    •  
     
  • Friday, September 28, 2012 11:37 AM
     
     
    Sign In to Vote
    0

    Your name resolution is not right, that's a different issue.

    As for MDT and logging in automatically, try this.

    Bootstrap.ini:

    [Settings]
    Priority=Default

    [Default]
    DeployRoot=\\10.0.0.22\DeploymentShare$
    SkipBDDWelcome=Yes

    UserID=10.0.0.22\Andrew
    UserPassword=YourPassword

    CustomSettings.ini:

    SkipBDDWelcome=Yes

    Obviously confirm your correct ip address, deploymentshare name and credentials.

    After that, right-click the deployment share in the deployment workbench to recreate the boot disk then try booting again.

    Andrew.

    Blog: http://scriptimus.wordpress.com

     
  • Friday, September 28, 2012 11:48 AM
     
     
    Sign In to Vote
    0

    Thanks Andrew, will try this.

    I dont see how our DNS can be incorrect as it works everywhere else. How can i use the FQDN or the hostname with the deploymentshare on the PC im connecting to from the same laptop but when in MDT nothing works?

     
  • Friday, September 28, 2012 12:10 PM
     
     
    Sign In to Vote
    0

    I really appreciate the help but nothing is working...

    I tried Andrews way twice with 2 different sets of admin credentials, mine and the domain admins.

    I got both times from the Wizard Error:

    A connection to the deployment share
    (\\192.168.0.111\deploymentshare$) could not be made.
    Connection OK. Possible cause: invalid credentials.

    So I click F8 to bring up CMD prompt and type: net use \\mycomputername\deploymentshare$
    I get error:

    System Error 53 has occurred.

    The Network Path was not found.

     
  • Friday, September 28, 2012 12:15 PM
     
     
    Sign In to Vote
    0

    Can you go into the deployment share folder from command prompt and run the following command?

    cacls .

    Eg:-  e:\DeploymentShare> cacls .  <enter>

    Can you paste the output here? Also, make sure that after cacls there is a period(.)

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Friday, September 28, 2012 12:17 PM
     
     
    Sign In to Vote
    0
    C:\DeploymentShare$ mydomain\MyNameisHere:(OI)(CI)F
                        BUILTIN\Administrators:(OI)(CI)F
                        BUILTIN\Administrators:F
                        BUILTIN\Administrators:(OI)(CI)(IO)F
                        NT AUTHORITY\SYSTEM:F
                        NT AUTHORITY\SYSTEM:(OI)(CI)(IO)F
                        Everyone:(OI)(CI)F
     
  • Friday, September 28, 2012 12:25 PM
     
     
    Sign In to Vote
    0

    Permissions look ok, Did you recreate the WIM after Andrew's post?

    Turn off firewall, antivirus on the source and destination and try...

    Lastly, if you can run a network trace (Netmon 3.4) or similar and reproduce the issue, and upload it on public storage - I can have a look.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

     
  • Friday, September 28, 2012 1:42 PM
     
     
    Sign In to Vote
    0

    Its a strange one as I have had this working on the same laptop about a day before, something changed along the line and I cannot figure out what.

    Thanks for the support on this, if I manage to find a fix for this i'll post back.
    NN

     
  • Friday, September 28, 2012 6:33 PM
     
     
    Sign In to Vote
    0

    NN this may sound obvious but. . .

    The laptop that has the new deployment share will need its own media creating. You appear to be using CD so. . 

    Did you create a new CD on the laptop where the deployment share is?

    Or are you trying to use the same media as your other deployment?

    Blog: http://scriptimus.wordpress.com