Ultra 20 workstation NIC driver install

hi friends,
I have brand new Sun Ultra 20 WS installed.
It was preinstalled with Solaris 10 6/06 system,
in ifconfig -a command only loop back intervace is showing.
and
*/etc/path_to_install* also not able to find the interface name.
my questions are:
1. Is there any command to get only interface name.
2. Do i have to install driver for my NIC if so how.
I also nead the URL path of the driver to download.
Please help me ASAP.......

Never mind. I think the drivers for this workstation can be found in this ISO file download available on SUN's web site.
http://www.sun.com/desktop/workstation/ultra20/downloads.html
Hope it helps all who may or may not be installing Windows on this workstation.
- SG

Similar Messages

How to install NIC driver

I'm very new to Solaris and I need to install RealTek 8169 driver. How do I unzip and install? Any help would be greatly appreciated.

Where did you get the driver? This page perhaps?
http://homepage2.nifty.com/mrym3/taiyodo/eng/
If so, here are the instructions for compiling and installing it:
1. Introduction
This is the Realtek RTL8169/8110 giga bit ethernt NIC driver for Solaris.
It is distributed under the BSD license.
2. Specification of the driver
File name of the driver: /kernel/drv/gani
Special file name: /dev/ganiN (Where N is a unit number, typcally 0 for first
card)
For example
% ifconfig gani0
RTL8169/8110 chipset dosn't support 1Gbpis half duplex mode.
Currently gani driver isn't stable on sparc platforms.
Tested OS version
Solaris10 x86 3/05 (Athlon 2800+ w/ VIA K8T800 chipset)
Solaris10 x86 3/05 (Athlon 3000+ w/ nVIDIA nForce4 CH8-04 Ultra chipset)
Tested cards
RTL8169s -- Planex Communications GN-1200TC
RTL8169s -- Corega CG-LAPCIGT
3. Preparing for installation
(1) Install your PCI card and boot Solaris.
(2) Copy source and binary files.
# gunzip -cd gani-x.x.x.tar.gz | tar xf -
(3) Add hostname for the NIC card into /etc/hosts file
(4) Make links to correct binary directory and Makefile according to your
configuration. i386 and gcc are default.
% cd /.../gani-x.x.x
% rm obj Makefile
% ln -s Makefile.${KARCH}_${COMPILER} Makefile
% ln -s ${KARCH} obj
where ${KARCH} is the result of `isainfo -n`, and ${COMPILER} is
"gcc" or "suncc" which you want to use to make the driver.
(5) Making binaries (only for sparc platform)
Gani driver is ready for 64bit and 32bit solaris8 10/00 sparc or
later. (But currently it is unstable on sparc platforms.)
This distribution does not include sparc binaries. To make the binaries,
you need Sun C compiler or gcc version 3, and do the following operations.
% /usr/ccs/bin/make
4. Testing
Testing before installation is strongly recommended.
# cd /.../gani-x.x.x
# /usr/ccs/bin/make install
# ./adddrv.sh
# /usr/ccs/bin/make uninstall (for solaris7, don't remove the file )
# modload obj/gani
# devfsadm -i gani (for solaris7, use drvconfig and reboot with -r )
# ifconfig ganiN plumb ( where N is an instance number, typcally 0 for first card)
# ifconfig -a ( you will see an entry for ganiN)
# ifconfig ganiN YOUR-HOST-NAME
# ifconfig ganiN ( ensure IP address is correct)
# ifconfig ganiN up ( and then you can test with ping, telnet, ftp ...)
5. Installation
After you ensure that the gani driver is fully functional, install it.
(1) install the gani driver into the kernel directory
# cd /.../gani-x.x.x
# /usr/ccs/bin/make install
If you do not test the gani driver yet, execute the following commands:
# ./adddrv.sh
# devfsadm -i gani (for solaris7, use drvconfig and reboot with -r)
(2) Configure the network interface. Create and/or modify the following file:
/etc/hostname.ganiN
(3) Reboot the system.
# init 6

App-V 5 SP2 install issue with Intel NIC Driver 11.16.96.0

