Latitude 2120 not recognizing WDS

[KnuckleHead37]

My issue is pretty simply, but very frustrating.

I have a WDS set up for my district, it works fine for all machines except my dell latitude 2120s. The issue is when you boot the netbook to the WDS it cannot contact the server to upload the image. The issue also happens if you try to send an image to the machine, it says there is no network driver. Ive tried injecting WDS with the network driver from dells website, as well as the drivers package disc from dell. Ive even tried a few other drivers from different places without any luck.

Booting to WDS has no issues. While booted, i can pull up the cmd prompt but cannot ping anything on my network.

This issue is fairly common, but usually fixed with a driver on the network. This case seems to be more specific to the 2120s.

Any thoughts?

 

[HelpSaint]

I had the same problem, i just resolved it

So i too was running into this problem and it was ticking me off. I was able to track down a drive cab file from Dell that had all the device drivers for the 2120. I was then able to get that here: en.community.dell.com/techcenter/enterprise-client/w/wiki/2168.latitude-2120-windows-7-driver-cab.aspx I extracted the cab and then found the network drivers and used those INF files to inject into my WDS images and they now work.

 

[KnuckleHead37]

Wow its been a while, but thanks for posting.

Ill have to try this. We tried multiple network drivers and still can't upload an image, but we can now deploy and image to them.

I had to save the image to the machine and grab the image off the hard drive myself and put it into the wds . This way worked but is a pain in the ass and takes a while longer to do.

 

[Parman]

Does your machine have IP address now through DHCP?

 

[KnuckleHead37]

When trying to image the computer, yes. When trying to upload an image from it, I don't know. The last network driver I added to the ads pool allowed me to image the machines, plus they can use 64bit so we don't need a special image


In short, I can just throw any of my images on them and it works.

If I need to make an image particularly for the machine I will definitely try the above suggestion that is said to work.

 

[Parman]

Link didnt take me anywhere so I couldnt tell you.

Anyways have tried mapping a drive to the share and then saving the image to the mounted drive when you're creating the image?

 

[KnuckleHead37]

Yea. I can't upload it through the network period.
It doesn't matter too much anymore. We mainly did that when he had to have a 32bit image for certain applications. We filled those few old ones out and imaged them with the 64 bit image perfectly fine.

So if I need to actually make an image on those machines for any reason, ill give this a go.

More or less, I fixed the issue an indirect way, which in return ended up making things easier since I don't have to make an image for that specific machine

 

[Parman]

Last question through WDS what kind of image were you using to boot the machines?

were you using a capture image?

 

[KnuckleHead37]

if I was trying to upload the image yes. If I'm deploying to them than I use the boot image

 

[Parman]

crazy, Well if you ever do after you capture an image again and it doesn't work post back on here and we can try to figure it out for you.

Here is a nice link to creating the capture image process.

Creating a Capture Image in WDS (en-US) - TechNet Articles - United States (English) - TechNet Wiki

 

[KnuckleHead37]

I know how to do that. The only issue is with these particular machines not working with the server properly.

Btw they can run 32 and 64bit os, and both the 32 and 64bit capture images failed to connect to the network