Install DLC Protocol on NICs automatically?

  • Thread starter Thread starter Steve Parkinson
  • Start date Start date
S

Steve Parkinson

I have created a component with all the necessary
resources to support the DLC network protocol. When my
system comes up after FBA is complete I can manually
install the protocol on my adapters. Does anyone know how
I can automate the process so it is not necessary to
manually install the protocol on the adapters.

Thanks!

Steve Parkinson
Halliburton
 
Steve,

Have you looked at snetcfg.exe utility (find it under XPE Repositary). It
may help you installing a protocol.
However, since DLC is no longer be supported on Windows XP, it mat not work
for you (I haven't tried it and can't confirm whether it works).

KM


SP> I have created a component with all the necessary resources to
SP> support the DLC network protocol. When my system comes up after FBA
SP> is complete I can manually install the protocol on my adapters.
SP> Does anyone know how
SP> I can automate the process so it is not necessary to manually
SP> install the protocol on the adapters.

SP> Thanks!

SP> Steve Parkinson
SP> Halliburton
 
Thank you KM, snetcfg.exe is exactly what I needed. The
following is the string I used.

snetcfg.exe -l %windir%\ing\netdlc.inf -c p -i ms_dlc
 
This works fine from the command line if run once FBA is
complete and the system is ready to use. For some reason
though when I add a Generic FBA resource to run the
command, after my system completes FBA, neither of my
adapters show up...

When I run snetcfg -s n I see that ms_dlc was indeed
installed during FBA but neither of my adapters appear.
They also do not appear in my network connections folder
or from ipconfig.

We have been using DLC with XP Pro for a long time and
have not had any problems. Any ideas on why the snetcfg
would have different results when run during and after
FBA?

Here's the settings for my Generic FBA command:
Arguments: -l %17%\netdlc.inf -c p -i ms_dlc
FilePath: %11%\snetcfg.exe
Phase: 8600 (This is the only FBA command I currently
have)
Everything else is default.
 
Steve,

To be honest, don't know why the installation fails on your target during
FBA.
What your FBALog.txt says about the protocol installation?
Just a couple simple guesses:
Change the Arguments to "-l c:\windows\inf\netdlc.inf -c p -i ms_dlc".
Change FBA phase to 8500 (although, it should not be a matter for you).

KM

S> This works fine from the command line if run once FBA is complete
S> and the system is ready to use. For some reason though when I add a
S> Generic FBA resource to run the command, after my system completes
S> FBA, neither of my adapters show up...

S> When I run snetcfg -s n I see that ms_dlc was indeed installed
S> during FBA but neither of my adapters appear.
S> They also do not appear in my network connections folder or from
S> ipconfig.

S> We have been using DLC with XP Pro for a long time and have not had
S> any problems. Any ideas on why the snetcfg would have different
S> results when run during and after
S> FBA?

S> Here's the settings for my Generic FBA command:
S> Arguments: -l %17%\netdlc.inf -c p -i ms_dlc
S> FilePath: %11%\snetcfg.exe
S> Phase: 8600 (This is the only FBA command I currently have)
S> Everything else is default.
 
Back
Top