MS has botched the Wireless networking DCHP

Discussion in 'Wireless Networking' started by Guest, Sep 6, 2004.

  1. Guest

    Guest Guest

    I have been using a Linksys Wireless B PC card in my notebook for two years
    with a Siemens Wireless B Router on my Broadband cable connection with no
    issues. In addition, I have used the same Linksys PC card with my other
    router, a Linksys Wireless B 4-port router/hub. About two weeks ago (before
    SP2), a recent download broke this funcitonality, and I can no longer acquire
    a DCHP address or make the wireless connection work. I can only get a
    connection if I wire my notebook directly to the router (defeats the concept
    of wireless).

    Since then, I have validated that it does not work with my Belkin Wireless G
    card with either the Siemens or Linksys routers. Does Microsoft not do
    regression testing with anything other than their own products?

    I hope their support reads this group, because I need a patch ASAP.
    Guest, Sep 6, 2004
    1. Advertisements

  2. Guest

    Bryan Martin Guest

    Follow the instructions below

    How to Recover from Winsock2 corruption
    To resolve this issue, delete the corrupted registry keys, and then
    reinstall of the TCP/IP protocol.
    Step 1: Delete the corrupted registry keys
    Click Start, and then click Run.
    In the Open box, type regedit, and then click OK.
    In Registry Editor, locate the following keys, right-click each key, and
    then click Delete:


    When you are prompted to confirm the deletion, click Yes.
    Note Restart the computer after you delete the Winsock keys. Doing so causes
    the Windows XP operating system to create new shell entries for those two
    keys. If you do not restart the computer after you delete the Winsock keys,
    the next step does not work correctly.
    Step 2: Install TCP/IP
    Right-click the network connection, and then click Properties.
    Click Install.
    Click Protocol, and then click Add.
    Click Have Disk.
    Type C:\Windows\inf, and then click OK.
    On the list of available protocols, click Internet Protocol (TCP/IP), and
    then click OK.
    Restart the computer.

    Bryan Martin
    Bryan Martin, Sep 6, 2004
    1. Advertisements

  3. Guest

    Chuck Guest


    Actually, the netsh command does both of those steps.
    1) Start - Run - "cmd". Type "netsh winsock reset catalog" into the command
    2) Restart system.
    3) Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the
    command window.
    4) Restart system.

    Be aware that, if you have any custom applications that inserted Winsock
    entries, and you want to continue using those applications, you may have to re
    install them.

    Paranoia comes from experience - and is not necessarily a bad thing.
    Chuck, Sep 7, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.