Announcement

Collapse
No announcement yet.

TCP/IP Network Transport failure

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • TCP/IP Network Transport failure

    I booted up my laptop this morning to discover that "The TCP/IP network transport is not installed."

    Funny, I was all over the net, web, email, just last night. Supposedly, TCP/IP is a "core component" of XP, and cannot be uninstalled. Apparently there's a grey area between 'installed' and 'not installed.'

    So I did a bit of good old fashioned google troubleshooting.

    Daniel, your article at http://www.petri.com/reinstall_tcp_ip_xp.htm was both informative and helpful. Sadly, netsh int ip reset ipresetlog.txt doesn't seem to have achieved the reinstallation of the protocol.

    System:
    Dell Latitude D600
    Windows XP Pro
    Intel Centrino 1.6 Ghz
    512 RAM
    40 GB HD

    Networking:
    Internal Truemobile 1300 Wireless
    Cisco 350 PCMCIA Wireless
    Integrated Broadcom 10/100 NIC
    Bluetooth
    IrDA
    Linksys WRT54G Wireless router/hub
    setup in gateway mode to offer dhcp addresses out to my machines. The one I am typing on right now is punching out to the net through this router, and the cable modem behind it
    Toshiba PCX 2500 Cable Modem
    I bought the second wireless card because it is much more stable at school.

    Symptoms:
    Cannot connect to net. Cannot retrieve email. Cannot secure IP addresses.

    What I've tried:

    ipconfig /all returns APIPA addresses.
    ip: 169.254.235.157
    sub: 255.255.0.0
    ip: 169.254.3.228
    ip: 255.255.0.0
    etc.

    I did enter a manual alternative ip address in the advanced tab of the TCP/IP settings for each adapter in an attempt to shake APIPA. In this case ipconfig /all simply returned the manually set ip addresses, rather than securing original ip addresses from my network.

    ipconfig /release returns
    "An error occured while releasing interface yy: the ssytem cannot find the file specified." for all three network adapters (2 wireless, 1 10/100)

    ipconfig /renew returns
    "An error occured while renewing interface yy: the system cannot find the file specified." again for all three network adapters.

    network adapter properties dialogue for each network adapter lists TCP/IP as a currently installed and selected (checked) protocol, along with Client for Ms Networks, Determnistic Network Enhancer, File and Print Sharing, and QoS Packet Scheduler - uninstalling TCP/IP, of course, is not an option.

    the log produced by netsh int ip reset ipresetlog.txt is included below.

    That's it. That's all I've got. I hope something here makes sense to someone.

    Sorry if I posted this in the wrong forum, I thought it would post under Networking, not Alcatel. I guess maybe I should have posted in Windows XP...

    NYLaw

    ipresetlog.txt:

    deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters \EnableLmhosts
    reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{3697B309-5BEB-441B-9EDD-39EE58800CA1}\AddressType
    old REG_DWORD = 1

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{3697B309-5BEB-441B-9EDD-39EE58800CA1}\IpAutoconfigurationAddress
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{3697B309-5BEB-441B-9EDD-39EE58800CA1}\IpAutoconfigurationMask
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{3697B309-5BEB-441B-9EDD-39EE58800CA1}\IpAutoconfigurationSeed
    reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{AA4BB8C5-513F-45E9-B108-937F76B3B5A0}\AddressType
    old REG_DWORD = 1

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{AA4BB8C5-513F-45E9-B108-937F76B3B5A0}\IpAutoconfigurationAddress
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{AA4BB8C5-513F-45E9-B108-937F76B3B5A0}\IpAutoconfigurationMask
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{AA4BB8C5-513F-45E9-B108-937F76B3B5A0}\IpAutoconfigurationSeed
    reset SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{C3E6F425-81C9-4E94-9DE4-2C1C8A162E4A}\AddressType
    old REG_DWORD = 1

    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{C3E6F425-81C9-4E94-9DE4-2C1C8A162E4A}\IpAutoconfigurationAddress
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{C3E6F425-81C9-4E94-9DE4-2C1C8A162E4A}\IpAutoconfigurationMask
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{C3E6F425-81C9-4E94-9DE4-2C1C8A162E4A}\IpAutoconfigurationSeed
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \DontAddDefaultGatewayDefault
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \EnableIcmpRedirect
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \EnableSecurityFilters
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \SearchList
    deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \UseDomainNameDevolution
    reset Linkage\UpperBind for PCMCIA\CISCO_SYSTEMS-350_SERIES_WIRELESS_LAN_ADAPTER-512A\1. bad value was:
    REG_MULTI_SZ =
    DNE

    reset Linkage\UpperBind for PCI\VEN_14E4&DEV_4320&SUBSYS_43201737& REV_02\5&11F07975&0&0008F0. bad value was:
    REG_MULTI_SZ =
    DNE

    reset Linkage\UpperBind for ROOT\NET\0000. bad value was:
    REG_MULTI_SZ =
    DNE

    reset Linkage\UpperBind for PCI\VEN_14E4&DEV_4320&SUBSYS_00011028& REV_02\4&39A85202&0&18F0. bad value was:
    REG_MULTI_SZ =
    DNE

    reset Linkage\UpperBind for PCI\VEN_14E4&DEV_16A6&SUBSYS_81261028& REV_02\4&39A85202&0&00F0. bad value was:
    REG_MULTI_SZ =
    DNE

    reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
    REG_MULTI_SZ =
    DNE

    <completed>

  • #2
    My fix

    I reached Dell customer support on this issue, and after a bit of troubleshooting found a solution.

    Win XP system restore enabled me to restore the system to a previous working configuration, and now all of my network adapters secure proper ips.

    Still don't know why the problem happened in the first place. We tried uninstalling all of the adapters and then letting Windows reinstall them on reboot, but that didn't work either.

    NYLaw

    Comment

    Working...
    X