What does "unidentified network" mean (when otherwise, everything is fine) ?

This post is not really a plea for help. Everything works fine.

I have a situation (Win 10 pc) where the PC is connected to a network via
ethernet and everything works fine. But when you mouse over the "network"
icon in the systray, it says "unidentified network".

Why is that? What do I need to do on the other end of the connection to
make it an identified network?

--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/Mandela

Kenny McCormack wrote:
This post is not really a plea for help. Everything works fine.

I have a situation (Win 10 pc) where the PC is connected to a network via
ethernet and everything works fine. But when you mouse over the "network"
icon in the systray, it says "unidentified network".

Why is that? What do I need to do on the other end of the connection to
make it an identified network?


A quick search reveals an excessive amount of sites selling
"cha-cha-cha" fixes. Each site copying the recipe of the
other, and never bothering to mention a root cause.

This is the first site I could find that remained focused.

https://kb.vmware.com/s/article/2013496?lang=en_US

"This issue occurs if the winsock protocol in the
virtual machine is corrupted or not configured correctly.
This prevents your virtual machine from making
a network connection."

netsh winsock reset

netsh int ip reset resetlog.txt

And those commands are typically included in things
like the Network Troubleshooter in the
Control Panels : Troubleshooter icon.

As far as I know, the netsh commands are reasonably
consistent from one OS version to the next.

https://docs.microsoft.com/en-us/win...netsh-contexts

https://support.microsoft.com/en-us/...tshell-utility

Paul

Paul wrote in :

Kenny McCormack wrote:
This post is not really a plea for help. Everything works fine.

I have a situation (Win 10 pc) where the PC is connected to a network
via ethernet and everything works fine. But when you mouse over the
"network" icon in the systray, it says "unidentified network".

Why is that? What do I need to do on the other end of the connection
to make it an identified network?


A quick search reveals an excessive amount of sites selling
"cha-cha-cha" fixes. Each site copying the recipe of the
other, and never bothering to mention a root cause.

This is the first site I could find that remained focused.

https://kb.vmware.com/s/article/2013496?lang=en_US

"This issue occurs if the winsock protocol in the
virtual machine is corrupted or not configured correctly.
This prevents your virtual machine from making
a network connection."

netsh winsock reset

netsh int ip reset resetlog.txt

And those commands are typically included in things
like the Network Troubleshooter in the
Control Panels : Troubleshooter icon.

As far as I know, the netsh commands are reasonably
consistent from one OS version to the next.

https://docs.microsoft.com/en-us/win...g/technologies
/netsh/netsh-contexts

https://support.microsoft.com/en-us/...set-tcp-ip-by-
using-the-netshell-utility

Paul

ipconfig also has a lot of options for controlling your network.

In article ,
lonelydad wrote:
....
ipconfig also has a lot of options for controlling your network.

Note that none (i.e., neither) of the responses so far have any relevance
to the OP.

Please carry on...

--
Just for a change of pace, this sig is *not* an obscure reference to
comp.lang.c...

This idiotic troll didn't get the answer it wanted,
so it threw a hissy fit...

--
(Kenny McCormack) wrote:

Path: not-for-mail
From: (Kenny McCormack)
Newsgroups: alt.comp.os.windows-10
Subject: What does "unidentified network" mean (when otherwise, everything is fine) ?
Date: Mon, 27 May 2019 09:40:51 -0000 (UTC)
Organization: The official candy of the new Millennium
Message-ID:
References: 8
Injection-Date: Mon, 27 May 2019 09:40:51 -0000 (UTC)
Injection-Info: news.xmission.com; posting-host="shell.xmission.com:166.70.8.4"; logging-data="1216"; "
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: (Kenny McCormack)
X-Received-Bytes: 1253
X-Received-Body-CRC: 1766272233

In article ,
lonelydad wrote:
...
ipconfig also has a lot of options for controlling your network.

Note that none (i.e., neither) of the responses so far have any relevance
to the OP.

Please carry on...

--
Just for a change of pace, this sig is *not* an obscure reference to
comp.lang.c...

Kenny McCormack wrote:
In article ,
lonelydad wrote:
...
ipconfig also has a lot of options for controlling your network.

Note that none (i.e., neither) of the responses so far have any relevance
to the OP.

Please carry on...


All I've found so far, is a lot of "spray and wash" procedures.
The enthusiast sites can't just come out and name the reason,
and so they blast everything in sight.

A Superuser thread offers:

"An unidentified network just means that the gateway isn't
set on that computer for the current connection;

enter a valid one and the issue will be resolved."

Now, is that a partial DHCP failure or what ?

Paul

Kenny McCormack wrote:
This post is not really a plea for help. Everything works fine.

I have a situation (Win 10 pc) where the PC is connected to a network via
ethernet and everything works fine. But when you mouse over the "network"
icon in the systray, it says "unidentified network".

Why is that? What do I need to do on the other end of the connection to
make it an identified network?


It means that the setting of Public or Private for that network is
either not set or was lost. Settings Network & Internet Network
Status Change connection properties

Select Private or Public

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

"Jonathan N. Little" wrote:

Kenny McCormack wrote on 2019-05-26:
^^^^^^^^^^^^^
snip

snip

You didn't notice the OP's post was dated over a year ago?

VanguardLH wrote:
"Jonathan N. Little" wrote:

Kenny McCormack wrote on 2019-05-26:
^^^^^^^^^^^^^
snip

snip

You didn't notice the OP's post was dated over a year ago?


Naw, my sort got all screwed up when Eternal September when wacky
yesterday...

Anyway the solution was still correct.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com