The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @nadineswagerman: Iemand mailde me dat een 13-jarig meisje mijn novelle had uitgekozen om te lezen/bespreken op school. Het boek bevat 9… 6 hours ago
    • RT @jilles_com: Afgelopen 10 dagen hebben we door NL gereisd, elke dag een nieuw hotel en op heel veel locaties gegeten. In 60% van de geva… 6 hours ago
    • RT @FTM_nl: Sywert van Lienden plaatste bewust een serie tweets om het ministerie onder druk te zetten om de omstreden mondkapjesdeal met h… 6 hours ago
    • RT @ArmsControlWonk: China just used a rocket to put a space plane in orbit and the space plane glided back to earth. Orbital bombardment i… 6 hours ago
    • RT @shossontwits: O jee. Nu dit weer. 6 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,482 other followers

“net view” “System error 1231 has occurred.” “Windows 10”

Posted by jpluimers on 2020/11/09

On my research list: none of my Windows 10 PC’s in WORKGROUP can see that other machines exist, but they can connect to each other.

C:\>net view
System error 1231 has occurred.c

C:\>net view
System error 6118 has occurred.

On Windows 8.1 and 7 (I know: both beyond end-of-support) can see both Windows 8.1/7 machines and Windows 10 machines:

C:\>net view
Server Name          Remark
The command completed successfully.

It is unclear on which Windows 10 release this started failing. I think it is around 1803 (April 2018 Update) or 1709 (Fall Creators Update). It fails despite all settings indicating sharing and discovery are enabled:

Things tried that failed:

Start service WebClient

Tried from an administrative command prompt, then waited a minute:

C:\net start WebClient
The WebClient service is starting.
The WebClient service was started successfully.


Via: [WayBack] System error 1231 has occurred – Microsoft Community

Ensure system names are uppercase

The system names were already in uppercase.

Via: [WayBack] Win10 10586 – FOUND FIX for system error 1231 bug ( network shares – Microsoft Community


Note: do not re-enable SMBv1 as it is inherently insecure!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: