Missing Bindings TCP/IP

The TCP/IP protocol will not bind to anything. It is
shown as a component in network configuration but with no
bindings. We have tried removing all network components,
removing drvdata.bin/drvidex.bin (as MS KB article 295085)
but TCP/IP protocol (unbound) always appears without
having to re-install.

How can we force it to re-install and bind to dial-up
adaptor/realtek 8139 network card?

(It was all working fine but seems to have become
corrupted whilst installing an SBS 4.5 client)

John

In article <040501c36d56$d5cef0f0$(E-Mail Removed)>, "John"
<(E-Mail Removed)> wrote:
>The TCP/IP protocol will not bind to anything. It is
>shown as a component in network configuration but with no
>bindings. We have tried removing all network components,
>removing drvdata.bin/drvidex.bin (as MS KB article 295085)
>but TCP/IP protocol (unbound) always appears without
>having to re-install.
>
>How can we force it to re-install and bind to dial-up
>adaptor/realtek 8139 network card?
>
>(It was all working fine but seems to have become
>corrupted whilst installing an SBS 4.5 client)
>
>John

There might not be a problem. Have you tried using TCP/IP anyway?

If the computer only has one network adapter, it won't show the TCP/IP
binding explicitly. For example:

Client for Microsoft Networks
Realtek 8139
TCP/IP
File and Printer Sharing

If the computer has more than one network adapter, it will show the
bindings explicitly. For example:

Client for Microsoft Networks
Dial-Up Adapter
Realtek 8139
TCP/IP -> Dial-Up Adapter
TCP/IP -> Realtek 8139
File and Printer Sharing

Go to Start | Run | Winipcfg and see if it shows the TCP/IP properties
for the Realtek card. If it does, everything should be working.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

In article <017f01c36d7c$3bdd5880$(E-Mail Removed)>, "John"
<(E-Mail Removed)> wrote:
>Thanks Steve
>
>I'll try that tomorrow (the machine is not at this site).
>Perhaps the problem is elsewhere (ie not the bindings)but
>a PING to the server produces an immediate 'destination
>host unreachable'. The network card appears to be working
>correctly and the full network logon appears (ie,user,
>password, domain)
>
>John

I'm sure that TCP/IP is bound to the network card. Otherwise, the
PING would give a different error message.

"Destination host unreachable" means that TCP/IP is working, but it
doesn't know how to send packets to the address that you're pinging,
i.e. there's no matching route in the route table. You can use this
command to write the route table to a file:

route print >route.txt
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm