• unidentified network

    From Iain@21:1/5 to All on Fri Oct 25 11:31:34 2019
    Windows 10 build 1903
    can't connect to network.
    I've tried many different solutions found on the web but nothing works.
    Drivers are up to date.
    Anyone able to help me?
    Regards
    Iain

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Henry Law@21:1/5 to Iain on Fri Oct 25 17:11:10 2019
    I sent this as email first off ... stupid.

    On 25/10/2019 11:31, Iain wrote:
    Windows 10 build 1903
    can't connect to network.

    Meaning what, exactly? When you do whatever-it-is, what do you expect
    to see and what do you see?

    Do you have an IP address (use ipconfig to find out)? Can you ping
    anything (your router, for example, which unless you changed it is often 192.168.1.1)?

    I've tried many different solutions found on the web but nothing works.

    It would help us a little if you outlined at least some of the things
    you tried.

    Has it ever worked? Did you do anything just before it stopped working?
    (where "any" should, initially at least, be interpreted very widely).

    --
    Henry Law n e w s @ l a w s h o u s e . o r g
    Manchester, England

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adrian Caspersz@21:1/5 to Iain on Fri Oct 25 18:50:33 2019
    On 25/10/2019 11:31, Iain wrote:
    Windows 10 build 1903
    can't connect to network.
    I've tried many different solutions found on the web but nothing works. Drivers are up to date.
    Anyone able to help me?
    Regards
    Iain

    There is a comprehensive list of 'fixes' on the following page

    https://www.thewindowsclub.com/fix-unidentified-network-windows

    Start from top to bottom, tell us which tests you have tried

    Also,

    Is this cabled, or wifi?
    Do other devices connect OK?

    --
    Adrian C

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Iain@21:1/5 to Henry Law on Sat Oct 26 12:33:05 2019
    On 25/10/2019 17:11, Henry Law wrote:
    I sent this as email first off ... stupid.

    On 25/10/2019 11:31, Iain wrote:
    Windows 10 build 1903
    can't connect to network.

    Meaning what, exactly?  When you do whatever-it-is, what do you expect
    to see and what do you see?

    Do you have an IP address (use ipconfig to find out)?  Can you ping
    anything (your router, for example, which unless you changed it is often 192.168.1.1)?

    I've tried many different solutions found on the web but nothing works.

    It would help us a little if you outlined at least some of the things
    you tried.

    Has it ever worked?  Did you do anything just before it stopped working? (where "any" should, initially at least, be interpreted very widely).


    In Network Connections I expect to see the name of the network but
    instead I see "Unidentified Network"
    If I use Automatic connection ipconfig shows an address 169.254.187.76
    If I Manually enter an address ipconfig shows the correct address.

    I have followed the advice given in the site referenced by AdrianC.

    The computer was recently upgraded to Windows 10 Pro from Windows 7 Pro

    Iain

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Henry Law@21:1/5 to Iain on Sat Oct 26 12:59:40 2019
    On 26/10/2019 12:33, Iain wrote:
    In Network Connections I expect to see the name of the network but
    instead I see "Unidentified Network"
    I'm not a Windows man (any more) but I can see from various sources that
    that means essentially "Lights on but nobody home".

    If I use Automatic connection ipconfig shows an address  169.254.187.76
    It's not getting an address from DHCP then, because that's a "link
    local" address. Do you have another machine on the network which is
    using DHCP? Is it functioning correctly? I'm wondering if the DHCP
    component of your router is not working properly.

    If I Manually enter an address ipconfig shows the correct address.

    And when you have done that does networking work correctly? In other
    words can you ping your router?

    If we're chasing a bug in Windows (it does happen, I'm told ...) then
    I'm running out of suggestions. But if you have assigned a valid IP
    address on your local network you ought to be able to see other devices
    on that network.

    Any chance of running a tcpdump network trace from somewhere on the
    network? (If you don't know what that is, don't worry, but don't try it).

    --
    Henry Law n e w s @ l a w s h o u s e . o r g
    Manchester, England

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Iain@21:1/5 to Adrian Caspersz on Sat Oct 26 11:58:53 2019
    On 25/10/2019 18:50, Adrian Caspersz wrote:
    On 25/10/2019 11:31, Iain wrote:
    Windows 10 build 1903
    can't connect to network.
    I've tried many different solutions found on the web but nothing works.
    Drivers are up to date.
    Anyone able to help me?
    Regards
    Iain

    There is a comprehensive list of 'fixes' on the following page

    https://www.thewindowsclub.com/fix-unidentified-network-windows

    Start from top to bottom, tell us which tests you have tried

    Also,

    Is this cabled, or wifi?
    Do other devices connect OK?


    I've gone through that list to no avail. It is a cabled connection. 2
    other Win 10 computers and 1 Linux computer connect OK.
    I'm getting really frustated now.

    Iain

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Iain@21:1/5 to Henry Law on Sat Oct 26 13:38:00 2019
    On 26/10/2019 12:59, Henry Law wrote:
    On 26/10/2019 12:33, Iain wrote:
    In Network Connections I expect to see the name of the network but
    instead I see "Unidentified Network"
    I'm not a Windows man (any more) but I can see from various sources that
    that means essentially "Lights on but nobody home".

    If I use Automatic connection ipconfig shows an address  169.254.187.76
    It's not getting an address from DHCP then, because that's a "link
    local" address.  Do you have another machine on the network which is
    using DHCP?  Is it functioning correctly?  I'm wondering if the DHCP component of your router is not working properly.

    If I Manually enter an address ipconfig shows the correct address.

    And when you have done that does networking work correctly?  In other
    words can you ping your router?

    If we're chasing a bug in Windows (it does happen, I'm told ...) then
    I'm running out of suggestions.  But if you have assigned a valid IP
    address on your local network you ought to be able to see other devices
    on that network.

    Any chance of running a tcpdump network trace from somewhere on the network?  (If you don't know what that is, don't worry, but don't try it).

    Other machines use DHCP with no problem.
    No matter what address I enter I get the same result.
    tcpdump is beyond my ken at the moment.

    Iain

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniel James@21:1/5 to Iain on Sat Oct 26 18:55:15 2019
    In article <qouiu5$avh$1@dont-email.me>, Iain wrote:
    Windows 10 build 1903
    can't connect to network.

    Windows does that, sometimes. That's one of the reasons I don't use it
    any more.

    I've tried many different solutions found on the web but nothing
    works.
    Drivers are up to date.
    Anyone able to help me?

    I don't use Windows 10 ... but I noticed that on Windows 7 the network connection could sometimes turn into an "Unidentified network" if the
    wind changed ... or you looked at it funny ... or there was a day in the
    week ...

    Sometimes that could be traced back to something that had actually
    changed (like when the router failed, and the replacement router with
    exactly the same settings was seen as a different network), sometimes
    not.

    The network "troubleshooter" in Windows can sometimes fix these things
    .. I think it basically turns off networking and goes through the DHCP
    setup again and if you're lucky it configures things correctly. Other
    times Windows may need to be told that there is a "new" network and
    whether it is a home, office, or public network (in other words, whether
    to allow peer access on that network connection). Until you answer that question Windows won't play (for fear of peer-peer connecting to summat
    it shouldn't).

    On occasions I've just turned the machine off in disgust, and it has
    worked the next day.

    Sorry if that's not much help.

    --
    Cheers,
    Daniel.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From grinch@21:1/5 to Iain on Sat Oct 26 21:13:18 2019
    On 26/10/2019 11:58, Iain wrote:
    On 25/10/2019 18:50, Adrian Caspersz wrote:
    On 25/10/2019 11:31, Iain wrote:
    Windows 10 build 1903
    can't connect to network.
    I've tried many different solutions found on the web but nothing works.
    Drivers are up to date.
    Anyone able to help me?
    Regards
    Iain

    There is a comprehensive list of 'fixes' on the following page

    https://www.thewindowsclub.com/fix-unidentified-network-windows

    Start from top to bottom, tell us which tests you have tried

    Also,

    Is this cabled, or wifi?
    Do other devices connect OK?


    I've gone through that list to no avail. It is a cabled connection. 2
    other Win 10 computers and 1 Linux computer connect OK.
    I'm getting really frustated now.

    Iain

    Does the dhcp serving device think it run out of IP address to allocate,
    ? Flush its memory or reboot/power-cycle it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adrian Caspersz@21:1/5 to grinch on Mon Oct 28 16:41:15 2019
    On 26/10/2019 21:13, grinch wrote:
    On 26/10/2019 11:58, Iain wrote:

    I've gone through that list to no avail. It is a cabled connection. 2
    other Win 10 computers and 1 Linux computer connect OK.
    I'm getting really frustated now.

    Iain

    Does the dhcp serving device think it run out of IP address to allocate,
    ? Flush its memory or reboot/power-cycle it.

    Hmmm... rebooting/resetting the router is a good step before anything else.

    Find out what addresses the router is allocating and statically assign
    one in the same subnet range instead of using DHCP.

    If no joy connecting, then sling a cable directly between two items and
    see if they can at least ping each other (disable firewalls for the
    test). They should each negotiate an address from 169.254.*.* and at
    least be able to ping each other. Or try giving each an address in the
    same subnet range.

    Could be broken hardware, or dodgy cable. Booting from a linux live CD
    might be able to exonerate or blame windows 10 configuration.

    Could be a lot of "could be's".

    If patience too short, just buy a USB to ethernet adaptor or use wireless.

    --
    Adrian C

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anthony R. Gold@21:1/5 to Iain on Wed Oct 30 21:56:38 2019
    On Fri, 25 Oct 2019 11:31:34 +0100, Iain <iain.gordon46@gmail.com> wrote:

    Windows 10 build 1903
    can't connect to network.
    I've tried many different solutions found on the web but nothing works. Drivers are up to date.
    Anyone able to help me?
    Regards
    Iain

    Do you know what channel your router or AP is using? If it's above Channel
    11 in the 2.4 GHz band your Windows 10 computer will have difficulty finding the signal if the regionality of its WiFi is set is some USA default.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)