{"id":1393,"date":"2005-03-22T00:00:00","date_gmt":"2005-03-22T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/03\/22\/microsoft-shares-longhorn-networking-details\/"},"modified":"2021-12-30T11:39:17","modified_gmt":"2021-12-30T11:39:17","slug":"microsoft-shares-longhorn-networking-details","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/03\/22\/microsoft-shares-longhorn-networking-details\/","title":{"rendered":"Microsoft Shares Longhorn Networking Details"},"content":{"rendered":"<p>Microsoft execs go public with some of the enterprise and home networking changes that will debut with its next-gen Windows, Longhorn, due out in it&#8217;s client version in 2006 and server in 2007.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Delivery of a new, integrated IPv4\/IPv6 stack optimized for low-speed wireless and multi-gigabit networks.<\/p>\n<p>Built-in support for streaming audio\/video for entertainment and real-time communications tasks.<\/p>\n<p>Support for 802.11i wireless networking and 802.1x enterprise wireless scripting support. Microsoft also will deliver more troubleshooting tools for wireless users, officials said.<\/p>\n<p>Enhancements to Redmond&#8217;s support of core DHCP, RRAS\/VPN and RADIUS networking infrastructure services, including updates allowing them all to support fully IPv6. Microsoft will step up its IPSec support by providing server-to-server communications, domain isolation and network-access protection, execs said.<\/p>\n<p>http:\/\/www.microsoft-watch.com\/article2\/0,1995,1778408,00.asp<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1393","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1393","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1393"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1393\/revisions"}],"predecessor-version":[{"id":3880,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1393\/revisions\/3880"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1393"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1393"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1393"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}