win98SE and XP internet sharing via linksys wireless B router and wpc11 wireless

Discussion in 'Windows Networking' started by Darlene, Jan 21, 2004.

  1. Darlene

    Darlene Guest

    We are trying to share internet connections between a
    desktop and a laptop. We have DSL with an external DSL
    ethernet modem. Before getting DSL we were using aol
    dialup. We see both the dial up adapter and the wireless
    adapter in the control panel under networking. I read
    where 10038: The port which your card tries to open..is
    already opened by another internet application.
    Ok here is the problem. After installing the linksys
    router software on the Desktop, running XP. The desktop
    connects fine. It can ping the ip address, and it can ping
    the web address, and even view web sites. The laptop
    running WIN98SE ver 4.10.2222A after installing the
    hardware and software was pinging both ipaddress and web
    address, but not able to open a website. When you restart
    the laptop a message box pops up in the header of the box
    states:Wireless-B Notebook adapter WLAN monitor. then it
    states inside the message box 10038: Socket operation on
    non-socket. How do I fix it. I am thinking we need to
    remove anything associated with the dial up adapters but I
    am not quite sure about this. Should we remove any tcp/ip
    dial up adapters as well? It would seem like the logical
    thing to do. I disabled the dial up adapters, I can still
    ping but can't access a website .Then the next thing is to
    get the two computers sharing the internet connection.
     
    Darlene, Jan 21, 2004
    #1
    1. Advertisements

  2. Before you mess with network settings, scan your system for spyware or
    adware that may have altered the network stack. Error 10038 after changing
    connection types almost always means that some nasty software has messed
    with the TCP/IP network.

    http://www.lavasoftusa.com/

    Get AdAware, install it, update it, then run it and clean off everything it
    finds. Restart and run it again, keep running and cleaning and restarting
    until clean. Then try your network again.
     
    Richard G. Harper, Jan 21, 2004
    #2
    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.