Issues binding TCP/IP to NIC

To summarize, I had issues with my PC, lost my network connection,
reinstalled my NIC (working properly according to device manager), removed
and redid all network components (Client, protocol etc.). The issue is that
now the TCP/IP protocol is not binding to by NIC. When I try to "fake it
out" and add IPX/SPX, it looks like it is binding to both, but still no
connection. When I remove the IPX/SPX, the TCP/IP binding is again lost.

Obviously, any suggestions appreciated.

" wrote
in message ...
To summarize, I had issues with my PC, lost my network connection,
reinstalled my NIC (working properly according to device manager), removed
and redid all network components (Client, protocol etc.). The issue is
that
now the TCP/IP protocol is not binding to by NIC. When I try to "fake it
out" and add IPX/SPX, it looks like it is binding to both, but still no
connection. When I remove the IPX/SPX, the TCP/IP binding is again lost.

Obviously, any suggestions appreciated.

could be winsock stack is corrupt ?

read here

http://cexx.org/lspfix.htm

" wrote
in message ...
To summarize, I had issues with my PC, lost my network connection,
reinstalled my NIC (working properly according to device manager), removed
and redid all network components (Client, protocol etc.). The issue is
that
now the TCP/IP protocol is not binding to by NIC. When I try to "fake it
out" and add IPX/SPX, it looks like it is binding to both, but still no
connection. When I remove the IPX/SPX, the TCP/IP binding is again lost.

Obviously, any suggestions appreciated.

could be winsock stack is corrupt ?

read here

http://cexx.org/lspfix.htm

In article ,
"
wrote:
To summarize, I had issues with my PC, lost my network connection,
reinstalled my NIC (working properly according to device manager), removed
and redid all network components (Client, protocol etc.). The issue is that
now the TCP/IP protocol is not binding to by NIC. When I try to "fake it
out" and add IPX/SPX, it looks like it is binding to both, but still no
connection. When I remove the IPX/SPX, the TCP/IP binding is again lost.

Obviously, any suggestions appreciated.

How do you know that TCP/IP isn't binding to the NIC?

If a computer only has one network adapter, the adapter name and
protocol name appear in the list of network components, with no
explicit indication of the binding. For example:

Client for Microsoft Networks
Ethernet Adapter
TCP/IP
File and Printer Sharing for Microsoft Networks

If a computer has more than one network adapter, the bindings are
shown explicitly. For example:

Client for Microsoft Networks
Dial-Up Adapter
Ethernet Adapter
TCP/IP - Dial-Up Adapter
TCP/IP - Ethernet Adapter
File and Printer Sharing for Microsoft Networks
--
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 ,
"
wrote:
To summarize, I had issues with my PC, lost my network connection,
reinstalled my NIC (working properly according to device manager), removed
and redid all network components (Client, protocol etc.). The issue is that
now the TCP/IP protocol is not binding to by NIC. When I try to "fake it
out" and add IPX/SPX, it looks like it is binding to both, but still no
connection. When I remove the IPX/SPX, the TCP/IP binding is again lost.

Obviously, any suggestions appreciated.

How do you know that TCP/IP isn't binding to the NIC?

If a computer only has one network adapter, the adapter name and
protocol name appear in the list of network components, with no
explicit indication of the binding. For example:

Client for Microsoft Networks
Ethernet Adapter
TCP/IP
File and Printer Sharing for Microsoft Networks

If a computer has more than one network adapter, the bindings are
shown explicitly. For example:

Client for Microsoft Networks
Dial-Up Adapter
Ethernet Adapter
TCP/IP - Dial-Up Adapter
TCP/IP - Ethernet Adapter
File and Printer Sharing for Microsoft Networks
--
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