As the launch of Microsoft's new operating system is just days away, we look at how to network PCs running the OS.
Windows Server 2008 R2 required
DirectAccess cannot function in a vacuum on a Windows 7 system. It requires a DirectAccess server to connect to, and a DirectAccess server means Windows Server 2008 R2.
The DirectAccess server must have two network interface cards: one connected to the public internet and one to provide access to the internal intranet resources. DirectAccess also requires at least two consecutive IPv4 addresses on the network interface card connected to the Internet.
The IPv6 translation technologies mentioned above (6to4, Teredo, and ISATAP) must be implemented on the DirectAccess server. Only a Public Key Infrastructure (PKI) environment can issue the necessary certificate for authentication and security, and a DNS server running on Windows Server 2008 or Windows Server 2008 R2 is required as well.
Users who experience problems connecting to DirectAccess can use the appropriate troubleshooting wizard to identify and resolve problems. Open the Network and Sharing Center and click on Troubleshoot problems; then select the Connection to a Workplace Using DirectAccess wizard to begin troubleshooting.
No matter how much network bandwidth an organisation has, it is safe to assume it is not unlimited. As more users access the network, or more users connect to bandwidth-intensive data like streaming audio and video, the network bandwidth is nibbled away until it is gone, forcing the router to queue data, which in turn slows down network communications.
Even without maxing out the internal network capacity, this type of queuing often takes place where the internal network meets the external network.
The internal network may be operating at 1GBps speeds, but the connection to the public internet might be 10MBps. Network packets from the internal network are queued by the router and transmitted on a first-come-first-serve basis as bandwidth becomes available on the external connection.
Not all network destinations are created equal, though, or treated equally. Requests to an application server used to process orders or data being sent to a mission-critical database should take precedence over traffic destined for Google or Facebook, say.
Administrators can configure Quality of Service (QoS) to prioritise the traffic and ensure that the high-priority traffic gets preferential treatment.
Windows will assign outgoing packets a Differentiated Services Code Point (DSCP) number that the router can use to determine the priority of the packets. As the network gets bogged down and packets are queued up, the default first-in-first-out functionality is overridden, and high-priority packets are sent out first.
The QoS functionality has been a part of previous versions of Windows, but it required that priority be assigned based on specific IP addresses and port numbers.
However, multiple websites may use the same IP address, and one website may have multiple IP addresses, making QoS difficult to utilise in some instances.
With Windows 7, Microsoft has added an ability to configure QoS based on URL. Administrators can ensure that traffic intended for intranet applications or important Web sites gets processed ahead of lower-priority traffic without having to configure the precise IP address and port of the destination sites.
URL-based QoS can also be used to intentionally downgrade the priority of nonbusiness-related sites such as ESPN or Facebook. Assigning these URLs a low priority will force those packets to be handled with even less urgency than normal traffic.
See all laptop review
See also: Windows 7 for business FAQ