|< Day Day Up >|
Although the flashy improvements in
DNS added a number of changes and improvements. We discuss these in detail in Chapter 6, but a few are worth noting here for an overview:
Another improvement in DNS has been the collective knowledge of how it works with AD. Take advantage of Microsoft's
The popularity of consumers having networks in their home to connect multiple computers to the Internet has prompted Microsoft to develop features in the operating system to address their needs. This section describes some of those new features.
The network bridge feature really has its benefit in the home network environment. It allows you to "bridge" multiple network adapters, such as between a public network and a private network, or between a wireless adapter, an Ethernet adapter, and a dial-up adapter. The network bridge allows these adapters to communicate with each other without requiring the
Figure 1.21. Network Bridge is listed in Network Connections window.
Device Driver Enhancements
This is another improvement for home networking, removing legacy drivers that are no longer used or supported and adding or improving drivers in the following areas:
Remote Desktop Client and Resource Redirection
In answering customer support calls at HP, and in speaking engagements at conferences, I hear Administrators frequently comment that Windows 2000's Terminal Services (Administration mode) is the best tool Microsoft offers. It allows remote access to servers
In Windows 2000, you must install the TS client manually by building floppy disks with the Terminal Services Server Manager or by running
The Remote Desktop feature
Chapter 15, "Terminal Services for Windows Server 2003," contains more
Internet Authentication Service (IAS)
In addition to a new MMC snap-in, IAS has several new features. Two important features are noted here.
IAS and Radius Client
In Windows 2000, you can use an IAS server only as a Radius server, configured to perform access request authentication against the domain. In Windows Server 2003, you can configure an IAS server as a Radius Proxy that either authenticates the remote request or forwards the request to another Radius server.
IAS and Cross-Forest Authentication
You use cross-forest authentication to authenticate the user account when two AD forests are connected with a two-way, cross-forest trust. We discuss these trusts in the "Security" section of this chapter.
New Features in RRAS
IPSec over NAT
VPN clients behind a NAT (Network Address Translation) can now establish IPSec (IP Security) or Level 2 Tunnel Protocol (L2TP) tunnels to a Windows 2003 server. This was not available in Windows 2000. You can use this feature to make a connection to the company's internal network when one server is in the company's DeMilitarized Zone (DMZ), a branch office, or perhaps a client in a home network that shares a single IP address behind a NAT.
Broadcast Name Resolution
Also known as the NetBT Gateway, this feature provides TCP/IP name resolution for RAS (Remote Access Service) clients where no WINS (Windows Internet Naming Service) or DNS servers are available. This is similar to the WINS proxy and is shown in Figure 1.22. This is advantageous for small networks in which a DNS or WINS server is not in place.
Figure 1.22. Configuring the NetBT Gateway in the RRAS snap-in.
When the RAS server receives a request to resolve a name to an IP address, and it does not have that information in its NetBIOS name cache, it
If the NetBIOS over TCP / IP option is disabled on the RAS server, Broadcast Name Resolution will fail.
Broadcast Name Resolution is enabled by default, but you can disable or
This option is controlled by the Registry key EnableNetbtBcastFwd :
HKEY_LOCAL_MACHINE\CurrentControlSet\Services\RemoteAccess\ Parameters\Ip\ Name: EnableNetbtBcastFwd Type: REG_DWORD Data: 0 (disabled) 1 (enabled)
RRAS Firewall and NAT Integration
This feature enables you to integrate a firewall with a RRAS NAT function. It provides the Administrator a built-in firewall in RRAS. I have used this firewall for my home network, and while it isn't as flashy as some third-party applications, and it doesn't have logging or reporting features, it works quite well.
Enable RAS Interface as a NAT Private Interface
This feature allows a user, as a RAS client, to access the Internet via a server that is used for both NAT access to the Internet and dial-in access to his or her corporate network. Previously, you could not use this server for both.
Support for IPv6
Windows Server 2003 supports the IPv6 protocol, which may someday replace the existing IPv4 standard TCP/IP. IPv6 provides for 128-bit addresses, or more than 3.4 x 10 38 .
Removal of Legacy Networking Protocols
In Microsoft's effort to increase security, Windows Server 2003 has eliminated inclusion of and support for some legacy protocols. These include
Addition of New Protocols
HTTP.sys is a kernel mode driver that supports client-side and server-side APIs, although client-side APIs are disabled in the Windows Server 2003 implementation. Some server applications already take advantage of HTTP.sys, including IIS (Internet Information Services) v6.0, SQL's
Internet Group Management Protocol (IGMP) v3
Windows Server 2003 supports IGMP (Internet Group Management Protocol) v3 (currently an Internet draft). Some of IGMP v3's features include
Other Enhancements and Changes
Other networking enhancements include improvements for wireless LAN security, TCP/UDP (User Datagram Protocol) port ownership, removal of support for some modems and network adapters, and improvements in IPSec monitoring.
Secure Wireless LANS
Windows Server 2003 provides security and performance improvements for wireless LANs, such as automatic key management and user authentication and authorization prior to LAN access. It will also provide access control for Ethernet networks when wired Ethernet is used in public locations.
TCP/UDP Port Ownership
A new NETSTAT option displays the process that owns the (TCP/UDP) port. An Administrator can use this feature for configuring secure servers, security
Modems and Network Adapters No Longer Supported
Microsoft has dropped support for a number of modems and network adapters in Windows Server 2003, largely due to the respective
Details on the specific adapters that are not supported are available in Microsoft KB article 320892 "List of unsupported modems and network adapters in Windows Server 2003."
IPSec Monitoring Improvements
Windows Server 2003 includes the
|< Day Day Up >|