Jaa

Ready for Windows Server 2008?

  • Artikkeli

Windows Server 2008 incorporates the completely rewritten TCP/IP stack we shipped in Windows Vista and since this is the first server release with the stack we'd like to ask our readers to load up Windows Server RC1 and see if your applications are ready.

The new features (compared to Windows Server 2003) that may pose potential compatibility issues include: removed filter hooks, receive window auto tuning, dual IP layer architecture for IPv6, compound TCP, ECN support, default strong host model, easier kernel mode programming, extensive protocol offload.

Windows Server 2008 is also the very first Microsoft server product to have the firewall ON by default . Third party applications that are not aware of this behavior may break. 

-- Ari and Katarzyna

Comments

  • Anonymous
    January 08, 2008
    Windows Server 2008 incorporates the completely rewritten TCP/IP stack we shipped in Windows Vista and

  • Anonymous
    February 06, 2008
    I wish MS would deliver the Scalable Networking Pack for Windows XP SP3. How come? They are all server features... However I believe you get all of it available in Vista's Networking Stack, so if you really want it on a client OS, there is an option.

  • Anonymous
    February 07, 2008
    The comment has been removed

  • Anonymous
    April 02, 2008
    The comment has been removed

  • Anonymous
    May 23, 2008
    Hi, I need to write an Intremediate Driver with IEEE 802.1Q/P support in NDIS 6.x/5.x. Does windows 2008 server supports these standards? or Do I need to implement the standard?. Is there any sample IM Driver with source available with above standards. By the way I'm just reading the standards now. Please provide me some suggestion or Thanks & Regards Satheesh (mp.satheeshbabu@hotmail.com)

  • Anonymous
    February 04, 2009
    As <a href=http://blogs.msdn.com/wndp/archive/2008/01/07/ready-for-windows-server-2008.aspx#7535490>anonymous</a> said, I also have a problem with Automatic metric on my Server 2008. It's 2009 now and this issue is not yet solved!

  • Anonymous
    September 16, 2010
    The comment has been removed