Re: Erorr creating OS Image with OSD

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Also make sure that IPsec and NTLMv2 aren't required to talk to the server.

-Michael Niehaus
Systems Design Engineer
mniehaus@xxxxxxxxxxxxx
This posting is provided "AS IS" with no warranties, and confers no rights.

"ANguyen" <ANguyen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D5FDA2AF-7187-48F4-87F2-496F940073CD@xxxxxxxxxxxxxxxx
> Using the winPE lab cd, boot up and try ipconfig to see if it's picking up
> an
> IP address. If it is, ping the server you are trying to upload the image
> to.
> If the server name does not resolve, ping the server by IP to see if you
> get
> a response. If the IP reponds set the image destination path to
> \\xxx.xxx.xxx.xxx\sharename rather than \\servername\sharename.
>
> Cheers
>
> "Eric" wrote:
>
>> Yes, I have.
>>
>> "ANguyen" wrote:
>>
>> > Hi Eric,
>> >
>> > Have you updated Windows PE with the network driver for the GX520?
>> >
>> > Cheers
>> >
>> >
>> > "Eric" wrote:
>> >
>> > > I am using OSD to create an image of a Dell GX520. I have the latest
>> > > drivers
>> > > for Windows XP that I downloaded from Dell and included them in my OS
>> > > Image
>> > > Creation CD. I also reviewed the CD and they are there and in the
>> > > correct
>> > > location.
>> > >
>> > > When attempting to create the image, I get the following errors:
>> > >
>> > > "An error occurred while capturing the image (error code: 1326)
>> > > Logon failure: unknown user name or bad password"
>> > >
>> > > Once I click Ok I get another slightly different message:
>> > >
>> > > "An error occurred while capturing the image (error code: 2250)
>> > > This network connection does not exist"
>> > >
>> > > Any ideas? I have very carefully typed the user and password in all
>> > > screens
>> > > when prompted during sysprep. I verified the permissions on the
>> > > network
>> > > location. I have made images before so I have a little experience
>> > > with this
>> > > but just don't know why it will not work.
>> > >
>> > > Is there a way to control WinPE so that I can see where it errors out
>> > > and/or
>> > > take control over it to help find a solution?
>> > >
>> > > Any help would be appreciated.
>> > >
>> > > Thanks.
>> > >


.



Relevant Pages

  • Re: RDP can not logon error
    ... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: Cannot connect to Server
    ... Test 1 - the clients can ping one anotehr ... gpupdate/force - reboot both client and server - ping to server from client ... Suggestion 2 - ping to server works when running safe mode with networking ...
    (microsoft.public.windows.server.sbs)
  • Re: The specified network name is nolonger available
    ... My server is named FS1. ... > ping \\fs1 and I will get a successful return. ... I still can access the drives marked ... What is the point in these permissions as they can be bypassed by mapping ...
    (microsoft.public.win2000.networking)
  • Re: RDP can not logon error
    ... ping and tracert to the dc in that remote site (where this system ... Tracert & Ping to dc on the same subnet as the server that is having ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • RE: Unable to ping client2
    ... I understand that the server box can not ping one ... client workstation after upgraded to SBS 2003 SP1. ... Reboot the SBS Server. ... On the client workstation, run "ipconfig /release" and then run ...
    (microsoft.public.windows.server.sbs)