When deploying App-V 5 SP2 using SCCM 2007 it will install with no problem on the machine. However, when the user reboots after the install the machine will blue screen. The user then reboots again and machine comes up to the desktop. However,
the App-V service is not running and is still set to automatic.
Looking at the Blue Screen dmp file the common theme looks to be a conflict with an Intel NIC driver version 11.16.96.0. Machines running an older version of the driver do not experience the issue with the blue screen after reboot and the App-V service
starts with no issues.
Has anyone seen this issue before?

Version 19 appears to be the latest: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18713&lang=eng&ProdId=3025
Have you tested with this version instead?
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V

Installing a NIC driver and using it on startup

i just went through the process of installing a NIC driver but in order to use the nic i have to do every time computer is restarted
#insmod usr.o
how do i fix this so that the NIC is recognized as soon as the computer is started? thanks in advance...

thanks for the response.
depmod -ae generates bunch of lines in the form
depmod: softnet_data
depmod: printk
etc....
modprobe usr did not return any messages. i made sure that usr was loaded with lsmod and than added usr in rc.conf in before network. however when i restarted the computer i had to load the module again. i checked first with lsmod and it wasn't loaded. any ideas?

Ultra 40 fx3500 nvidia driver problem with XP

Hello,
I have a Sun Ultra 40 Workstation with an fx3500 graphic-card. With Solaris, Mandriva and 64Bit-Windows
the card works without problems. But with XP 32-Bit only the old 9x drivers from Nvidia work. If I try to
install a driver-release above 100 (today I tried 191.00, but I also have tried many other releases) the driver
installs fine. But after rebooting the workstation powercycles short before the Windows-Login-Screen
appears and Windows boots in "Safe-Mode". Then I can install the old 9x drivers and XP works again.
I tried a tool which wipes out the old Nvidia-driver first, bevor installing the new one, but no success.
Why is it not possible to install new Nvidia-drivers?
After the second boot when the driver has failed to load, the following messages appears on the screen
after the Bios has finished:
"Nvidia Rom Bios" "Detecting Arrays"
I could not read the whole text, because the message appears only a very short time, so I could not
read the message exactly. But the message only appears after the problem with the graphics card driver.
I have not configured disk-arrays. I'm not shure, but is it possible that there is something wrong with
the Nvidia-fx3500, the Nvidia-mainboard-Chipset and the Nvidia-graphics-driver above the 100. release.
Can you please help me?
Best Regards
Ralf

First of all, thank you guys for your replies, and sorry if I answer you late; but I was tring to apply some of your suggestions.
pharao:
My old card was "the stupid" (Hercules 3D Prophet 4000XT with Kyro 4000XT chipset)
Hotoro:
What do you mean by reload Windows XP? Un/Re-Install it?! It is not a good solution for me, at least, right now. I have huge data, my settings and a lot of application installed that needs days to restore or reconfigure, and I do not think that I have that much time.
daveg4otu (Dave):
Thank you for your help. I already removed old card drivers and registry entries, and now I also removed the new ones using "Driver Cleaner" as you suggest, but the same was the result
Raven236:
No, my old card was not ATI. OK, I will try this new driver (56.72), but I can not keep downloading all drivers without result, can I?
coollg:
I do not think so, because the card is working fine on the same PC on Windows 98SE. So, it is not Mainboard, AGP or compatibility problem, as I think. In other hand, you are right, I am not expecting to get the maximum performance from that card, I am, now, looking for the minimum.
Did I have to do someting else?!!!
Thanks again.

Setting up boot WIM... but having trouble setting up the correct NIC driver

