Wired ethernet not working after wireless setup

Discussion in 'Wireless Networking' started by STAN1ZX, Sep 25, 2007.

  1. STAN1ZX

    STAN1ZX Guest

    I have recently setup a wireless network and in the process I have lost the
    ability to use my PC off the network by going wired from the ethernet
    connector on the PC, to the ethernet connector on the modem
    Is this normal or did I do something wrong??
    The wireless Linksys-N network is working as expected.

    STAN1ZX, Sep 25, 2007
    1. Advertisements

  2. Turn off the wireless nic before pluging in the cable.
    Sometimes it is a switch on the machine,..sometimes it is a function key
    combination,...sometimes you can right-click on the wireless connection (in
    several places) and choose "Disable".

    You don't want to have two network interfaces active on the same Network
    Segment at the same time.

    Phillip Windell

    The views expressed, are my own and not those of my employer, or Microsoft,
    or anyone else associated with me, including my cats.
    Phillip Windell, Sep 25, 2007
    1. Advertisements

  3. Hi
    You can set the preference so that it would work with the wired connection
    when it is available.
    Here how, http://www.ezlan.net/metrics.html
    Jack (MVP-Networking).
    Jack \(MVP-Networking\)., Sep 25, 2007
  4. STAN1ZX

    STAN1ZX Guest

    Hi Jack and Phillip,
    Thanks for responding to my post.
    Before I start and before I bring this machine down to less than square 1.
    I need your advice on the following.
    The machine in question is XP tabletop, which originally was wired from the
    Ethernet on the PC
    to the Ethernet on the modem.
    I have since installed a PCI wireless card on this XP machine to work it
    through a wireless Linksys router.
    In the process of setting this up, the wireless card worked right up to
    the "access point but could not
    get through the router".
    Eventually I had to use the "Windows Zero Config Utility" to get it setup.
    and working through the wireless card to the modem.
    In trying to determine if I still had wired Ethernet function on this XP
    desktop, by wiring directly from the Ethernet connector on the PC to the
    Ethernet on the modem, I found that the desktop could not see the
    modem.even after going through its self diagnostics. Apparently, this
    connectivity on the PC is lost.
    Given this scenario, is there anything else I should know about or do before
    starting the outlined procedure to maintain the wireless connectivity and
    rebuild the Ethernet? Hopefully ending up with a working wireless
    connection to the wireless router and Ethernet capability when needed.

    ----- Original Message -----
    From: "Jack (MVP-Networking)." <>
    Newsgroups: microsoft.public.windows.networking.wireless
    Sent: Tuesday, September 25, 2007 3:35 PM
    Subject: Re: Wired ethernet not working after wireless setup
    STAN1ZX, Sep 26, 2007
  5. You may be misusing the terminology and confusing us as to what devices you
    really have. These are all distinctly separate devices for different

    Cable/DSL modem
    Broadband "router"
    Broadband wireless "router"
    Access Point

    A broadband router is in most cases a Switch and a NAT Firewall built into
    the same device. Some of them also include a Cable/DSL modem built into
    them as well

    A broadband wireless router is a Switch, a NAT Firewall, and an Access
    Point, and possibly a Cable/DSL modem all built into the same device

    An Access Point is not a "router". In some cases it is both an Access Point
    and a Switch built into the same device, and that is usually distinguished
    by how many ethernet ports are on the back of it. A straight Access Point
    will only have one port.

    If the "modem" is a separate device from the "router" then you never really
    connect to the modem,...it is a Layer2 device and is effectively
    "invisible". You would connect to the "router" if there is one, and if not
    then the next closest device would be the ISP's internet router at the
    opposite end of the line.

    Anyway, no matter which Nic you use you need to make sure it gets an IP
    configuration from either your "router" or the ISP's DHCP. If it gets an
    address that begins with 169 then is has failed. Check it by running
    "ipconfig" from a command prompt. If it gets a good config then ping the ip
    number that is reported as the Default Gateway and verify that you get a

    The Access Point, once configured and connected to, also acts as a Layer2
    device and is effectively "invisible". The only thing that even knows the
    Access Point is there is the Radio component of the wireless nic. The IP#
    of the Access Point is only for the purpose of managing the Access Point
    with the management interface and serves no other real purpose. The Access
    Point is more-or-less identical to a Network Switch except that the Clients
    don't use wires to connect to it. In this paragraph I am not talking about
    a wireless "router" which has an Access Point built into it.

    Phillip Windell

    The views expressed, are my own and not those of my employer, or Microsoft,
    or anyone else associated with me, including my cats.
    Understanding the ISA 2004 Access Rule Processing

    Troubleshooting Client Authentication on Access Rules in ISA Server 2004

    Microsoft Internet Security & Acceleration Server: Partners

    Microsoft ISA Server Partners: Partner Hardware Solutions
    Phillip Windell, Sep 26, 2007
    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.