How to Install TCP/IP

[Jim Romanchek]

I'm trying to install TCP/IP protocol on W2k SP4 machine. I've done it
a few times in the past. Now when I hit the Install_Add I'm getting an
error message that reads "specified path does not contain any applicable
device INFs". There is no opportunity to specify any path during the
installation procedure. Can anyone help?
Thanks,
Jim

 

[Steven L Umbach]

Tcp/ip is installed by default on all W2K computers. If there is a problem
and it was removed, etc. try going into Device Manager and uninstalling the
network adapter and reboot the computer at which time PNP should recognize
it and install it along with tcp/ip hopefully. --- Steve

 

[Jetro]

In addition, it might be a hardware problem and malfunctioning NIC in
particular or damaged driver.

If there are no setup information (INF) files for the particular class of
network components, SelectAndInstall returns a nonzero error code and
displays the following message to the user: "The specified path does not
contain any applicable device INFs."
The network configuration subsystem does not install the component until
INetCfg::Apply is called. The class GUID_DEVCLASS_NET used to obtain network
card components does not support SelectAndInstall. If notify objects call
SelectAndInstall for this class, it returns E_INVALIDARG. Users should
select network card components to install through the hardware wizard.

 

[Jim Romanchek]

Steve,
It was a good suggestion, but unfortunately it didn't work. Once I rebooted,
went through the "found new hardware" routine and reinstalled the network
adapter, TCP/IP was not installed. Any other ideas?
Thanks,
Jim

 

[Steven L Umbach]

I would try what Jetro recommended such as reinstalling drivers, seeing if
the manufacturer has updated drivers at their website, or trying a different
network card. I have had similar problems with flaky network adapters. You
might also try booting into safe mode with networking to see if it makes a
difference and if it does you have a problem with a startup
application/service. Another possibility is an in place upgrade of the
operating system where you pop in the install disk, let the setup start for
a new install and be SURE to select "upgrade". If you try that you will need
the product key for the operating system and have to first install the
service pack [SP4] and then critical updates from Windows Updates. I have
done that more than once with good results but I have a high speed internet
connection. If you have a dial up connection that may be saved for a last
resort repair, but it should preserve your applications and data. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175 --
explaination of W2K upgrade install.

 

[Jim Romanchek]

Steve,
Thanks for all the help. I finally fixed it by deleting a "disabled" network
device called WAN Miniport that had mysteriously appeared. (I had to edit the
registry to allow it to be deleted). Apparently that was stopping TCP/IP from
installing. Once the miniport was gone, I deleted the network card like you
first suggested. Upon reboot the network card was reinstalled together with
TCP/IP.
Thanks again,
Jim

I would try what Jetro recommended such as reinstalling drivers, seeing if
the manufacturer has updated drivers at their website, or trying a different
network card. I have had similar problems with flaky network adapters. You
might also try booting into safe mode with networking to see if it makes a
difference and if it does you have a problem with a startup
application/service. Another possibility is an in place upgrade of the
operating system where you pop in the install disk, let the setup start for
a new install and be SURE to select "upgrade". If you try that you will need
the product key for the operating system and have to first install the
service pack [SP4] and then critical updates from Windows Updates. I have
done that more than once with good results but I have a high speed internet
connection. If you have a dial up connection that may be saved for a last
resort repair, but it should preserve your applications and data. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175 --
explaination of W2K upgrade install.

Steve,
It was a good suggestion, but unfortunately it didn't work. Once I
rebooted,
went through the "found new hardware" routine and reinstalled the network
adapter, TCP/IP was not installed. Any other ideas?
Thanks,
Jim

 

[Steven L Umbach]

Great! Glad you got it sorted out and thanks for posting back the results so
we all can learn what worked for you. -- Steve

Steve,
Thanks for all the help. I finally fixed it by deleting a "disabled"
network
device called WAN Miniport that had mysteriously appeared. (I had to edit
the
registry to allow it to be deleted). Apparently that was stopping TCP/IP
from
installing. Once the miniport was gone, I deleted the network card like
you
first suggested. Upon reboot the network card was reinstalled together
with
TCP/IP.
Thanks again,
Jim

I would try what Jetro recommended such as reinstalling drivers, seeing
if
the manufacturer has updated drivers at their website, or trying a
different
network card. I have had similar problems with flaky network adapters.
You
might also try booting into safe mode with networking to see if it makes
a
difference and if it does you have a problem with a startup
application/service. Another possibility is an in place upgrade of the
operating system where you pop in the install disk, let the setup start
for
a new install and be SURE to select "upgrade". If you try that you will
need
the product key for the operating system and have to first install the
service pack [SP4] and then critical updates from Windows Updates. I have
done that more than once with good results but I have a high speed
internet
connection. If you have a dial up connection that may be saved for a last
resort repair, but it should preserve your applications and data. ---
Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175 --
explaination of W2K upgrade install.

Steve,
It was a good suggestion, but unfortunately it didn't work. Once I
rebooted,
went through the "found new hardware" routine and reinstalled the
network
adapter, TCP/IP was not installed. Any other ideas?
Thanks,
Jim


Steven L Umbach wrote:

Tcp/ip is installed by default on all W2K computers. If there is a
problem
and it was removed, etc. try going into Device Manager and
uninstalling
the
network adapter and reboot the computer at which time PNP should
recognize
it and install it along with tcp/ip hopefully. --- Steve

I'm trying to install TCP/IP protocol on W2k SP4 machine. I've done
it
a few times in the past. Now when I hit the Install_Add I'm getting
an
error message that reads "specified path does not contain any
applicable
device INFs". There is no opportunity to specify any path during
the
installation procedure. Can anyone help?
Thanks,
Jim