I'm trying to setup a network boot with Windows Deployment Services. Pretty straightforward (http://technet.microsoft.com/en-us/library/cc766320.aspx). Problem though is the OOTB Vista & Win2k8 boot.wim file don't include the necessary driver for the NIC card (Intel 82567LM Gigabit NIC). So I'm following these steps outlined here in the MSFT KB (http://support.microsoft.com/kb/923834) but seems I'm not loading the correct driver. I looked in my w500 Vista x64 install that has a working NIC to get the working NIC INF file, but that didn't work. Anyone successfully done this? I'm sure some of the bigger organizations have... just having trouble creating a boot.wim (or modifying the one I've got) to add the correct NIC driver to continue with a PXE boot.
AC
============
ThinkPad w520 | Intel i7 2.5Ghz | 2x 512GB Crucial SSD | 16GB | NVIDIA GeForce Quadro 2000M 2GB | 6.9 Windows Exp Index
Ultrabay DVD + modular Ultrabay 256GB Crucial SSD SATA
Win7 Ultimate x64 | Windows Server 2008 R2 | Win8 Release Preview
ThinkPad x200s | Core2 Duo 1.86 | 256GB Crucial SSD | 4GB | Intel Mobile Chipset Video | 3.4 Windows Exp. Index
Win7 Ultimate x64 | Windows Server 2008 R2

Thanks... I got that far as the boot loader is x86... but I'm trying to figure out which specific INF rather than load all of them as its a manual process.
AC
============
ThinkPad w520 | Intel i7 2.5Ghz | 2x 512GB Crucial SSD | 16GB | NVIDIA GeForce Quadro 2000M 2GB | 6.9 Windows Exp Index
Ultrabay DVD + modular Ultrabay 256GB Crucial SSD SATA
Win7 Ultimate x64 | Windows Server 2008 R2 | Win8 Release Preview
ThinkPad x200s | Core2 Duo 1.86 | 256GB Crucial SSD | 4GB | Intel Mobile Chipset Video | 3.4 Windows Exp. Index
Win7 Ultimate x64 | Windows Server 2008 R2

A connection to the deployment share could not be made - Networking device did not have a driver installed

I have a couple of HP 8200 desktops that I think might have bad nics. When I PXE boot them and start my LiteTouch, I get a Wizard error that says
A connection to the deployment share (\\mydpshare\share) could not be made. The following networking device did not have a driver installed
PCI\VEN_8086&DEV_1502&SUBSYS_1496103C&REV_04
I have that driver in MDT and it works on other HP 8200s. Looking into the Wpeinit.log, it looks like the driver loads but maybe the nic is bad:
Installing device root\kdnic X:\WINDOWS\INF\kdnic.inf succeeded
Installing device pci\ven_8086&dev_1502 X:\WINDOWS\INF\net1ic64.inf succeeded
Spent 16903ms installing network drivers
QueryAdapterStatus: no adapters found
Spent 0ms confirming network initialization; status 0x80004005
WaitForNetworkToInitialize failed; ignoring error
Has anyone seen this before?
Orange County District Attorney

Hi,
According to your description, it should be Intel NIC driver problem. I have checked HP official website, there is new NIC driver released, please access to the link below to download the NIC driver for test:
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=5037932&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3Didx%253D2%257CswItem%253Dvc_111651_1%257CswEnvOID%253D4060%257CitemLocale%253D%257CswLang%253D%257Cmode%253D4%257Caction%253DdriverDocument&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken
Roger Lu
TechNet Community Support

HTTP.SYS fails to load after ProLiant NIC driver update on Server 2008 R2

Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard
server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version
7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command
prompt...) DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or because
it has no enabled devices associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged
http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then
restore the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help...

