Windows 10: Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS

GHacks · Apr 23, 2022

Microsoft's Windows operating system supports several multicast name resolution protocols, including NetBIOS and LLMNR. The state of the art protocol that is widely used today is mDNS, while the protocols NetBIOS and LLMNR are not widely used anymore.

In Aligning on mDNS: ramping down NetBIOS name resolution and LLMNR, Microsoft informs Windows system administrators that it plans to disable the old protocols in future versions of Windows to improve device security and decrease the load on the networks they use.

Microsoft is aware that there are still scenarios and "real-world deployments" in which these protocols are used, but the company is convinced that disabling the protocols by default is the right direction to take.

The company has not started the process of disabling LLMNR by default yet, but it has started the process for NetBIOS.

The NetBIOS protocol is already turned off by default on cellular devices according to Microsoft. In the latest Windows Developer and Beta Insider builds, NetBIOS is in learning mode. Learning mode means that NetBIOS is used as a fallback if mDNS and LLMNR queries fail.

The change may lead to connectivity issues in some cases. Administrators may modify a Group Policy or a Registry value to change the behavior of the protocol.

Note: the Group Policy Editor is only available on Professional and Enterprise editions of Windows. Home edition administrators may modify the behavior in the Registry.

Changing NetBIOS in the Group Policy Editor

Use the keyboard shortcut Windows-R to open the Run box on the system.

Type gpedit.msc and hit Enter; this should load the Group Policy Editor.

Navigate to Computer Configuration > Administrative Templates > Network > DNS Client.

Double-click on the Configure NetBIOS policy.

Set the policy to Enabled.

Use the menu that is provided "Configure NetBIOS options" to switch to one of the supported options:

Allow NetBIOS name resolution -- Enables full NetBIOS support.

Disable NetBIOS name resolution -- Turns off NetBIOS support on the device.

Disable NetBIOS name resolution on public networks -- Keeps NetBIOS enabled on private networks, but disables it on public networks.

NetBIOS learning mode -- NetBIOS is only used as a fallback if mDNS and LLMNR queries fail.

Select OK to save the new policy setting.

Changing NetBIOS in the Windows Registry

The same options are also available in the Windows Registry.

Use the keyboard shortcut Windows-R to open the run box.

Type regedit.exe and hit the Enter-key.

Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters in the Registry Editor.

Right-click on Parameters and select New > Dword (32-bit) Value.

Name the value EnableNetbios.

Double-click on the new Dword and set it to one of the following values:

0 -- Disabled.

1 -- Allowed.

2 -- Disabled on public networks.

3 -- Learning Mode.

Close the Registry Editor after you have made the change.

Closing Words

LLMNR has not been touched yet, but Microsoft plans to make similar changes to this protocol in future builds and versions of the Windows operating system.

Now You: do you use NetBIOS or LLMNR? (via Deskmodder)

Thank you for being a Ghacks reader. The post Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS appeared first on gHacks Technology News.

read more...

Brink · Apr 23, 2022

Documenting the Web together with MDN Web Docs

Today, we’re excited to share some big news for developers around the world wide web: We’re committing our resources towards making MDN Web Docs the best place to go for web API reference. To kick things off, today we started redirecting over 7,700 MSDN pages to corresponding topics in the MDN web docs library powered by Mozilla.

In conjunction with similar commitments from Mozilla, Google, the W3C, and Samsung, we’re teaming up to make MDN Web Docs the best place for web developers to learn and share information about building for the open web.

MDN is a core part of Mozilla’s overarching mission: to ensure the Internet is a global public resource, open and accessible to all. We believe providing web developers the best possible information will enable them to deliver great web experiences that adhere to established standards and work across platforms and devices. We are excited to have Microsoft, Google, The W3C, and Samsung on board as we continue on our journey to make MDN the premiere resource for developers.

— Ali Spivak, Head of Developer Ecosystem at Mozilla
Representatives from each of these organizations will also be serving on the MDN Product Advisory Board, a committee dedicated to making MDN your definitive place for useful, unbiased, browser-agnostic documentation for current and emerging standards-based web technologies. The MDN Product Advisory Board is also looking for active individuals from the web community to serve on the board. If you’re interested, find more details on MDN web docs.

Web docs should just work for everyone

Redirecting our API reference library to MDN is the next step towards consolidating our compatibility info in the same place you probably already frequent for general web documentation. Earlier this year, we began the effort to backfill the MDN browser Compatibility tables with a column representing the Microsoft Edge browser.

Over 5000 MDN edits later, the entire web API surface of Microsoft Edge (as of the 10/2017 Windows 10 Fall Creators Update, Build 16299) is now documented on MDN, and will continue to be kept up-to-date with each new release of Windows and our EdgeHTML browser engine.

Example of a Browser compatibility table on MDN Web Docs

One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering.

