Can't ping router through physical Ethernet (Wi-fi works fine)

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 10
       #1

    Can't ping router through physical Ethernet (Wi-fi works fine)


    I have set up a Windows 10 computer, and initially I used a wireless adapter, but now I've moved it into my office and connected via Ethernet cable instead, it refuses to talk to the router. (The wireless adapter still works if I plug it in.)

    I would like help understanding why a very simple Ethernet connection is not working. Here are the steps that I've tried, and their results. I apologise for the long post, but I've tried so many different things!

    I booted the computer into Lubuntu, and it works perfectly.
    The indicator on the router, and the LEDs on the ethernet socket indicate that there's a hardware connection, in both Linux and Windows. No hardware was changed, other than plugging in the USB stick.

    I have tried using DHCP on the router (whose IP address is 192.168.1.1), in this case 'ping' says:

    Code:
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    PS C:\Windows\system32>

    It seems that with this setting, Windows fails to see the DHCP server, so it sets its own random(?) IP address, which is not within the subnet for the router, hence the failure.
    I have also tried manually setting a valid IP address (192.168.1.25) in which case 'ping' says:

    Code:
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    
    PS C:\Windows\system32>

    Note that during this ping test, the status page of the router lists 192.168.1.25 as having "active sessions" and 0 TCP and 1 UDP sessions are listed.

    In the control panel, the Network status shows as:
    Code:
    "No Internet access"
    Your device is connected, but you might not be able to access anything on the network.
    
    IPv4 address:    192.168.1.25
    IPv4 DNS servers:    192.168.1.1
    Manufacturer:    Realtek
    Description:    Realtek PCIe GBE Family Controller
    Driver version:    9.1.406.2015
    Physical address (MAC):    30-9C-23-99-C7-66
    
    If I run the troubleshooter, I get this:
    Windows Network Diagnostics:
    "Investigate router or broadband modem issues"
    
    And the detail says:
    Troubleshooting report:
    "The default gateway is not available" (not fixed)
    
    Diagnostics Information (Network Adapter) 
    Details about network adapter diagnosis: 
    
    Network adapter Ethernet driver information:
    
       Description . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Manufacturer  . . . . . . . . . : Realtek
       Provider  . . . . . . . . . . . : Microsoft
       Version   . . . . . . . . . . . : 9.1.406.2015
       Inf File Name . . . . . . . . . : C:\Windows\INF\rt640x64.inf
       Inf File Date . . . . . . . . . : April 11, 2018  11:33:49 PM
       Section Name  . . . . . . . . . : RTL8168.ndi
       Hardware ID . . . . . . . . . . : pci\ven_10ec&dev_8168&rev_15
       Instance Status Flags . . . . . : 0x180200a
       Device Manager Status Code  . . : 0
       IfType  . . . . . . . . . . . . : 6
       Physical Media Type . . . . . . : 14
    
     
    Name:    Ethernet
    Description:    Realtek PCIe GBE Family Controller
    Physical address (MAC):    30:9c:23:99:c7:66
    Status:    Operational
    Maximum transmission unit:    1500
    IPv4 address:    192.168.1.25/24
    IPv6 address:    fe80::c12a:2ece:f906:bd76%9/64
    Default gateway:    192.168.1.1
    DNS servers:    192.168.1.1
    Connectivity (IPv4/IPv6):    Connected to unknown network, no traffic
                                           
    I have tried turning off the firewall, but it does nothing.                                       
    I have performed a "Network Reset" (on the settings page).
    I have rebooted the computer.
    I have rebooted the router.
    
    PS C:\Windows\system32> ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : Rayquaza
       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. . . . . . . . . : 30-9C-23-99-C7-66
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::492c:ab27:8b8:5e29%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.25(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 271621155
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-4A-51-12-30-9C-23-99-C7-66
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    PS C:\Windows\system32>
    Any help would be appreciated, as you can imagine after all this, I'm at my wits' end. Every component is proven to work, yet it won't connect as it should.
    Last edited by Brink; 09 Oct 2018 at 17:27. Reason: code box
      My Computer

  2. Caledon Ken's Avatar
    Posts : 24,263
    Windows 10 Pro x64 Version 2004
       #2

    Hi Andy. Welcome to the TenForums @AndyCivil

    So the basics. Please power off router, wait, power on.

    Did you try alternate cable?

    While a wild shot could be adapter is hung in windows.

    Power off machine, disconnect from wall (this is a must or unplugged at PSU), hold power switch on for 20 secs, reconnect and boot.

    You could also try these four resets.

    Run the following four bolded commands. Use a Command Prompt(admin) or Powershell(admin)

    Do not key in info in brackets, there for your information.

    ipconfig /flushdns (Clear the dns cache)
    nbtstat -RR (release and refresh NetBIOS names)
    netsh int ip reset (reset ip settings)
    netsh winsock reset (Reset Winsock Catalog)


    Ken
      My Computer

  3. Eagle51's Avatar
    Posts : 1,471
    Win10 Home x64 - 1809
       #3

    Name: Ethernet
    Description: Realtek PCIe GBE Family Controller
    Physical address (MAC): 30:9c:23:99:c7:66
    Status: Operational
    Maximum transmission unit: 1500
    IPv4 address: 192.168.1.25/24
    IPv6 address: fe80::c12a:2ece:f906:bd76%9/64
    Default gateway: 192.168.1.1
    DNS servers: 192.168.1.1
    Connectivity (IPv4/IPv6): Connected to unknown network, no traffic
    Couple of other possibilities ...
    1. Check if your Ethernet Network Profile set to Private.
    2. If your router has Access Control & it's turned on, make sure it's not blocking your Ethernet Adapter by it's MAC address.
      My Computers

  4. Samuria's Avatar
    Posts : 6,070
    windows 10
       #4

    Can you connect via wireless again then open a cmd prompt type


    ipconfig/all

    post results so we can see you have correct settings
      My Computer

  5. Berton's Avatar
    Posts : 10,584
    Win10 Pro Versions 2004 and 2009/20H2, Win10 Pro IP_Dev, Win10 Home 1909
       #5

    To avoid errors use ipconfig /all as the space before the slash / usually is necessary.
      My Computers


  6. Posts : 6
    Windows 10
    Thread Starter
       #6

    Thank you for the suggestions.

    Ken,
    Yes, I've tried three different cables, and two routers.
    Yes, I power cycled the router.
    I tried your reset suggestions, results follow, none worked.
    Eagle,
    I can't set the network profile because it says there's 'no network'.
    However, if I let Windows choose its own IP address, then I think it did show the profile as 'public',
    perhaps because it was connected after the initial setup? That would fit, but SURELY I'd still be
    able to ping the router in either case?
    I have not set up MAC filtering on the router. I checked.
    Samuria,
    Output from that command is at the end of my rather long original post.
    I will take any and all suggestions at this point. I will not say 'that can't be it, because it worked in Lubuntu' because I've tried everything obvious, so it must be something non-obvious.




    Code:
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    PS C:\Windows\system32> ipconfig /flushdns
    
    Windows IP Configuration
    
    Successfully flushed the DNS Resolver Cache.
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.25: Destination host unreachable.
    Request timed out.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
    PS C:\Windows\system32>
    PS C:\Windows\system32> nbtstat -RR
        The NetBIOS names registered by this computer have been refreshed.
    
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    PS C:\Windows\system32>
    PS C:\Windows\system32> netsh int ip reset
    Resetting Compartment Forwarding, OK!
    Resetting Compartment, OK!
    Resetting Control Protocol, OK!
    Resetting Echo Sequence Request, OK!
    Resetting Global, OK!
    Resetting Interface, OK!
    Resetting Anycast Address, OK!
    Resetting Multicast Address, OK!
    Resetting Unicast Address, OK!
    Resetting Neighbor, OK!
    Resetting Path, OK!
    Resetting Potential, OK!
    Resetting Prefix Policy, OK!
    Resetting Proxy Neighbor, OK!
    Resetting Route, OK!
    Resetting Site Prefix, OK!
    Resetting Subinterface, OK!
    Resetting Wakeup Pattern, OK!
    Resetting Resolve Neighbor, OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , failed.
    Access is denied.
    
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Resetting , OK!
    Restart the computer to complete this action.
    
    PS C:\Windows\system32>
    
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    PS C:\Windows\system32>
    PS C:\Windows\system32> netstat -a
    
    Active Connections
    
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:135            Rayquaza:0             LISTENING
      TCP    0.0.0.0:445            Rayquaza:0             LISTENING
      TCP    0.0.0.0:5040           Rayquaza:0             LISTENING
      TCP    0.0.0.0:49664          Rayquaza:0             LISTENING
      TCP    0.0.0.0:49665          Rayquaza:0             LISTENING
      TCP    0.0.0.0:49666          Rayquaza:0             LISTENING
      TCP    0.0.0.0:49667          Rayquaza:0             LISTENING
      TCP    0.0.0.0:49668          Rayquaza:0             LISTENING
      TCP    0.0.0.0:49669          Rayquaza:0             LISTENING
      TCP    169.254.94.41:139      Rayquaza:0             LISTENING
      TCP    [::]:135               Rayquaza:0             LISTENING
      TCP    [::]:445               Rayquaza:0             LISTENING
      TCP    [::]:49664             Rayquaza:0             LISTENING
      TCP    [::]:49665             Rayquaza:0             LISTENING
      TCP    [::]:49666             Rayquaza:0             LISTENING
      TCP    [::]:49667             Rayquaza:0             LISTENING
      TCP    [::]:49668             Rayquaza:0             LISTENING
      TCP    [::]:49669             Rayquaza:0             LISTENING
      UDP    0.0.0.0:500            *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:4500           *:*
      UDP    0.0.0.0:5050           *:*
      UDP    0.0.0.0:5353           *:*
      UDP    0.0.0.0:5355           *:*
      UDP    0.0.0.0:61358          *:*
      UDP    127.0.0.1:1900         *:*
      UDP    127.0.0.1:53877        *:*
      UDP    127.0.0.1:61357        *:*
      UDP    169.254.94.41:137      *:*
      UDP    169.254.94.41:138      *:*
      UDP    169.254.94.41:1900     *:*
      UDP    169.254.94.41:61356    *:*
      UDP    [::]:500               *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:4500              *:*
      UDP    [::]:5353              *:*
      UDP    [::]:5355              *:*
      UDP    [::]:61359             *:*
      UDP    [::1]:1900             *:*
      UDP    [::1]:61355            *:*
      UDP    [fe80::492c:ab27:8b8:5e29%8]:1900  *:*
      UDP    [fe80::492c:ab27:8b8:5e29%8]:61354  *:*
    PS C:\Windows\system32>
    PS C:\Windows\system32> ipconfig
    
    Windows IP Configuration
    
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . :
       Link-local IPv6 Address . . . . . : fe80::492c:ab27:8b8:5e29%8
       Autoconfiguration IPv4 Address. . : 169.254.94.41
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
    PS C:\Windows\system32>
    (At this point I set the IP address to 192.168.1.25 again)
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    PS C:\Windows\system32>
    PS C:\Windows\system32> netsh winsock reset
    
    Sucessfully reset the Winsock Catalog.
    You must restart the computer in order to complete the reset.
    
    PS C:\Windows\system32>
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    PS C:\Windows\system32> ping 192.168.1.1
    
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    Reply from 192.168.1.25: Destination host unreachable.
    
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    PS C:\Windows\system32>
    Last edited by Brink; 09 Oct 2018 at 17:27. Reason: code box
      My Computer

  7. Samuria's Avatar
    Posts : 6,070
    windows 10
       #7

    I wanted ipconfig /all from it with wireless working to see correct settings at the momnet your getting a 169 ip which means its not connecting to the dhcp
      My Computer


  8. Posts : 6
    Windows 10
    Thread Starter
       #8

    Ah, sorry. Result follows.
    I should add that my router is set up as:
    192.168.1.1 = the router itself
    192.168.1.2 ... 99 = configured (provisioned) addresses
    192.168.1.100 ... 199 = DHCP generated addresses
    192.168.1.250 = a Nas4Free server

    If I let the Ethernet follow DHCP, the result is:
    Code:
    PS C:\Windows\system32> ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : Rayquaza
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    
    Wireless LAN adapter Local Area Connection* 9:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
       Physical Address. . . . . . . . . : 52-3E-AA-3E-52-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Wireless LAN adapter Local Area Connection* 10:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
       Physical Address. . . . . . . . . : 50-3E-AA-3E-52-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 30-9C-23-99-C7-66
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::492c:ab27:8b8:5e29%8(Preferred)
       Autoconfiguration IPv4 Address. . : 169.254.94.41(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 271621155
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-4A-51-12-30-9C-23-99-C7-66
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Wireless LAN adapter Wi-Fi:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : TP-LINK Wireless USB Adapter
       Physical Address. . . . . . . . . : 50-3E-AA-3E-52-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::99fc:e63b:c79b:de9a%13(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.109(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : October 9, 2018 6:13:33 PM
       Lease Expires . . . . . . . . . . : October 10, 2018 6:13:33 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 407912106
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-4A-51-12-30-9C-23-99-C7-66
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    PS C:\Windows\system32>
    And if I configure an address, as I do for my other computers, the result is
    Code:
    PS C:\Windows\system32> ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : Rayquaza
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    
    Wireless LAN adapter Local Area Connection* 9:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
       Physical Address. . . . . . . . . : 52-3E-AA-3E-52-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Wireless LAN adapter Local Area Connection* 10:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
       Physical Address. . . . . . . . . : 50-3E-AA-3E-52-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 30-9C-23-99-C7-66
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::492c:ab27:8b8:5e29%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.25(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 271621155
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-4A-51-12-30-9C-23-99-C7-66
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Wireless LAN adapter Wi-Fi:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : TP-LINK Wireless USB Adapter
       Physical Address. . . . . . . . . : 50-3E-AA-3E-52-1C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::99fc:e63b:c79b:de9a%13(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.109(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : October 9, 2018 6:13:33 PM
       Lease Expires . . . . . . . . . . : October 10, 2018 6:13:32 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DHCPv6 IAID . . . . . . . . . . . : 407912106
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-4A-51-12-30-9C-23-99-C7-66
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    PS C:\Windows\system32>
      My Computer

  9. Samuria's Avatar
    Posts : 6,070
    windows 10
       #9

    Its not getting an ip from dhcp so its either a bad cable , bad router port , dead network port or router has mac filtering set
      My Computer


  10. Posts : 6
    Windows 10
    Thread Starter
       #10

    Your logic is on-point, for sure. I promised I wouldn't say "but it works in Linux", so I won't. I will try switching around all those elements again. I did just think of something; sometimes motherboards come with driver discs, and I don't think I installed anything for this one. I should root around in the box and see if there is one for mine. It would be weird if Windows 10 was unable to tell me if there was a driver missing, but who knows, perhaps it needs an extra driver layer or something. Troubleshooter didn't complain about anything missing, though.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:57.
Find Us




Windows 10 Forums