Networking

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. DHCP server should check network connection and start servicing IPs after Event 1041

    In the scenario where the DHCP server is started before the network switch, event 1041 is triggered and even after network is operational no IP addresses are services unless the DHCP service is manually started.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/e3f48935-33a1-4a16-87c2-8989c9cf42b4/dhcp-failover-does-not-work-if-service-is-not-servicing?forum=winserveripamdhcpdns

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DHCP  ·  Flag idea as inappropriate…  ·  Admin →
  2. DnsServer Module cmdlets need a credential parameter

    It would be extremely useful if the cmdlets in the DnsServer module had the credential parameter. It's a lot easier to provide the credentials in a variable versus having to wrap the cmdlet in a script block every time you want to run it with different credentials.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add support for SNMPv3

    Is there any thought to updating the built in SNMP agent to support v3 in Windows server 2016, and not just deprecating the existing agent? Currently it seems there is no industry supported standard that is a replacement for SNMP, and until there is it should be added to Windows Server 2016

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add more BGP debug info

    There's no info about:
    - routes that ingress or egress through BGP really,
    - reasons of including/excluding BGP routes in/from main route table.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Misc  ·  Flag idea as inappropriate…  ·  Admin →
  5. DirectAccess should support multiple CA

    if the customer wants to upgrade or change the CA, he needs to bring in all the remote computers and do a GPO refresh on-premises; otherwise the moment the new CA is input into the configuration of DA server, the clients which are still using the old CA are kicked out of DA.

    we need a process for such transition, in case of an expired or compromised CA, to let the clients smoothly transition into the new CA without the requirement of them comping onsite for a GPO refresh. I would say enable the addition of Multiple CA rather than…

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Misc  ·  Flag idea as inappropriate…  ·  Admin →
  6. Fix DNS management console sorting bug

    Come on, after 8 years you have still not fixed this bug?
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/f1b686ad-824f-4c16-a66c-f9470a2dfa6d/2008-dns-ip-address-sorting-issue
    And NO, this is neither MMC nor regional settings problem, since DHCP management console sorts the same (IP addresses) values CORRECTLY.
    And NO, exporting to Excel is NOT an option!
    Come on grow up and get serious, even in Srv 2K and 2K3 it worked like charm!

    79 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
  7. DirectAccess better visibility of connection interface

    it is hard to tell which IPv6 interface DirectAccess is using to connect to the infrastructure. now you have to run netsh on httpstunnel and teredo and 6 to 4 to have some "educated guess" about which one is the one chosen for DA.

    we should be able to easily identify which interface (native or tunnel) is being utilized for DA communication on the client. the server GUI shows it already.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Misc  ·  Flag idea as inappropriate…  ·  Admin →
  8. reengineer the whole DHCP Server

    The MMC console based management of windows server is still unchanged since server 2003. These are the things that bother me:


    • Window size is not saved. have to maximize everytime the window is opened

    • Treemenu on the left is collapsed every time the window is opened

    • Menu window on the left is very narrow, have to extend it every time the window is opened

    • Cant edit IP address range exclutions (you have to delete and recreate every time)

    • Cant edit reservations IP address

    Following features would be great to have:


    • Right click on a client and copy MAC address (for…
    16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  DHCP  ·  Flag idea as inappropriate…  ·  Admin →
  9. Bring load balancing to windows server!

    Many modern HTTP applications are deployed in enterprises with 3rd party load balancers running in layer 7 mode. I have yet to find a solution which runs on windows. NLB is often difficult to deploy because of incompatibilities with switches/hypervisors (some improvement with IGMP multicast), and does not operate in layer 7.

    IIS AAR can do layer 7 but does not do high availability without combining with NLB

    35 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  10. Include SNMPv2/v3 / 64bit counters to Windows Server 2016

    As we all know all Windows Servers from 2000 to 2012 R2 only support 32bit counters for SNMP. Because of this if you run diagnostics on high speed interfaces / virtual interfaces like 1GbE, 10GbE, 40GbE, 100GbE counters will go over it's 32bit value and reset, causing MRTG graphs and other SNMP monitoring utilities to report false values. So my idea is that microsoft implements 64bit counters in SNMP implementation and finally adds support for 64bit SNMP.
    My 7 year old 3com switch supports 64bit SNMP counters but the latest Windows 2012 R2 does not.

    MRTG: http://oss.oetiker.ch/mrtg/

    16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Improve DNS logging options

    Allow us to put a filter in to log for specific lookups. We should be able to specify a list of names, a list of domains. We will at times have a misbehaving client or piece of malware, or we have an old domain or host and we'd like to know what's still using it. Being able to create a targeted log for these types of situations would often come in handy. As it is, we end up needing to run a network capture on all our domain controllers. The ability to use a Powershell or dnscmd command to add…

    19 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  DNS  ·  Flag idea as inappropriate…  ·  Admin →
  12. Give more control for NIC teaming

    In Active/Passive NIC teaming configuration, there could be more control for failback, that when active NIC fails and failover happens, the team did not failback to previously (default) active NIC for specified amount of time.

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support for Layer 2 sharing between physical and NVGRE networks

    Not supporting Layer 2 network between physical and NVGRE networks is one of the blockers for Network Virtualization adoption.

    10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Layer 2 & Ethernet  ·  Flag idea as inappropriate…  ·  Admin →
  14. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Layer 2 & Ethernet  ·  Flag idea as inappropriate…  ·  Admin →
  15. Introduce a "debug" mode to the TCP/IP stack

    As this would be reasonably impactful of performance on busy servers, it would have to be designed for debug situations only. The idea is that we have a log specifically for TCP/IP debugging. In it would be written things like TCP session establishment, connection resets, adapter events, tcp window size change events, offload status, rss events, route changes, and a big one, MTU negotiation/black hole router events.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  TCP/IP  ·  Flag idea as inappropriate…  ·  Admin →
  16. 4G

    Network

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Layer 2 & Ethernet  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  DHCP  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 = &#39;IPsec3&#39;
    
    DisplayName = &#39;IPsec3&#39;
    KeyModule = &#39;IKEv2&#39;
    Mode = &#39;Tunnel&#39;
    LocalAddress = &#39;192.168.1.0/24&#39;
    LocalTunnelEndpoint = &#39;192.168.1.204&#39;
    RemoteAddress
    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Firewall  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Managment tools  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Misc  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base