Just like with end users, we think it’s well overdue for developers to have a simpler view of web standards documentation. Developers shouldn’t have to chase down API documentation across standards bodies, browser vendors, and third parties—there should be a single, canonical source which is community-maintained and supported by all major vendors.

For these reasons we’re all-in on making MDN the home of web standards documentation. Not only is MDN a veritable encyclopedia and thriving community of all things web development, it’s also an institution in itself–a living monument to our collective history—as web developers and enthusiasts, web standards advocates, and browser engineers–of developing the web forward.

Documenting the web forward

MDN was founded over 10 years ago in 2005 as the Mozilla Developer Center and later become known as the Mozilla Developer Network. Just as the Mozilla Organization was founded out of Netscape, the Mozilla Developer Center grew from the original Netscape Navigator browser docs.

Similarly, the Internet Explorer Developer Center was first published online from the Microsoft Developer Network (MSDN) several years before that in the late 90s to help introduce and showcase Dynamic HTML (“DHTML”), Microsoft’s precursor to the modern DOM and CSS object model.

Microsoft Internet Explorer Developer Center on MSDN Online, circa 2000. Courtesy of the Internet Archive Wayback Machine

Fast forward to the modern web platform of today. The competing Netscape and Internet Explorer browsers from the bygone era of the early web are now subjects of tech archaeology, not site compatibility testing. From the final releases of IE culminating with the birth of Microsoft Edge, we replaced earlier Microsoft technologies with emerging industry standards–the modern DOM and ECMAScript standards for DHTML and VBScript, HTML5 for ActiveX, a common browser extension model for Browser Helper Objects (“BHOs”).

Through all this change, MDN has grown up alongside the web, and today has over 34,500 documents, 6 million monthly users and 20,500 contributors. From its initial Netscape product docs, the breadth and depth of MDN’s content has radically expanded to encompass the state of the art of modern web development—so much so that recently the site was restructured and rebranded to reflect MDN’s commitment to being a browser-neutral community resource. We are excited to join Mozilla, Google, The W3C, and Samsung in making MDN our home for web standards documentation and dedicated to helping it grow even further to meet your needs.

We will continue to maintain Microsoft- and Windows-focused documentation on Microsoft Docs (docs.microsoft.com/microsoft-edge), including Windows-specific test guidance, information on the Edge DevTools, and upcoming details about Progressive Web Apps in the Windows Store. And you’ll still find the latest Microsoft Edge status, changelogs, and news at our Microsoft Edge Developer site (dev.microsoftedge.com).

Please join us in supporting and contributing to MDN web docs! We’re all building this Web together; let’s document our hard work!

— Erika Doyle Navara, Senior Dev Writer
Click to expand...

Source: Documenting the Web together - Microsoft Edge Dev Blog

Martin 520 · Apr 23, 2022

Ported number doesn't show up as SIM's MDN

Thanks for your suggestion JG2yang1, but since I posted this question back in February my network provider firstly suggested they try a network refresh (which didn't change anything) and then a replacement SIM. With that new SIM, the MDN setting simply
disappeared. The phone no longer indicates any such setting as Settings>About>More Info>MDN: or
(phone)>Settings>My Number Is... I also learned that I am not the only Lumia owner on that network (EE in UK) who has experienced this issue.

Do you know the anwer to my original question: Is it the case that Windows Phone owners have no way to edit the displayed MDN?

Brink · Apr 23, 2022

Microsoft Edge Chakra documentation is joining MDN web docs

Last fall, along with other browser vendors and web platform stakeholders, the Edge platform (EdgeHTML) team adopted MDN web docs as our official web API reference library. In the process, we redirected over 7700 MSDN pages for HTML, CSS, SVG and DOM APIs to corresponding reference content on MDN and joined the community in helping maintain it, including making over 5000 edits to the browser compatibility tables to reflect the latest Edge API surface.

Today the Microsoft Edge JavaScript engine, Chakra, joins the community-wide effort to make MDN web docs the web’s one-stop, premiere development reference, starting by redirecting all 500+ pages of Microsoft’s JavaScript API reference from docs.microsoft.com to their MDN counterparts and porting our legacy JS extensions reference for historical and servicing purposes.

We want to thank our community for enthusiastically embracing MDN web docs, and special kudos to everyone who helps to improve the docs, edit by edit. In the previous year alone, you helped the MDN web docs community grow monthly users by over 50%! Let’s keep documenting the web forward together.

– Erika Doyle Navara, MDN Product Advisory Board representative for Microsoft Edge
Click to expand...

Source: Chakra documentation is joining MDN web docs - Microsoft Edge Dev Blog

Windows 10: Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS

Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS

Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS

Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS

Microsoft starts to phase out NetBIOS and LLMNR to focus on mDNS - Similar Threads - Microsoft starts phase

out of focus

out of focus

Microsoft is phasing out VBScript in Windows to improve security

Start Screen out of focus

Microsoft to phase out Microsoft Store for Business and Education

Out of focus

Screen out of focus

Netbios

photo out of focus