Networking

How can we improve the networking platform and management in Windows Server?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. RE-code the DFACS utility

    RE-code the released DHCP Failover Auto Config Sync (DFACS) utility. We were considering an implementation of it but scrapped the idea hearing of all the alleged scary issues in the comments e.g. memory consumption, deletion of scopes, issues with reservations, etc. The result of implementing the tool should mitigate config drift, not end up causing other larger issues!

    Please do update me if a new build fixing the reported issues.

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  DHCP  ·  Flag idea as inappropriate…  ·  Admin →
    • Fix the ping timeout bug that gives incorrect "reply timed out" messages in Server 2012r2 and Windows 10 for pings under 1000ms timeout

      Ping can take a timeout, if the timeout is set less than 1000ms then genuine replies start getting ignored as timed out failures.

      Does not affect Server 2003 or 2008.

      Does affect Server 2012 r2 and Windows 10

      Appears to be a problem in WinAPI / networking stack rather than .Net or ping.exe implementation - happens at ICMPSendEcho2Ex and ICMP6SendEcho2Ex layers at least.

      Documented in detail here: https://stackoverflow.com/questions/45528336/winapi-why-does-icmpsendecho2ex-report-false-timeouts-when-timeout-is-set-belo

      and here: http://web.archive.org/web/20150519002258/http://www.frameflow.com:80/ping-utility-flaw-in-windows-api-creating-false-timeouts/

      1 vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
      • Remove Network Location Awareness from Windows Server

        Remove Network Location Awareness from Windows Server, all it does is cause problems. There is no reason to include this service in Windows Server, servers have static network settings, people do not consistently move servers to different networks. Network Location Awareness service fails way to often on reboots to find the proper network it should connect to. It then assigns the incorrect Windows Firewall to the NIC. This services needs to be removed, or we need the ability to set a static location (Domain).

        3 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  Firewall  ·  Flag idea as inappropriate…  ·  Admin →
        • Windows Firewall does not always display the correct default Main Mode IPsec policy

          Bug:

          The Windows Firewall snap-in does not always show the default Main Mode IPsec policy, it shows whatever MM policy was last created or assigned.

          Expected Behavior:

          Even if there are multiple Main Mode policies (called Main Mode Crypto Sets internally), the policy with the name of '{E5A5D32A-4BCE-4e4d-B07F-4AB1BA7E5FE1}' should always be displayed as the default in the GUI because it is the default used by Windows for IPsec.

          Steps to Reproduce:

          *In the Windows Firewall snap-in you can see the current default IPsec Main Mode proposal set by going to Properties of the Windows Firewall > IPsec Settings tab >…

          6 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            2 comments  ·  Firewall  ·  Flag idea as inappropriate…  ·  Admin →
          • Cannot create IKEv2 tunnel mode IPsec rules in PowerShell, but IKEv1 works just fine

            Bug:

            When creating an IPsec rule which uses the IKEv2 keying module in PowerShell, an error is thrown, but it is not likely a PowerShell error, but an underlying bug in Windows.

            Expected Behavior:

            We should be able to manage IKEv2 IPsec rules however we wish, including creating tunnel mode IKEv2 rules without using RRAS.

            Steps To Reproduce:

            In PowerShell, the following code should work (notice the KeyModule):

            -------start---------
            $P1MachineCertOnly = New-NetIPsecPhase1AuthSet -Default <rest of command not shown>

            $IPsec3Tunnel = @{
            IPsecRuleName = 'IPsec3'
            DisplayName = 'IPsec3'
            KeyModule = 'IKEv2'
            Mode = 'Tunnel'
            LocalAddress = '192.168.1.0/24'
            LocalTunnelEndpoint = '192.168.1.204'
            RemoteAddress…

            5 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  Firewall  ·  Flag idea as inappropriate…  ·  Admin →
            • DnsServerResourceRecord does not support multi-string records

              RFC-4408 (section 3.1.3) https://tools.ietf.org/html/rfc4408#section-3.1.3 defines the use of multi-string records for SPF (DNS TXT records), however the Get- or Add- DNSServerResourceRecord commands do not support this. For the Get- the actual DNS record is truncated to 256 chars, and for the Add- it simply errors out with an invalid propery.

              Example of a valid DNS record (that can be configured by the DNS GUI)
              $RecordName = "spfrecord"
              $RecordText = "v=spf1 ip4:192.168.0.1 ip4:192.168.0.2 ip4:192.168.0.3 ip4:192.168.0.4 ip4:192.168.0.5 ip4:192.168.0.6 ip4:192.168.0.7 ip4:192.168.0.8 ip4:192.168.0.9 ip4:192.168.0.10 ip4:192.168.0.11 ip4:192.168.0.12 ip4:192.168.0.13 ip4:192.168.0.14 include:spf.protection.outlook.com mx -all"
              $Zone = "contoso.com"
              $Type = "TXT"
              $DNSServer = "DC1.contoso.com"
              Add-DnsServerResourceRecord -DescriptiveText $RecordText -Name…

              2 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  Managment tools  ·  Flag idea as inappropriate…  ·  Admin →
              • DNS recursion using wrong NS for delegated zone CNAME

                When Server 2016 DNS Server has a delgation within a primary zone, CNAME records in that delegation result in queries to the delgation's name servers, not forwarders / root hints.
                For example:

                Primary zone: one.example
                Delegation: foo.one.example, with nameserver ns.bar.com

                In that delegated zone, there exists a record:

                baz.foo.one.example IN CNAME other.two.example

                two.example's zone, hosted by ns.somethingelse.com, has a record:
                other.two.example IN A 1.2.3.4

                From a client pointed at the DNS server, query baz.foo.one.example.

                I would expect the server to query ns.bar.com for baz, receive a reply of other.two.example, and then query either two.example's nameserver, or use the default forwarders…

                9 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
                • Routing and RRAS

                  Routing and RRAS is Broken on Windows Server 2016.
                  I can''t dail up via pppoe.
                  It would be great, if this could be fixed.

                  1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    1 comment  ·  Misc  ·  Flag idea as inappropriate…  ·  Admin →
                  • Fix -WhatIf, -Verbose, and -ErrorAction support in the DnsServer PowerShell module

                    The new cmdlets for DNS policies in particular have inconsistent and downright broken support for -WhatIf and -Verbose.

                    Example:

                    Add-DnsServerClientSubnet -cn MyDC -Name 'Whatever' -IPv4Subnet 10.0.0.0/32

                    That works if you explicitly add -WhatIf. But if I make the call inside an advanced function that SupportsShouldProcess and call the outer function with -WhatIf, the preference will NOT carry over. In order to do that, I have to use -WhatIf:$WhatIfPreference.

                    The same is true with -Verbose, having to use -Verbose:$VerbosePreference because it won't inherit it.

                    This is true on the cmdlets for:
                    - Client Subnets
                    - Zone Scopes
                    - Query Reoslution Policies

                    5 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      2 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
                    • DHCP Failover ist not possible between different Languages.

                      Dear Microsoft,

                      it's not possible to Setup a DHCP Failover between two Server (w2k12 R2) with different languages in my case English and german.

                      The Error Code 20044 comes up because of the differenet naming of the user and/or vendor classes.

                      I think this should be fixed.

                      Kind regards,
                      Benedikt Ochs

                      1 vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  DHCP  ·  Flag idea as inappropriate…  ·  Admin →
                      • Broke RRAS

                        At the moment PPPoE is broken in Windows Server 2016 over RRAS.
                        It would be great if this could be solved.
                        Till yet we're using Windows Server 2012. But we would like to upgrade but can't 'cause RRAS is broken.

                        5 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          8 comments  ·  Misc  ·  Flag idea as inappropriate…  ·  Admin →
                        • get-netipconfiguration

                          Get-netipconfiguration throws exception if you have multiple default gateways configured for an interface.

                          PS C:\Users\Administrator> Get-NetIPConfiguration

                          Exception setting "NetProfile": "Cannot convert the "System.Object[]" value of type "System.Object[]" to type
                          "Microsoft.Management.Infrastructure.CimInstance"."
                          At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\NetTCPIP\NetIPConfiguration.psm1:201 char:17
                          + ... $IPConfig.NetProfile = Get-NetConnectionProfile -Interfac ...
                          + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          + CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
                          + FullyQualifiedErrorId : ExceptionWhenSetting

                          InterfaceAlias : Ethernet0
                          InterfaceIndex : 4
                          InterfaceDescription : Intel(R) 82574L Gigabit Network Connection
                          IPv4Address : 172.16.110.222
                          IPv6DefaultGateway :
                          IPv4DefaultGateway : {12.12.12.12, 172.16.110.2}
                          DNSServer : 172.16.110.100

                          2 votes
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            2 comments  ·  TCP/IP  ·  Flag idea as inappropriate…  ·  Admin →
                          • DNS: Application high availability

                            Hello,

                            On your site "What's new in DNS Server in Windows Server 2016" is written that there will be a new feature called "DNS Policies", which can be used for "Application high availability". But i can't find this feature, which allows me to redirect clients to the healthiest endpoint like a failover-cluster. I'm not looking for a loadbalancer.

                            Other People are looking too for this Feature and some documentation, when will it be available?

                            This feature would be great for applications like ADFS and so on.

                            "What's New" https://technet.microsoft.com/en-us/windows-server-docs/networking/dns/what-s-new-in-dns-server
                            Other person: https://social.technet.microsoft.com/Forums/office/en-US/84d3b0de-e427-4987-b498-6b053851e2dc/dns-policies-application-high-availability?forum=WinServerPreview

                            6 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              2 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
                            • Enable-NetLldpAgent not useful

                              The Enable-NetLldpAgent , in order to be useful in proper management of a network, should allow setting TLV subtypes.
                              Or...........Some options I would prefer:
                              set TLV 1 to ID subtype 5 (network address) instead of subtype 4 (MAC address)
                              set TLV 2 to ID subtype 5 (interface name) instead of 3 (MAC address)

                              include the optional TLV 5 system name

                              MAC address is easily obtained by other networking tools. Using this as the information for mandatory TLVs is redundant and useless.

                              4 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                1 comment  ·  Managment tools  ·  Flag idea as inappropriate…  ·  Admin →
                              • Provide useful parameters for Enable-NetLldpAgent

                                Enable-NetLldpAgent not useful

                                The Enable-NetLldpAgent , in order to be useful in proper management of a network, should allow setting TLV subtypes.
                                Or...........Some options I would prefer:
                                set TLV 1 to ID subtype 5 (network address) instead of subtype 4 (MAC address)
                                set TLV 2 to ID subtype 5 (interface name) instead of 3 (MAC address)

                                include the optional TLV 5 system name

                                MAC address is easily obtained by other networking tools. Using this as the information for mandatory TLVs is redundant and useless.

                                And include lldp driver and PS modules in every version of Windows. You can't build a…

                                2 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  1 comment  ·  Layer 2 & Ethernet  ·  Flag idea as inappropriate…  ·  Admin →
                                • Fix Remote-NetIPAddress to work inside try/catch

                                  Writing a script to provision a machine - we first remove the IPAddress (and any default gateway), But sometimes there is no address. That;s fine - we just try/catch and move on, liike this:

                                  Try {
                                  Remove-NetIPAddress -InterfaceIndex $IfIndex `
                                  -AddressFamily IPv4 `
                                  -Confirm $false
                                  }
                                  Catch {Write-Verbose 'No IPAddresses found'}

                                  But instead of the nice write-verbose message, we get a fatal error:
                                  Remove-NetIPAddress : No matching MSFT_NetIPAddress objects found by CIM query for instances of the ROOT/StandardCimv2/MSFT_NetIPAddress class on the CIM server:
                                  SELECT * FROM MSFT_NetIPAddress WHERE ((IPAddress LIKE 'False')) AND ((InterfaceIndex = 3)) AND ((AddressFamily = 2)). Verify…

                                  2 votes
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Make Direct Access to work also User based

                                    "Direct Access" which unfortunately only works for domain joined clients (I dont get it why u made this fantastic technology computer based and not also user based which would also work for non domain joined computers)

                                    Giving customers access to our fileshares via https would be easy then.
                                    Currently almost all products from Microsoft are ready to deploy to external users via https the only thing left is classic filesharing.

                                    I know u want customers to use ur cloud services, but there are also a lot of companys which could not use them for compliance reasons, so please dont forget…

                                    1 vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  DirectAccess  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Expose whether DNS Client Server Address assigned by DHCP or Static

                                      The Get-DNSClientServerAddress cmdlet does not provide information on whether or not the Server Addresses were assigned via DHCP or have been statically assigned.

                                      This is presumably because the information is not provided to WMI/CIM.

                                      This information is available by using NETSH, so it is available in the OS.

                                      This would allow some problems in the xDNSServerAddress resource in the xNetworking DSC resource module (in the Resource Kit) to be solved.

                                      For more information about the problem and why it is causing problems, please see this issue in the xNetworking resource module: https://github.com/PowerShell/xNetworking/issues/164

                                      7 votes
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        1 comment  ·  Managment tools  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Move the GlobalBlocklist to the ADS

                                        Everytime you set up a new DC with DNS (integrated DNS Zones) you have to remember to clear the GlobalBlocklist in the Registry (when using wpad and isatap). If you set up new DC everytime a new OS is live, you have to remember for this every ~ 3 years. Please move the GlobalBlocklist to a Paramter in the integrated zones, so that every DNS Server with this zone get a real "Global" Blocklist. Or, at least, make the Blocklist visible in the mmc. Would make the search for the misconfiguration a lot faster.

                                        2 votes
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Server 2016 wifi does not work

                                          In Windows Server 2016 RTM, like in the TP5, still Wifi does not work!
                                          I can enable the service, device is known in device manager and it also finds Wifi networks, but when i connect, after entering password, Explorer.exe crashes!

                                          6 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4
                                          • Don't see your idea?

                                          Networking

                                          Feedback and Knowledge Base