Hi team,
This has been driving me crazy for a week and I can't find any reference to solving the problem in Technet or any forums...
I have a ProLiant ML350G5 server that I installed Server 2008 R2 on and migrated all my domain AD, DNS, File Services, Shares and files from SBS2003 (end of life, so let's take that out of the network) - Exchange and SharePoint were not being used so Standard
server 2008 was the choice seeing that the server hardware is 4 years old...
Everything went well, migration was successful, AD was primary and active.
Then (stupidly) I decided I'd better install all the updated drivers and management software from HP. The NIC is showing as an HP NC373i which is a Broadcom BCM5708C. I updated the FLASH in that card (HP utility) and updated the driver to the latest version
7.8.52.0 along with a bunch of other updates all handled by HP's Support Solutions Framework (msi).
After the reboot required, I noticed that the Print Spooler (set to Automatic) didn't start, neither did IIS or Web Services...
Trying to manually start them gives the error that a dependency failed. Now Print Spooler only uses HTTP (no longer a "service" but integrated into the kernel for multiple http connections on the same port and controlled using netsh http command prompt...)
DCOM and RPC. The last 2 are running, so that leaves HTTP as the culprit.
The Event Log shows that HTTP failed to load as "the services cannot be started. Either because it is disabled or because it has no enabled devices
associated with it"
From an administrator cmd prompt, net start http gives the same failure error.
netsh http show servicestate returns "The handle is invalid" - it's not seeing http at all...
OK. If you've read this far, thank you - keep going...
Here's my thinking... Updating the NIC driver has "broken" the association with HTTP.SYS - How to I get that association back?
I uninstalled anything http related, IIS, BITS, Web, Printing Services. Reboot after reboot and still no HTTP. I deleted http.sys from \windows\system32\drivers and did sfc to get windows to give me a clean one. Reboot, still doesn't load so it's not a damaged
http.sys.
I uninstalled EVERYTHING ProLiant, uninstalled the NIC, deleted the bxnd60a.sys driver so Windows would use it's own, rebooted, let it load NIC drivers, set the IP's up again, reboot - still no http.sys loading...
I've tried older versions of drivers from Broadcom, the latest version of drivers, still in the same hole...
Does anyone know how I can get HTTP.SYS to associate with the NIC? Can I do anything in the registry to achieve this? Do I have to do a System State Backup (is that the only way to preserve the AD and DNS?) scrub the server and start from scratch and then restore
the System State to get my AD and DNS back? If I do that will it bring the http.sys fault back?
I'm really at a loss - please, someone, please help...

Prom Security on Sun Ultra 10 Workstation

Just purchase a Sun Ultra 10 Workstation from my company. When I took the system home, it would boot with the follow sequence:
Boot Device: disk File and args:
SUNOS Release 5.7 Version Generic_106541_09 64-bit [UNIX(R) System V Release 4.0]
Copyright(c) 1983-1999, Sun Microsystems, Inc.
configuring network interface: hme0
Hostname: skywalker
The system is coming up. Please wait
checking ufs file systems
/dev/rdsk/c0t0d0s7: is stable
NIS domaniname is nexen.com
starting routing daemon
starting rpc services: rpcbind keyserv jpbind done.
WARNING: Time out waiting for NIS to come up.
The system locks and thats all she wrote. I have tried using STOP-A commands with no luck. It looks like the Prom Security must be enabled because the documentation specifies that these commands will not work if prom security is enabled.
Attempted to install Solaris 8 and other that this initial CD lights indicating that a cd was loaded, I cannot get beyond this.
Is there any suggestions on what to do next to get the system up and running or just to get Solaris 8 to start load, anyone????

You already posted this question, approximately 10 days ago,
[http://forums.sun.com/thread.jspa?threadID=5394403|http://forums.sun.com/thread.jspa?threadID=5394403]
and have responses to your inquiry.
Keep in mind that you'll get no output to any screen until you connect a Sun-branded keyboard-and-mouse kit. Do NOT force a PS/2 keyboard into the systemboard port else you'll damage it.
That screen must also be capable of displaying Sun's default resolution of 1152x900 at a vertical refresh of 60Hz. If the monitor cannot do that, it will commonly stay black.
Stay with your original forum thread. This "duplicate" will likely get deleted as being a double-post.

K7N2G will not load windows xp with any type of dvd/cd drive installed?

This is on my old computer, the specs are as follows
k7n2g
athlon 2600+
radeon 9700 pro
Caviar SE wd800
1gb samsung ddr333
It does not matter if it is keyed as master or slave, primary or secondary my old k7n2g will not load windows with a cd drive installed. I have tried three different drives and everything that I can think of, changed cables, channels, drives, everything. Windows just hangs. I cannot even get into safe mode. Is this an IRQ problem? The drives keeps trying to eject themselves, no matter what kind I use. This has never happened before, but there was a point before this problem where the vga wouldn't kick on (at the login screen) until I hit eject on the cd drive. This is driving me crazy and I have a girlfriend who just has to play her stupid sims and will not stop bothering me about it. PLEASE PLEASE PLEASE help me!
Thanks
Chris
PS here is my NEW workstation (I couldn't be happier to get rid of the old system)
two Opteron 250 90nm
2gb 2-3-2-6 Corsair Reg/ECC DDR 400
Tyan Thunder K8WE
1x BFG 7800GTX OC (one for now)
Audigy 4 Pro
Seagate Cheetah U160 10k 73.4 gb
Atlas V U160 18.3 gb
Lite on Dual Layer burner

Your Tyan based hardware listing on the first post has no relevance to anything, and might only serve to confuse. Please remove it and put the hardware you are trying to troubleshoot in a signature. Look in your profile>Forum Profile Information and enter that in the Signature box. That way we wont have to scroll to hunt down your hardware specs
So let us get this straight.
This system used to work fine? Yes? Then what prompted you to reload the OS?
You mentioned that didn't happen when you owned it. Are we to assume that at some point you sold or gave parts of this system to someone else? If so, what changed?
A little more history might prove useful in helping us to give you better suggestions.
Look at the PSU and give the Amps for the +3.3, +5v, & +12v lines.
***Edit, from what I see on the net, that is a dual rail PSU and the amps are as follows:
+3.3V@22A, +5V@21A, +12V1@18A, +12V2@16A
Is this correct?
Both the 3.3 and +5v seem a little low to me, but I am not entirely convinced that would be your problem. However, the fact that the 12v rails are split, can lead to other problems such as overvoltage protection circuitry getting in the way. Especially if the 16amp 12v rail is overloaded.
This is something to consider. Just because it is supposedly capable of wattage over it's rated power output doesn't mean it can handle what you're throwing at it all at once. If you have a single rail PSU that has at least 18 amps on the 12v rail to test with, we could almost definitively rule out power as the sole problem or a contributing factor.
I have never had a CD rejected, but if you could be more detailed about what you have connected to the board while attempting to load the OS, and then a detailed description of at what point the OS installation fails, and the CD is ejected, that would be helpful as well.
The fact that you've tried several drives, cables, with the same result. And also had a blackscreen event, does point to at least one problem that could point to a power issue. The CD rejection issue is foreign to me since I usually use the same type of PSU in all my builds or ones that I know work with a particular set of hardware, so I can't attribut that to a power issue.
Did you try clearing the CMOS and then initialize the default settings?
Do you have a cheap AGP card to try instead of the 9700?

Sun Ultra 40 Workstation & eSATA

I am trying to add an eSATA card into my Ultra 40 Workstation and I am getting the following message:
Expansion ROM not initialized - PCI Mass Storage Controller on Motherboard. Bus:02 Device:00 Function:00
I am able to hit F1 to continue past this message but I would like to get my settings adjusted properly so that the message goes away.
I have flashed to the latest BIOS (1.6) and that does not seem to help.
Please let me know what I can do...
2 Dual Core Opteron 280's
8 GB Memory
250 GB - 7200 RPM SATA drive
NVIDIA Quadro FX3500 Graphics Accelerator
BIOS 1.6

Okay.... since no one had a solution for me I did some experimenting on my own.... Here is what I discovered...
The eSATA card I was trying to use has a Silicon Image chipset on it... I think this is where the actual problem lies... not with the bios on my Ultra 40.
I tried a different eSATA card with a VIA chipset and it seems to be working just fine. No boot errors and once I found the drivers I needed, the card is functioning just fine in the Windows Server 2003 x64 and Windows Vista x64. I will load also be loading the machine with Vista x86 when I get a chance.
So the bottom line is that there seems to be a compatibility issue with the Silicon Image chipset on the eSATA card and either the BIOS or chipset on the Ultra 40 workstation.
Hope this helps someone else one day.

Sun Ultra 20 Workstation - working very slow

Dear sir,
I have got 20 nos of Sun Ultra 20 Workstations, with AMD opteron 64 bit processors.i have installed Windows XP 64 bit o/s where in all the systems are facing the identical problems. it is that the system are working very slow. The users are using Autocad like Designing Software and while working for quite a little time and if the users saves the current documen or the file, the system gets hanged up.
I have the System BIOS version number : 2.1.7. but i found in the site that there is a latest update is available for the same. i am downloading it now. eventhough i am trying pls provide me a better solution as Soon as possible

Go here:
http://www.sun.com/desktop/workstation/ultra20/downloads.html
and install the latest BIOS and drivers for MS Windows
Bios updated to 2.2.3

PXE Marvel NIC driver.

I have a bunch of workstations that has a Marvell Yukon gigabit NIC in
them. The BIOS for the NIC support PXE. When I enable PXE the workstation
boots from the network and I can even go in the the IMG menu with out any
issues except there is no network connectivity. When I go to the BASH
shell and do a ifconfig there is no NIC driver loaded. I beleive this is
simply a problem that there is no linux driver in the linux kernal that
PXE is loading. Is it posible to add a driver to the PXE kernal that is
being booted?

[email protected] wrote:
> Is it posible to add a driver to the PXE kernal that is being booted?
>
take a look at forge... IIRC the Marvel driver is there..
If you have already compiled drivers or have linux.2 please put them on
http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
Live BootCd and USB Disk from Mike Charles
http://forge.novell.com/modules/xfmod/project/?imagingx
eZie http://forge.novell.com/modules/xfmod/project/?ezie
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
http://www.edu-magic.net

Motherboard NIC driver OptiPlex 380 win7

Windows 7 ultra could not find a driver for a Dell Optiplex 380. I went to your driver site and entered my service tag. I also detected the device. Neither path found a NIC driver for this Dell. Please point me to the correct NIC win 7 64 bit driver. With an internet connection, I can't move forward on the rebuild.

Hi creiss001,
Thank you for writing to the Dell Community Forum.
Please download the network driver for Broadcom 57XX Gigabit Integrated Controller.
Do reply to this community thread so that if there are any more queries we will be glad to assist you.
Have a great day ahead.
Regards,
DELL- Infant R
Social Media and Community Professional
#iwork4Dell

NIC Driver Problem in WDS 2010

Not sure if this is the right place to post this, but I am having an issue with re-imaging Dell Optiplex 745's. When I boot into the PE image and click on "Run Deployment Wizard", I get the message:
"A connection to the deployment share could not be made. The following device did not have a driver installed. PCI\VEN_14E4&DEV_167A&SUBSYS_01DA1028&REV_02."
Retry or Cancel.
After much headache over the past two days, I discovered this is the NIC which is a Broadcom 5754. I have tried injecting the driver (new and older versions) into the PE image in WDS but that doesn't seem to fix it. The driver is b57nd60a.inf. The older
driver I used (14.6.1.0) was previously used when imaging the machines. I have used the x64 Windows 7 version. Should I be using a different version for the PE image? I do not get an IP address in the PE so I know the driver is not correct or loading properly.
The Out-of-box drivers in the Deployment Workbench have nothing to do with the PE image, correct? They are just used when imaging the computers, right?
The previous network administrator has imaged all of these models before so it had to of worked at some point.
Any guidance is much appreciated.

The Out-Of-Box drivers node has everything to do with drivers for the WinPE boot image. By default it will inject all storage class abd network class driver it finds into the boot image.
What you should do however, is limit the amount of drivers being added to the boot image. For example, the workbench will happily inject wireless drivers by default to the boot image because it's a network class driver.
Check the "Drivers for Windows PE (the boot image)" section in this post for MDT 2010. It's stil very much valid for MDt 2012 Update 1 and MDT 2013.
http://www.deployvista.com/Default.aspx?tabid=78&EntryID=132
Note: After uppdating the deployment share (to get a new boot image), don't forget to replace the boot image in the WDS Console.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Ultra 20 workstation NIC driver install

Similar Messages

Maybe you are looking for