Networking

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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/

    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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 MSFTNetIPAddress objects found by CIM query for instances of the ROOT/StandardCimv2/MSFTNetIPAddress class on the CIM server:
    SELECT * FROM MSFT_NetIPAddress WHERE ((IPAddress LIKE 'False')) AND ((InterfaceIndex = 3)) AND ((AddressFamily =…

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

    We’ll send you updates on this idea

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  6. shutdown-i

    shutdown-i-now

    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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  7. Conservative RSS Profile assigns 2 CPUs when 1 RSS Queue is chosen

    Hi,

    I'm trying to understand how RSS works and while experimenting, I found out that when Convervative RSS Profile is used with 1 RSS Queue, Indirection Table stay the same, with two processors. Is that correct behavior?

    I'm asking, because when I choose other RSS Profile (for example Closest or ClosestStatic), number of the processors in IndirectionTable always match NumberOfRecaiveQueues.

    Is that mean that I have some bad version of Powershell/Windows/Drivers or is it correct??

    Can anyone help with that?

    I've used Set-NetAdapterRss cmdlet to set things up.

    Name : test0
    InterfaceDescription : Intel(R) Ethernet Converged Network Adapter X550-T2
    Enabled…

    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  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base