NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

seankc's avatar
seankc
Aspirant
Jul 09, 2019
Solved

wired PC can't connect to wireless printer

My nighthawk router bit the dust so I replaced it with another nighthawk that I have used in the past. I changed the name and password of the wireless network to match the router that failed. I conne...
  • IrvSp's avatar
    IrvSp
    Jul 10, 2019

    seankc wrote:

    Yes, it's an R7000, sorry about that. The My Printer canon tool is used when connected via usb. I use the wired connection for this PC. I can't connect to to routerlogin.com on the wired PC. I can connect on the wireless PC. The wired PC doesn't show as a connected device. 

     


    You answer is now more confusing? Something is clearly wrong. The tool should not be used unless you can't connect?

     

    Normally the router sends out the SSID and the Printer sees it and connects to it. It then gets an IP Address that other LAN devices can see and use by loading the printer driver and making that the default printer. If you can't see the printer, then the tool is use, the MY PRINTER tool.

     

    Link to it:

     

    https://canonusa.allegiancetech.com/cgi-bin/qwebcorporate.dll?idx=M6BSBQ&mcxModel=&mcxPCategory=&mcxID=M6BSBQ&mcxReferrerURL=https%3A%2F%2Fwww.usa.canon.com%2Finternet%2Fportal%2Fus%2Fhome%2Fsupport%2Fdetails%2Fprinters%2Finkjet-multifunction%2Fmx-series-inkjet%2Fmx472%2Fpixma-mx472%3Fcm_sp%3DCSO-_-PFListing-_-MX472&ref_url=https://www.usa.canon.com/internet/portal/us/home/support/details/printers/inkjet-multifunction/mx-series-inkjet/mx472/pixma-mx472?cm_sp=CSO-_-PFListing-_-MX472

     

    (Optional)This application facilitates basic maintenance and trouble-shooting for your product.

     

    The MX470 is OLD and need to use the current model, MX472.

     

    This part confuses me but might be a CLUE, "I can't connect to to routerlogin.com on the wired PC. I can connect on the wireless PC. The wired PC doesn't show as a connected device. "?

     

    How MANY PC's are we talking about in that sentence, 1 or 2? If two, then the problem could be WHAT is ahead of the ROUTER? A modem or modem/router? Make and model please.

     

    The hint is ROUTERLOGIN.COM. If you are using the router's DNS that gets the ISP's one, that URL is resolved to the router.

     

    So as I see it, you have a configuration problem. One that doesn't make sense at all either. IF, and that is a big IF, you plugged the wired PC directly into one of the four ports of the R7000, then ROUTERLOGIN.NET will work as long as the router is configured to get the ISP's DNS. So that leads me to three possible conclusions:

     

    • You have a BAD Ethernet cable.
    • There is a bad port on the PC.
    • There is a bad port on the router (easy to test by using a different port).

    Assuming you can verify none of those are the case (basically because you said it worked before but things can break), then the problem would be 'where are you connecting the cable to?

     

    I still don't understand the original comment in the 1st post, "When I connect to the wireless, I see a 2nd network for the wireless. Another network for the wired PC." How are you seeing 2 networks? Do you mean SSID's?

     

    I am sort of thinking you DO have a MODEM/ROUTER and the WIRELESS is connecting to the MODEM. That would make sense to me in that you have TWO different LAN's, one from the MODEM/ROUTER and another from the Router which would be the ONLY place you could connect the WIRED PC to.

     

    Can you LIST all SSID's the WIRELESS devices see?

     

    If you are on Windows, please use the WINDOWS KEY+R and enter CMD and press enter. Then enter IPCONFIG /ALL on both the PC that can be both wired and wireless for each type of connection. It should look like this:

     

    ---------------------------

    C:\>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Irv8700
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

     

    Ethernet adapter Ethernet:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
    Physical Address. . . . . . . . . : F8-B1-56-DD-6A-5B
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::58bf:9e27:bf45:87e8%8(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.12(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Wednesday, July 10, 2019 3:22:47 PM
    Lease Expires . . . . . . . . . . : Thursday, July 11, 2019 3:22:46 PM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 49852758
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-04-98-17-F8-B1-56-DD-6A-5B
    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

     

    Wireless LAN adapter Wi-Fi 3:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : NETGEAR A6200 WiFi Adapter
    Physical Address. . . . . . . . . : 08-BD-43-A5-8C-AA
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::835:5b00:35a2:407c%4(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.50(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Wednesday, July 10, 2019 1:32:47 PM
    Lease Expires . . . . . . . . . . : Thursday, July 11, 2019 1:32:47 PM
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 587775299
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-04-98-17-F8-B1-56-DD-6A-5B
    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    ===========================

     

    In the above, I had both types of connections enabled at the same time to show you what each should look like. I suggest you don't do that but enable each one individually and then cut and paste the data for each into a reply.

     

    That will possibly clear all this up.