The TCP/IP network transport is not installed

Try uninstalling the network adapter in device manager, rebooting, and
letting XP reinstall it.

If you are still having trouble then type "ipconfig /renew" at a command
line. If you get an error about something not being a socket or not being
able to load a specified provider then read on.

I have traced several of these problems to improperly configured winsock
LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.

If that fails or your provider list is empty, you may need to rebuild the
catalog from scratch. The following instructions will rebuild your catalog
for TCP/IP. If you are using any other transports (If you don't know, then
you probably aren't) then you will have to reinstall them as well.


1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock2

2. Reboot

3. Go to the network connections folder, right click the icon for your
network connection, and select properties.

4. Click install, choose "protocol", and click "add..."

5. Click "Have Disk...", enter "\windows\inf", click OK

6. Select "Internet Protocol (TCP/IP), click OK

7. When the process in complete, reboot

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"Bob" <bobwmonahan@earthlink.net> wrote in message
news:062a01c361fc$45a770c0$a501280a@phx.gbl...

> Still need help... Getting desparate.
>
>

> >-----Original Message-----
> >I was trying to connect to the broadband network at my
> >work last night with my laptop that runs XP Home.
> >
> >I was unsuccessful after fiddling with it for quite

> awhile.

> >
> >Now I can't even use my dialup at home.
> >
> >When I boot I get this error message.
> >
> >"Mobile Devices Properties"
> >"The TCP/IP network transport is not installed"
> >
> >Any ideas?
> >
> >$bob$
> >.
> >

Ken,
It works!
I stumbled across your words of wisdom here, after having had a
two-day ordeal trying to back out of a broken McAfee installation that
left me in the "network transport not installed" boat along with many
others. I am running Win2000, and had tried - only partially
successfully - to install McAfee Internet Security 5. It was secure
alright - I couldn't connect at all.

I was getting desparate, seeing so many unhelful "just reinstall the
TCP/IP stack" responses on the web.

Many thanks for reply to Bob's and my plight. Now if only Microsoft
would put something in the knowledgebase about it ...

Anyway, your fix worked perfectly. Now, at 5:32 AM, I can go get some
sleep.

Julian.
=================================


"Ken Wickes [MSFT]" <kenwic@online.microsoft.com> wrote in message news:<#Wbpr6fYDHA.736@TK2MSFTNGP09.phx.gbl>...

> Try uninstalling the network adapter in device manager, rebooting, and
> letting XP reinstall it.
>
> If you are still having trouble then type "ipconfig /renew" at a command
> line. If you get an error about something not being a socket or not being
> able to load a specified provider then read on.
>
> I have traced several of these problems to improperly configured winsock
> LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
> names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
> Provider" should be fine. Anything else is suspect, and uninstalling the
> owning program might help.
>
> If that fails or your provider list is empty, you may need to rebuild the
> catalog from scratch. The following instructions will rebuild your catalog
> for TCP/IP. If you are using any other transports (If you don't know, then
> you probably aren't) then you will have to reinstall them as well.
>
>
> 1. Backup and delete the following registry keys
>
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock2
>
> 2. Reboot
>
> 3. Go to the network connections folder, right click the icon for your
> network connection, and select properties.
>
> 4. Click install, choose "protocol", and click "add..."
>
> 5. Click "Have Disk...", enter "\windows\inf", click OK
>
> 6. Select "Internet Protocol (TCP/IP), click OK
>
> 7. When the process in complete, reboot
>
> --
>
> Ken Wickes [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Bob" <bobwmonahan@earthlink.net> wrote in message
> news:062a01c361fc$45a770c0$a501280a@phx.gbl...

> > Still need help... Getting desparate.
> >
> >

> > >-----Original Message-----
> > >I was trying to connect to the broadband network at my
> > >work last night with my laptop that runs XP Home.
> > >
> > >I was unsuccessful after fiddling with it for quite

> awhile.

> > >
> > >Now I can't even use my dialup at home.
> > >
> > >When I boot I get this error message.
> > >
> > >"Mobile Devices Properties"
> > >"The TCP/IP network transport is not installed"
> > >
> > >Any ideas?
> > >
> > >$bob$
> > >.
> > >

I have been attempting to get this into the KB, but things can move slowly
sometime.

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"Julian Opificius" <julianop@mninter.net> wrote in message
news:af571aa0.0308310237.75ae145f@posting.google.c om...

> Ken,
> It works!
> I stumbled across your words of wisdom here, after having had a
> two-day ordeal trying to back out of a broken McAfee installation that
> left me in the "network transport not installed" boat along with many
> others. I am running Win2000, and had tried - only partially
> successfully - to install McAfee Internet Security 5. It was secure
> alright - I couldn't connect at all.
>
> I was getting desparate, seeing so many unhelful "just reinstall the
> TCP/IP stack" responses on the web.
>
> Many thanks for reply to Bob's and my plight. Now if only Microsoft
> would put something in the knowledgebase about it ...
>
> Anyway, your fix worked perfectly. Now, at 5:32 AM, I can go get some
> sleep.
>
> Julian.
> =================================
>
>
> "Ken Wickes [MSFT]" <kenwic@online.microsoft.com> wrote in message

news:<#Wbpr6fYDHA.736@TK2MSFTNGP09.phx.gbl>...

> > Try uninstalling the network adapter in device manager, rebooting, and
> > letting XP reinstall it.
> >
> > If you are still having trouble then type "ipconfig /renew" at a command
> > line. If you get an error about something not being a socket or not

being

> > able to load a specified provider then read on.
> >
> > I have traced several of these problems to improperly configured winsock
> > LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
> > names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
> > Provider" should be fine. Anything else is suspect, and uninstalling

the

> > owning program might help.
> >
> > If that fails or your provider list is empty, you may need to rebuild

the

> > catalog from scratch. The following instructions will rebuild your

catalog

> > for TCP/IP. If you are using any other transports (If you don't know,

then

> > you probably aren't) then you will have to reinstall them as well.
> >
> >
> > 1. Backup and delete the following registry keys
> >
> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock
> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock2
> >
> > 2. Reboot
> >
> > 3. Go to the network connections folder, right click the icon for your
> > network connection, and select properties.
> >
> > 4. Click install, choose "protocol", and click "add..."
> >
> > 5. Click "Have Disk...", enter "\windows\inf", click OK
> >
> > 6. Select "Internet Protocol (TCP/IP), click OK
> >
> > 7. When the process in complete, reboot
> >
> > --
> >
> > Ken Wickes [MSFT]
> > This posting is provided "AS IS" with no warranties, and confers no

rights.

> >
> >
> > "Bob" <bobwmonahan@earthlink.net> wrote in message
> > news:062a01c361fc$45a770c0$a501280a@phx.gbl...

> > > Still need help... Getting desparate.
> > >
> > >
> > > >-----Original Message-----
> > > >I was trying to connect to the broadband network at my
> > > >work last night with my laptop that runs XP Home.
> > > >
> > > >I was unsuccessful after fiddling with it for quite

> > awhile.

> > > >
> > > >Now I can't even use my dialup at home.
> > > >
> > > >When I boot I get this error message.
> > > >
> > > >"Mobile Devices Properties"
> > > >"The TCP/IP network transport is not installed"
> > > >
> > > >Any ideas?
> > > >
> > > >$bob$
> > > >.
> > > >

i assume you have checked your protocols on all your
adpaters? have u got tcp/ip binded to them?

also try this - goto-contorl panel-admin tools-compent
services-right clcik on your local system-proerties-then
check here if tcp/ip is installed and dcom is enabled

>-----Original Message-----
>Greetings!
>
>I have a laptop with XP Professional installed on it.
>Recently I started getting the message upon login
>saying "The TCP/IP network transport is not installed".
>From what I know of XP, that isn't really possible. I am
>unable to connect to my LAN.
>
>Any ideas for me?
>.
>

Re postings on this topic 13th August to 29th September. This is sound and
good advice offered by the respondent below. It worked for me (operating
under Windows 2000) and solved the problem described which was possibly
caused when I tried to uninstall Ontrack SystemSuiite 4. The only slight
amendment I would make to the protocol was that with the Windows 2K CD in
the drive, there was no need to enter under point 5 in the list
"\windows\inf" - the CD did the 'biz' itself.

Many thanks to Ken Wickes.

Dormouse

From: Ken Wickes [MSFT] (kenwic@online.microsoft.com)
Subject: Re: The TCP/IP network transport is not installed



View this article only
Newsgroups: microsoft.public.windowsxp.network_web
Date: 2003-08-13 17:56:18 PST

Try uninstalling the network adapter in device manager, rebooting, and
letting XP reinstall it.

If you are still having trouble then type "ipconfig /renew" at a command
line. If you get an error about something not being a socket or not being
able to load a specified provider then read on.

I have traced several of these problems to improperly configured winsock
LSPs. Run "winmsd" and go to Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and uninstalling the
owning program might help.

If that fails or your provider list is empty, you may need to rebuild the
catalog from scratch. The following instructions will rebuild your catalog
for TCP/IP. If you are using any other transports (If you don't know, then
you probably aren't) then you will have to reinstall them as well.


1. Backup and delete the following registry keys

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Winsock2

2. Reboot

3. Go to the network connections folder, right click the icon for your
network connection, and select properties.

4. Click install, choose "protocol", and click "add..."

5. Click "Have Disk...", enter "\windows\inf", click OK

6. Select "Internet Protocol (TCP/IP), click OK

7. When the process in complete, reboot

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.