"Invalid Credentials: The Network Path was not found" MDT 2010


I get an error while attempting to conect to MDT 2010 through my boot wim and wds.  
the error i get is Invalid Credentials: Network path cannot be found.

In looking at the issue I hit cancel and get to a command prompt. I attempt to map the drive using net use and am unable to find the resource with an error code of 53.  I then was able to map the drive using the ip address of the server.  I then connected the drive using the fully qualified name.  and was able to connect.  I then went to the mdt share and edited the bootstrap.ini to relfect the fully qualified name and this did not work.  I tried the IP address and this did not work as well.  I verified my network drivers and I am still getting the same error.  I verified all the permissions and rebooted the server as well.  We have not had a patch on the server since Monday last week and the system worked all last week.  

your help is much appreciated
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Micko210Author Commented:
I figured it out....

in using WDS to push the wim I had the path wrong. i have share unde another folder and i needed to set that properly.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
So it's solved? Then please close the question. TY
I had the same problem where the Deployment Wizard would ask me to enter the path of the Deployment Share and then it would not accept my credentials. I added network credentials in the Bootstrap.ini file like this below the line that has the UNC path for the Deployment Share.

I updated the Deployment Share after this step since I edited the Bootstrap.ini file.

Then, I updated the boot images in Windows Deployment Services by selecting the LiteTouchPE_x64.wim and LiteTouchPE_x86.wim files using the full UNC netowrk path like this:
\\DEPLOYMENTSERVER\MDT Deployment Share$\Boot\LiteTouchPE_x64.wim

Now the Deployment Wizard does not ask for credentials and it goes rigt to my task sequences and connects to the Deployment Share no problem!
Best of luck, Todd
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.