WINIPCFG Help

I have recently installed a new PCI network adapter
(Belkin) on my system (Win98SE). In device manager, all
appears fine (working normal). However in winipcfg, this
device does not show up, therefore I cannot connect
through DSL. I spent much time on the phone with Belkin
tech support and as far as troubleshooting with them,
everything is fine with the card.

Can anyone give me any ideas on what to do next?

Thanks in advance.

In article <1d2d701c453a5$ab22a460$(E-Mail Removed)>, "Sheila"
<(E-Mail Removed)> wrote:
>I have recently installed a new PCI network adapter
>(Belkin) on my system (Win98SE). In device manager, all
>appears fine (working normal). However in winipcfg, this
>device does not show up, therefore I cannot connect
>through DSL. I spent much time on the phone with Belkin
>tech support and as far as troubleshooting with them,
>everything is fine with the card.
>
>Can anyone give me any ideas on what to do next?
>
>Thanks in advance.

Go to Control Panel | Network and see whether there's a network
component shown as "TCP/IP -> Belkin PCI Network Adapter".

If there isn't, click Add | Protocol | Add | Microsoft | TCP/IP to add
it. If that doesn't work the problem could be that the computer
already has the maximum number of TCP/IP bindings. To increase the
maximum, follow the steps in this Microsoft Knowledge Base article:

Unable to Bind Protocols to More Than 5 Network Adapters
http://support.microsoft.com/?id=217744
--
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

>-----Original Message-----
>In article <1d2d701c453a5$ab22a460
$(E-Mail Removed)>, "Sheila"
><(E-Mail Removed)> wrote:
>>I have recently installed a new PCI network adapter
>>(Belkin) on my system (Win98SE). In device manager, all
>>appears fine (working normal). However in winipcfg,
this
>>device does not show up, therefore I cannot connect
>>through DSL. I spent much time on the phone with Belkin
>>tech support and as far as troubleshooting with them,
>>everything is fine with the card.
>>
>>Can anyone give me any ideas on what to do next?
>>
>>Thanks in advance.
>
>Go to Control Panel | Network and see whether there's a
network
>component shown as "TCP/IP -> Belkin PCI Network
Adapter".
>
>If there isn't, click Add | Protocol | Add | Microsoft |
TCP/IP to add
>it. If that doesn't work the problem could be that the
computer
>already has the maximum number of TCP/IP bindings. To
increase the
>maximum, follow the steps in this Microsoft Knowledge
Base article:
>
>Unable to Bind Protocols to More Than 5 Network Adapters
>http://support.microsoft.com/?id=217744
>--
>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
>.
>Thanks for the reply. I actually only have 2 TCP/IP
bindings. One for the dial-up and one for the belkin card.
During troubleshooting with Belkin last night, we actually
removed it and added it again. It still does not show up
as an option in the drop down in winipcfg.

I just performed a clean re-install of 98SE this past
weekend. I didn't receive any error messages, so I assumed
everything installed fine. Could something have screwed
upd during the re-install? I'm considering another re-
install since I don't have anything else installed yet
since the last one. I also have not yet been able to get
any of the updates for this install yet. Could this be
the problem? (This is what Belkin suggested).

Many thanks again,
Sheila Weitkamp