Advanced Networking

Microsoft Windows® XP New Hire

Microsoft Confidential – Provided Under NDA

© 2004 Microsoft Corporation. All rights reserved.

Microsoft, Internet Explorer, and Windows are either registered trademarks or

trademarks of Microsoft Corporation in the United States and/or other
countries.

The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.

THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND

TRAINING PURPOSES ONLY AND ARE PROVIDED "AS IS" WITHOUT
WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-
INFRINGEMENT.

No part of the text or software included in this training package may be

reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying, recording, or any information storage and
retrieval system, without permission from Microsoft®. Because Microsoft must
respond to changing market conditions, it should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the
accuracy of any information presented after the date of publication. The names
of actual companies and products mentioned herein may be the trademarks of
their respective owners.

To obtain authorization for uses other than those specified above, please visit
the Microsoft Copyright Permissions web page at
http://www.microsoft.com/permission/copyrgt/img-req.htm.

This content is proprietary and confidential, and is intended only for users
described in the content provided in this document. This content and
information is provided to you under a Non-Disclosure Agreement and cannot
be distributed. Copying, disclosing all or any portion of the content and/or
information included in this document is strictly prohibited.
Table of Contents

Introduction .................................................................................. 5
Internet Connection Sharing (ICS) ................................................ 7
What Is Internet Connection Sharing?....................................................7
Network Address Translation ..................................................................7
DHCP Allocator .....................................................................................8
DNS Proxy and Resolver ........................................................................8
Discovery and Control ......................................................................... 10
Hardware Requirements .......................................................................11
Verifying Configuration .........................................................................12
Host IP Addressing.............................................................................. 13
Client IP Addressing ............................................................................ 13
Troubleshooting....................................................................................14
Troubleshooting ICS Client Configuration ............................................... 15
Troubleshooting Connectivity from the ICS Client to the Internet .............. 15
Troubleshooting Connectivity from the ICS Client to the Internet .............. 16
Things to Remember ........................................................................... 17
Bridge .......................................................................................... 19
Troubleshooting....................................................................................22
Remote Desktop .......................................................................... 23
Remote Desktop Features .....................................................................23
Remote Desktop Components ...............................................................23
Remote Desktop Protocol 5.1 ............................................................... 23
Remote Desktop Connection................................................................. 24
Remote Desktop Web Connection.......................................................... 24
Remote Desktop vs. NetMeeting ........................................................... 25
Configuration and Use...........................................................................26
Enable Remote Desktop ....................................................................... 26
Configuring a Client Connection ............................................................ 28
Remote Desktop Web Connection.......................................................... 34
Remote Desktop and Remote Assistance Compared..............................35
Intended Purpose and Audience ............................................................ 35
Troubleshooting....................................................................................36
Connectivity Issues with RDC ............................................................... 36
Visual Issues in RDC Sessions............................................................... 38
Feature Issues in RDC Sessions ............................................................ 39
Performance Issues with RDC ............................................................... 39
VPN.............................................................................................. 41
Incoming VPN Connections ...................................................................43
Troubleshooting....................................................................................46
Windows Messenger .................................................................... 49
Login Issues ....................................................................................... 49
Audio/Video Conferencing Considerations............................................... 49

Table of Figures
Figure 1: Autodial configuration in Dial-up Connection Properties .............................................. 9
Figure 2: ICS Host configuration...........................................................................................10
Figure 3: ICS Client configuration .........................................................................................11
Figure 4: ICS configuration..................................................................................................12
Figure 5: Network Bridge.....................................................................................................19
Figure 6: Bridged Network Connection Properties ...................................................................20
Figure 7: Bridge Properties ..................................................................................................20
Figure 8: Remote Desktop Connection ..................................................................................25
Figure 9: Remote Tab in System Properties ...........................................................................26
Figure 10: Remote Sessions Warning ....................................................................................27
Figure 11: Add Remote Desktop Users.................................................................................. 27
Figure 12: Establish a Client Session .................................................................................... 28
Figure 13: Remote Connection General Tab........................................................................... 29
Figure 14: Remote Connection Display Tab ........................................................................... 30
Figure 15: Remote Connection Local Resources Tab ............................................................... 31
Figure 16: Remote Connection Programs Tab ........................................................................ 32
Figure 17: Remote Connection Experience Tab ...................................................................... 33
Figure 18: RDC Behind a PC NAT ......................................................................................... 37
Figure 19: RDC behind a Hardware NAT................................................................................ 38
Figure 20: Create VPN ........................................................................................................ 41
Figure 21: VPN Configuration .............................................................................................. 42
Figure 22: Configure Incoming Connection............................................................................ 44
Figure 23: Configure Direct connection ................................................................................. 45
 Advanced Networking

Introduction
Module Objectives:
● Discuss Internet Connection Sharing.

● Define a Network Bridge.

● Describe Remote Desktop.

● Explain Virtual Private Networking (VPN).

● Discuss Windows Messenger.

5
 Advanced Networking

Internet Connection Sharing (ICS)

With Internet Connection Sharing (ICS), all the users of a small network can
access the Internet by sharing the connection on one computer on the
network.

What Is Internet Connection Sharing?

ICS has several related functions that allow the home or small office user to
share their one Internet connection with all other users on their network. These
functions are:

First, Network Address Translation, which does the passing and translating of
network data from the private network to the public Internet. Then there is the
DHCP allocator, which is a means of handing out IP addresses to the clients on
the network. Next, there is the DNS Proxy and Resolver, which is used to
resolve name queries for the internal network. Windows has autodial
functionality, if the external connection is not always on. And finally, Windows
XP ICS allows automatic discovery and control by the network clients.

Internet Connection Sharing is the same in both the Home and Professional
versions of Windows XP.

Internet Connection Sharing was first introduced in Windows 98SE. The

technology was also included in Windows 2000 and Windows Millennium
Edition.

Network Address Translation

Network Address Translation, or NAT, is really the primary function of ICS. It
does the passing and translating of data from the internal to the external
network. NAT is a well-known Internet technology that has been in use for
some time. To review the NAT process briefly:

A request to an external resource is made from a client on the internal

network, which has an IP address in the RFC-defined private IP address range
of 192.168.0.x (this is the private IP address range used in Windows ICS). The
NAT computer takes the request, gives it a valid, public IP source address (its
own) and forwards the request on to the destination. When the response
comes back, addressed to the NAT computer’s IP address, the NAT computer
accepts the response, translates it back, and sends it on to the client computer
that made the original request.

One of the new technologies that Windows XP introduces into this is called NAT
traversal. NAT traversal allows Internet applications that use specific
technologies such as DirectPlay, Instant Messaging, Real-Time Communications
or streaming media, to run on client computers of the private network, without
requiring any manual configuration by the user. Some Internet applications
that use this technology are the Remote Assistance utility built in to Windows
XP, and games that use DirectPlay version 8 or version 4.

7
 It should be noted that while they have largely the same functionality, NAT is
not an application or Winsock proxy server, like Microsoft’s Proxy Server
product. NAT works at a much lower level, requiring no configuration of the
application, or installation of client software to enable its functionality. Because
of this, it is transparent to the client – it just works.

DHCP Allocator
The DHCP allocator in Windows XP ICS provides IP configuration information to
the clients on the internal network – it functions like a mini-DHCP server. This
functionality has not changed from versions of ICS in previous releases of
Windows.

When the network client, which is configured for DHCP starts, it sends a DHCP
Discover request to the ICS host. The ICS host sends IP configuration
information to the client, such as an IP address in the private IP address range
from 192.168.0.2 through 254, and a default gateway and DNS server address
of 192.168.0.1 (which is the IP address of the ICS host itself on the internal
side).

This functionality is not the same as a full-blown DHCP server. For example, it
is not configurable: it cannot be disabled, aside from disabling ICS itself, and
the IP address range that it uses is always the same and cannot be changed or
expanded.

DNS Proxy and Resolver

The DNS Proxy functionality of ICS is necessary to enable clients to get to
Internet resources by their familiar Fully Qualified Domain Names, such as
www.microsoft.com.

The DNS Proxy on the ICS host automatically relays a name resolution request
for an external resource from a client out to its own DNS server on the
Internet. When that reply comes back, the DNS Proxy does two things: it sends
the response back to the client that requested it, and it also caches that
response in its own DNS cache. In this way, if that name resolution request
comes through again, the DNS Proxy can simply directly respond to the
request, instead of having to forward it on and wait for the reply.

While DNS Proxy functionality has always been in ICS, the DNS Resolver
functionality was first introduced into ICS in Windows Me–this is now in
Windows XP. The DNS Resolver is a sort of mini-DNS server for the internal
network. Previously, without this feature, for an internal client to resolve the
name of another internal client, the first client had to rely on some form of
NetBIOS name resolution, while still using DNS for external name resolution.
Now, the client can go to the same DNS server to resolve either external OR
internal names.

8
 Advanced Networking

Autodial
Autodial takes these factors into account, and will generally keep a shared
Internet connection alive, even if the user on the ICS hosts either logs off or
switches to a different user.

Figure 1: Autodial configuration in Dial-up Connection Properties

In the situation where the connection is not already established, again autodial
will try to behave intelligently and automatically connect, using cached (or
saved) credentials for the shared connection, whether the Internet request
comes from a network client, or a user on the ICS host itself. Even if the
credentials for the shared Internet connection are not cached, when the
Internet request comes through, autodial will pop up a screen on the ICS host
asking for the credentials when it needs to establish the connection.

The only time autodial will fail is if credentials have never been stored on the
dial-up connection, and no one is logged on to the ICS host at the time autodial
tries to make the connection (or if the user logged on to the ICS host does not
have the correct credentials for the dial-up connection).

9
Discovery and Control
Discovery and control of the ICS host by the clients is a new feature of
Windows XP ICS. It is enabled on the ICS host in the same area where ICS is
enabled (and autodial as well, if the shared connection is dial-up). When
enabled, the ICS host advertises its presence and availability to be controlled
using a proprietary protocol named the ICS Simple Beacon Protocol.

Figure 2: ICS Host configuration

This advertisement is then picked up by the client, and a new icon for the ICS
host appears in the Windows XP client’s network connections folder. There is
also a standalone application that can be installed on Windows 2000, Windows
Me and Windows 98 computers to allow them to control and monitor the ICS
host as well.

10
 Advanced Networking

When the icon in the network connections folder is double-clicked, a status

screen for the shared Internet connection appears as shown below.

Figure 3: ICS Client configuration

This interface provides the user the status and some basic statistics for the
connection. In addition, two buttons are available for the client, Properties and
Disable.

The disable button does just that – it disables (or disconnects) the shared
Internet connection, and this will affect every user on the network.

The Properties button gives a few details of the connection, but also leads to a
Settings button that allows the client user to enable, disable or configure
shared services, such as a published FTP server, just as if the user were at the
ICS host.

Hardware Requirements
There are no specific hardware requirements for Internet Connection Sharing,
other than that there be an Internet Connection to share. In other words, at
least two connections must be present. Any outbound connection listed in the
network connections folder will have ICS listed on the Advanced tab, with the
option to enable or disable it shown as a check box, along with the options to
enable the autodial and Discovery and Control options.

Note: ICS set up on only one adapter at a time on the host machine at a time.

11
Verifying Configuration

Figure 4: ICS configuration

To verify the host adapter settings or to enable ICS:

1. Log on to the host computer as Administrator or Owner.

2. On the taskbar, click start, and then click Control Panel.

3. In Control Panel, click “Network and Internet Connections” found under “Pick
a category.”

4. Under “or pick a Control Panel icon,” click the Network Connections icon.

5. Right-click the connection that you use to connect to the Internet. For
example, if you connect to the Internet using a modem, right-click the
connection that you want under Dial-up.

6. On the shortcut menu that appears, click Properties.

7. Click the Advanced tab.

8. Under Internet Connection Sharing, verify that “Allow other network users to
connect through this computer’s Internet connection” check box is selected.

9. If sharing a dial-up Internet connection, verify that the “Establish a dial-up

connection whenever a computer on my network attempts to access the
Internet” check box is selected provided you want to allow your computer to
automatically connect to the Internet.

12
 Advanced Networking

While in Network Connections verify that the home adapter has been setup
correctly.

Host IP Addressing
Addressing for the shared adapter on the ICS host is provided by the ISP, and
can be either static or dynamic. Internal addressing on the home adapter is
static and ICS clients obtain IP addresses provided by ICS on the host
machine.

Client IP Addressing
Clients obtain their IP addresses from the ICS host DHCP Allocator component.
Ensure that when connected, the ICS client obtains an address in the
192.168.0.x range, with a subnet mask of 255.255.255.0. Clients should also
receive a DNS server configuration from the host. When connected they should
be configured to use the ICS host address (192.168.0.1) as their DNS Server
address.

13
Troubleshooting
Although ICS is straightforward and simple in its presentation to the customer,
there are areas where there may be problems.

The first of these may occur if the ICS host is incorrectly configured, which can
cause routing problems. One of the most common issues is where the user
adds a default gateway setting to the internal network adapter. Since the
adapter is set by ICS to a specific IP address of 192.168.0.1, this enables the
default gateway configuration to be set, and many users seeing this believe
that it must be configured, and may do so. This would be incorrect, though. In
general, each computer on a network, no matter how many network
connections, should have only one default gateway. In the case of an ICS host,
that default gateway should be set on the shared connection, and on no other
connection. Often, the shared connection is configured via DHCP, so no specific
configuring is needed.

To find out if this is the problem, the “route print” command can be used to
view the route table. Also, the IPCONFIG /ALL command will show if more than
one connection has a default gateway setting.

The next issue can occur with applications run on client computers that connect
to the Internet. If these applications expect to be directly connected to the
Internet, especially if they assume that they have a valid IP address, their
functionality might be impaired. Some applications, such as the Remote
Assistance application built into Windows XP, and games that use DirectPlay,
have been taken into account for this issue, and use NAT traversal to assist in
overcoming it.

Finally, if a problem does come up, tracing can be enabled on the ICS host to
determine where the problem is occurring. This can be configured by either
using the Netsh command or changing the registry to enable tracing on the
IPNATHLP component. Netsh command is: “Netsh ras set tracing ipnathlp
enabled”. The registry is located at:
HKLM\Software\Microsoft\Tracing\IPNATHLP. If done by changing the registry,
the computer must be rebooted for the tracing to begin. Enabling via the netsh
command does not require a reboot.

With Tracing enabled, a trace log file named IPNATHLP.LOG is created in the
Windows\Tracing folder, which traces all packets that go through the ICS host
– very useful for troubleshooting.

Troubleshooting Internet Connection Sharing involves three primary steps:

● Troubleshooting Internet Connectivity from the Host Machine

● Disable ICS and then test for connectivity to the Internet from the ICS
host computer.

● If that is successful, enable ICS and test for connectivity again.

14
 Advanced Networking

● If the connection is lost once enabling ICS but home network connectivity
is working, verify that the correct adapter has been shared.

Troubleshooting ICS Client Configuration

Once connectivity from the ICS host to the Internet has been established, the
next step is to check the configuration on the ICS client computers. The
configuration settings on the client that must be checked are:

● TCP/IP should be configured so that Obtain an IP address automatically

and Disable DNS are selected.

● Internet Explorer Connections should be set to Never dial a connection.

● Internet Explorer Connections LAN settings should have Use a proxy

server disabled.

● Verify that the client machines can browse the Private network.

● Verify the Internet Connection Firewall is not enabled on the client

machines.
Note: On Windows XP SP2 computers, leave Windows Firewall enabled,
but enable the Allow incoming echo request option in the ICMP
Settings. This interface is available on the Advanced tab of the Windows
Firewall control panel interface.

Troubleshooting Connectivity from the ICS Client to the Internet

● Test connectivity to the ICS host by pinging 192.168.0.1 from the client.

○ If this succeeds, continue to the next step.

○ If it fails, check for an addressing or physical connectivity issue.

● Try to open a Web page in IE by IP address.

○ If this succeeds, continue to the next step.

○ If it fails:

■ Test connectivity to the same site on the ICS host.

■ Check other sites by IP address.

■ Check for local IE issues.

● Try to open a page by host name.

○ If this succeeds, ICS is working properly.

○ If this fails:

15
 ■ Test on ICS host to eliminate DNS issue.

■ Check DNS server address used on client.

Once connectivity from the ICS host to the Internet has been established, the
next step is to check the configuration on the ICS client computers. The
configuration settings on the client that must be checked are:

● TCP/IP should be configured so that Obtain an IP address automatically

and Disable DNS are selected.

● Internet Explorer Connections should be set to Never dial a connection.

● Internet Explorer Connections LAN settings should have Use a proxy

server disabled.

● Verify that the client machines can browse the Private network.

● Verify the Internet Connection Firewall is not enabled on the client

machines.

You can also assign a unique static IP address to the client machines in the
range of 192.168.0.2 to 192.168.0.254. For example, you can assign the
following static IP address, subnet mask, and default gateway:

● IP Address 192.168.0.2

● Subnet mask 255.255.255.0

● Default gateway 192.168.0.1

This configuration is only recommended for specific networking needs and for
testing connectivity issues. (Refer to KB article Q306126)

Troubleshooting Connectivity from the ICS Client to the Internet

Test connectivity to the ICS host by pinging 192.168.0.1 from the client.

● If this succeeds, continue to the next step.

● If it fails, check for an addressing or physical connectivity issue.

Try to open a Web page in IE by IP address

● If this succeeds, continue to the next step

● If it fails:

○ Test connectivity to the same site on the ICS host

○ Check other sites by IP address

16
 Advanced Networking

○ Check for local IE issues

○ Try to open a page by host name

○ If this succeeds, ICS is working properly

● If this fails:

○ Test on ICS host to eliminate DNS issue

○ Check DNS server address used on client

Things to Remember
With connectivity issues involving Internet Connection Sharing, it is important
to narrow down the issue to the specific area that the problem resides. With
ICS, not only may the problem be an application problem (like Internet
Explorer), it could also be a network connectivity problem.

Bridging is supported and detected by the Home Networking Wizard on mixed

networks in Windows XP. The wizard does not bridge a network adapter that is
connected to an external DSL or cable modem.

The Network Setup Wizard can only be run on computers running Windows 98,
Windows 98SE, Windows Me, Windows XP Home Edition and Windows XP
Professional. ICS only supports 5 client machines per Internet connection.

Not all applications may be able to communicate through the ICS host without
special configuration support from the manufacturer. If Web browsing from the
ICS client to the Internet is functioning, then ICS is working correctly.

17
 Advanced Networking

Bridge
Network Bridge in Microsoft® Windows® XP provides an easy way to connect
several network segments to make them appear as a single network. All
bridged adapters on the bridging computer appear as a single network
interface to applications and protocols.

Creating a Bridge
Bridges are created by using two methods in Windows XP:

● By the Network Setup Wizard, when the selections indicate multiple

network interfaces are for the home network.

● Manual Creation.

The result of either method is the same:

● Adapters participating in the bridge are grouped in the Network

Connections folder.

● Limited properties available for bridged connections.

● Configures TCP/IP and Service bindings in the properties for the bridge.

When you have created a bridge, the bridged connections are grouped in the
Network Connections folder as shown below.

Figure 5: Network Bridge

19
 Modification of the participating adapters is not recommended; therefore only
limited properties are available, as shown below.

Figure 6: Bridged Network Connection Properties

Because the two connections have been bound together as one virtual network,
properties such as the TCP/IP configuration must be set on the bridge using the
bridge properties interface.

Figure 7: Bridge Properties

20
 Advanced Networking

In addition to the network configuration, the bridge properties also enable you
to add or remove specific network connections from the bridge configuration,
as shown in the Adapters portion of the interface above.

If you need to modify individual network interface properties, press the Shift
key, right-click, and select the properties for the interface.

When troubleshooting a customer’s network issue, it can be useful to remove

the bridge from the configuration until the underlying issue is resolved. To do
this, simply delete the Bridge in the Network Connections folder.

Note:
If you want to see how a bridge appears in the Windows XP Network
Connections folder, create one yourself. If you only have one network adapter
on the computer, install the “Microsoft Loopback Adapter” using the Add
Hardware wizard. This is a software-implemented network adapter that only
connects to the local machine. Even though it doesn’t connect you to another
network, it does give you the ability to bridge this new network connection with
your existing NIC connection.

Bridge Technology Overview

The Bridge component interconnects network segments by forwarding frames
from one segment to another. This appears to be transparent to the
networking layers that are above Layer 2.

Bridges in Windows XP are designed to simplify the setup and administration of

a multi-segment home network. The classic model of a multiple-segment IP
network involves assigning each network segment a subnet number, correctly
configuring hosts on each subnet, and configuring packet forwarding between
the subnets. Bridging the segments that comprise a home network simplifies
the situation and the entire home network can be operated as a single IP
subnet.

The Windows XP Bridge driver binds to multiple network adapter drivers, and
shows a single bridge connection in the Network Connections folder. This
causes all bridged network segments to appear as a single virtual network
adapter. This is advantageous because the bridge’s behavior effectively
combines the bridged network segments into a single logical segment and
presents only a single virtual interface to transport drivers. The single virtual
interface causes the network binding structure to reflect a logical arrangement
of the network.

For example, the TCP/IP driver expects to be able to associate each adapter
with an IP subnet. When a single subnet number is shared by more than one
adapter, TCP/IP behaves undesirably. It sends all outbound IP packets to the
first shared-subnet adapter it was bound to in the absence of host-route entries
in the IP routing table. The bridge’s status as an intermediate driver solves this
problem.

21
Troubleshooting
What should you do if you cannot create a bridge?

● Verify that the connections to be bridged are of a supported type, such as

Ethernet, HomePNA, or 802.11 Wireless.

● Verify need for the bridge and eliminate any potential topology issues.

● Verify if the bridge can be eliminated from the configuration.

● Verify if the network adapters are installed properly.

What should you do if the bridge is not functioning properly after it is created?

● Verify that the interface configurations have not changed after the bridge
was created.

● Check documentation from the manufacturer to verify that all adapters

support Promiscuous mode.

● If one or more adapter does not support promiscuous mode, test the
bridge in Compatibility Mode.

22
 Advanced Networking

Remote Desktop
Remote Desktop provides the ability to gain access to and operate a remote
computer. While this capability is based on Terminal Services, it provides
functionality well beyond that of the Terminal Services provided by Windows
2000.

All Remote Desktop functionality is provided with Windows XP Professional. The

XP Home Edition contains the client, but cannot serve as a host. Remote
Desktop is based upon Terminal Services technology. Only the keyboard input,
mouse input, and display output data are transmitted over the network to the
remote location. Remote Desktop hosting is available on Windows XP
Professional.

Remote Desktop Features

When you establish a Remote Desktop session, it becomes the only active
session on that machine. The remote console “locks down,” meaning that it
disables display of the session on the remote computer's monitor and disables
input via the remote computer's keyboard and mouse. If a session is currently
active at the remote machine, the user will be prompted to relinquish control.
The user can approve or deny the request.

Unlike the 2000 Terminal Services, Remote Desktop can handle high screen
resolutions and color depths. It will display in as many colors as the client
computer will support, up to 24-bit. While this capability is configurable by the
client, and can be overridden by the remote host; it is handled automatically in
most cases.

Many of the new features of Remote Desktop are provided by Remote Desktop
Protocol 5.1. We’ll detail those items later in the lesson.

Remote Desktop Components

The key components of Remote Desktop are its protocol RDP and its clients,
Remote Desktop Connection and Remote Desktop Web Connection. We’ll take a
closer look at each of them.

Remote Desktop Protocol 5.1

The capabilities of RDP 5.1 allow many improvements over the Terminal
Services provided on Windows 2000. Resource redirection is the key to much of
the improved functionality of a Remote Desktop session. For instance, the
following features are available:

● Since your local file systems appear in the session’s Explorer views, files
can easily be transferred from one machine to the other.

23
 ● If you launch a program in the remote session that has audio output, the
sound comes out of the client’s speakers.

● If you are running an application that uses a serial port, like a bar-code
reader, it will utilize the port on the client machine.

● If you print from a remote application, the default printer will be the
client’s default printer, so it will print where you are.

● If you copy data to the clipboard from the remote session, it can be
pasted into the local session, or vice-versa.

● Client resources are available within a session:

Remote Desktop Connection

Remote Desktop Connection is a tool that allows your client computer to
establish a Remote Desktop session with another computer running
Windows XP Professional. These computers could be located anywhere,
provided that they have network access from one to the other. The client user
must also have been granted permissions to remotely access the host
computer.

The Remote Desktop Connection tool is installed by default when you install
Windows XP Professional or Home Edition. You can also install this tool
manually on a computer running Windows 95, Windows 98, Windows NT, or
Windows 2000 Professional. There is a utility on the Windows XP Pro CD that
installs the Remote Desktop Connection on these non-XP clients.

Remote Desktop Connection connects a client computer to another computer

running Windows XP Professional. Network access and appropriate permissions
are required. Remote Desktop Connection is configured by default in Windows
XP Professional. It can be installed manually on computers running Microsoft
Windows 95, Windows 98, Windows NT®, and Windows 2000 Professional. The
clients for these operating systems are on the Windows XP Professional CD

Remote Desktop Web Connection

Users who travel can use Remote Desktop Web Connection to gain secure
access to their primary workstation from any computer running Windows and
Microsoft Internet Explorer 4.0 or higher.

Remote Desktop Web Connection can establish a Remote Desktop session with
a remote computer, even if Remote Desktop Connection is not installed on the
client computer. Remote Desktop Web Connection must be installed on a Web
server with Internet Information Services and Active Server Pages enabled.

24
 Advanced Networking

When a client establishes a connection by using a Remote Desktop Web

Connection, the session traffic does not go through the web server that hosted
the control. The session is established directly between the client and host
computers.

Figure 8: Remote Desktop Connection

Remote Desktop delivers virtually the same functionality as the Remote
Desktop Connection, but over the Web. It is implemented by an ActiveX control
embedded in a web page—no special client is needed, but TCP/IP is required. It
requires Internet Information Server (IIS) and Active Server Pages (ASP) for
hosting the control. The traffic does not route through the web server. The
remote session opens in a web page. With Remote Desktop Web Connection, a
Terminal Services connection can be deployed by sending a URL.

Remote Desktop vs. NetMeeting

Traditional remote-control products, including NetMeeting, have what is known
as "the janitor problem.” This means that people can see your remotely-
activated desktop at the office when you connect to it and unlock it from home.
The Windows XP Remote Desktop actually disconnects your console when you
connect remotely, so all anyone sees when you're using the computer remotely
is the log on screen. For that reason, when you're remotely connected, a
person can't walk up to your PC's console and take control of your session.
Thus, Remote Desktop is more secure than NetMeeting because it prevents
third party intervention and viewing.

Remote Desktop is a console session, making the remote session the sole
active point of control. NetMeeting uses joint control, leaving the host
computer accessible from the console. NetMeeting allows anyone near the
machine to observe all activity

25
Configuration and Use
Remote Desktop is configured on the target computer – the computer with the
desktop you want to use remotely. Then, the client software is used to make a
connection to that computer.

Enable Remote Desktop

In Windows XP Professional, Remote Desktop access is enabled by a checkbox
in the Remote tab of the System Properties dialogs. To enable Remote Desktop
access to a computer running Windows XP Professional, you must have
administrative privileges.

● On the Start Menu, right-click My Computer and select Properties.

● Click the Remote tab.

● In the Remote Desktop section, put a check in the box to allow users to
connect remotely.

Figure 9: Remote Tab in System Properties

26
 Advanced Networking

When Remote Desktop is enabled, a warning appears as shown below. This

notifies the administrator that users with null passwords will be unable to
connect remotely. This behavior is universal in Windows XP and is explained in
greater detail in the Security lessons of this training. The dialog also points out
that Remote Desktop may be blocked by firewalls or other intermediary
software or devices.

Figure 10: Remote Sessions Warning

To set permission for remote access, press the Select Remote Users button.
Note the warning that remote users must have passwords and that firewalls
may block Remote Desktop access.

Figure 11: Add Remote Desktop Users

Assigning Remote Desktop Rights

For a user to establish a Remote Desktop connection with a Windows XP
Professional machine, the right to do so must be granted. The following series
of dialogs provides a mechanism for viewing, adding, or removing users from
the Remote Desktop access list.

27
Configuring a Client Connection
Now that we have enabled Remote Desktop and granted access rights to users,
we need to configure a client to make a connection to it.

From a Windows XP Professional or Home Edition machine, the Remote

Desktop Connection tool is located in the communications group in the Start
menu structure.

The initial dialog that it opens is all that is needed to launch a Remote Desktop
Connection. Entering the remote machine name, the authorized username, and
pressing Connect is all that is necessary.

Launch the Remote Desktop Connection tool by selecting: Start > All Programs
> Accessories > Communications > Remote Desktop Connection. In the dialog,
enter the Remote Computer Name and an authorized username.

Figure 12: Establish a Client Session

Click the Connect button to establish the session. The next section examines
the additional settings available via the Options button.

28
 Advanced Networking

Connection Configuration – General

The General tab is used for creating a quick method of launching a specific or
customized Remote Desktop Connection. By entering the Remote machine
name and the authorized username, then pressing Save As, the connection can
be launched in the future by double-clicking an icon. This approach is most
convenient f or frequently used connections.

Figure 13: Remote Connection General Tab

On this tab you can enter the computer and user information as before, but
also add the domain and password of the user. This tab also allows you to save
the connection settings as an RDP file, much like a dial-up connectoid. The
Open button allows modification of a previously saved connection

29
 Connection Configuration – Display
The Display tab can be used to specify the color depth and screen resolution of
the Remote Desktop. Although Remote Desktop can auto-detect and configure
these settings, customization for special circumstances or applications may be
appropriate. The default is full screen and 24-bit color, or the color depth of the
client, which ever is lower.

Figure 14: Remote Connection Display Tab

This tab allows you to specify the display settings for the session, including:

● The initial screen size for the session

● The color depth for the session

At the bottom there is a check box to enable or disable the connection bar. This
bar provides window controls for the full screen session. The controls can be
used to minimize, maximize, restore, or close the Remote Desktop window.
The connection bar provides controls similar to a window title bar. This is
necessary since there are no such controls on the desktop.

30
 Advanced Networking

Configuration – Local Resources Tab

The Local Resources tab controls aspects of the interaction between the
Remote Desktop and the local machine.

Figure 15: Remote Connection Local Resources Tab

The following resources can be configured on this tab:

● Sounds can be played on the remote speakers, the client speakers, or not
at all.

● The Windows shortcut key combinations, such as Alt-Tab can be applied

to the remote machine, the local machine, or to the remote machine only
when the Remote Desktop is full-screen.

● The ability to have a remote session print to a client’s printer has obvious
benefits, but the option to have it print in the remote location can be
configured here.

31
 Connection Configuration – Programs
The Programs tab is especially useful when configuring a connection in order to
repeatedly perform a specific function. This could be running a report or
checking mail. This option relieves the user of navigating the remote UI to
launch the application each time. This tab allows you to configure a specific
program to be launched at the start of the session.

Figure 16: Remote Connection Programs Tab

32
 Advanced Networking

Configuration – Experience Tab

The Experience tab is used to reduce the visual data that is transmitted over
the connection. The selection of a specific connection speed changes the visuals
that will be transmitted, optimizing the balance of performance and aesthetics.

Manually selecting an item may trigger the settings to be shown as Custom.

Care should be taken with specifying a speed higher than actual as serious
performance degradation could result.

Figure 17: Remote Connection Experience Tab

This tab allows you to configure a number of settings which will affect the
performance of the session. Select the connection speed from the dropdown
box, which changes the on/off defaults for the following settings:

● Desktop Background

● Dragging full windows

● Menu and window animation

● Themes

● Bitmap caching

Save the Connection

After changing any of the settings in these five dialogs, remember to go back
to the General tab and save the connection. Failure to do so will force you to
make the changes each time you establish the connection.

33
Remote Desktop Web Connection
In addition to the Remote Desktop Connection software included with Windows
XP, there is a web-based option. This option is called the Remote Desktop Web
Connection.

Like the regular client, this software creates a connection to the Remote
Desktop host using TCP port 3389. The only difference is that you do not need
to have the full client installed on the client computer. You simply connect to a
web page that loads the Remote Desktop Web Connection ActiveX control, and
can then logon to the Remote Desktop computer.

Benefits
Following are a few benefits of the Remote Desktop Web Connection.

● Users who are away from their computers can use Remote Desktop Web
Connection to gain secure access to their primary workstation or favorite
Terminal Server from any computer running Windows and Internet
Explorer.

● With Remote Desktop Web Connection, deploying a connection can be as

easy as sending a URL.

● The Remote Desktop Web Connection is targeted at a lowest common

denominator cross platform system. Remote Desktop Web Connection
can also meet the needs of organizations that want identical clients on all
platforms, thus reducing the total cost of ownership

● The delivery of extranet applications is also now possible with the Remote
Desktop Web Connection. Corporations that want to deploy Terminal
Server to serve up a set of applications using the Remote Desktop Web
connections to their vendors, suppliers, can now do so easily,
inexpensively, and efficiently over the Internet.

Installation
The Remote Desktop Web Connection can be downloaded from the following
location to install on a web server:
http://www.microsoft.com/windowsxp/downloads/tools/rdwebconn.mspx

See that web page for information on installing the software.

34
 Advanced Networking

Remote Desktop and Remote Assistance Compared

Microsoft® Windows® XP includes both Remote Desktop and Remote
Assistance. They are similar in appearance, but quite different in
implementation and intent. This lesson will illuminate the differences.

In many ways, Remote Desktop and Remote Assistance are very much alike.
They are both capable of providing a remote control session for a computer for
a user who is not at the physical location of the machine.. They are both built
on the Terminal Services architecture. They both require permission to
establish a session, and either session type can be terminated from either
machine. Despite all those similarities, they are quite different.

Intended Purpose and Audience

Remote Desktop is targeted at a user who has a desktop machine containing
his applications and data files. Remote Desktop allows him to connect from a
variety of remote locations and operate the machine as if he were there.
Remote Desktop is designed for potential every day use.

Remote Assistance is targeted at a user who needs assistance from a support

organization or friend. This may be for resolving a problem, or demonstrating a
technique. It is likely to be used only infrequently.

Remote Desktop
● Remote Desktop is designed for frequent accesses by an individual or
small group of users.

● Remote Desktop is generally designed for a user to remotely operate

his/her own machine from another location.

● Remote Desktop and Remote Assistance are available on Windows XP

Professional.

Remote Assistance
● Remote Assistance is intended for one-time or infrequent access for
troubleshooting and resolving a problem, or demonstrating a technique.

● Remote Assistance is intended for a helpdesk, friend, or other support

person to access the machine of an end-user.

● Remote Assistance is available on the Windows XP Home Edition

35
Troubleshooting
Issues with Remote Desktop fall into three basic categories.

● The inability to establish a Remote Desktop Connection under some

circumstances.

● Unexpected reduction of display resolution or visual quality.

● Poor performance during a Remote Desktop session.

We will cover each of these areas.

Connectivity Issues with RDC

Remote Desktop Connectivity failures largely fall into two categories:

● The inability to connect due to incomplete configuration

● The inability to connect due to specific network configurations

General Connectivity Points

When a Remote Desktop Connection fails, you must first check to make sure
the basics have been addressed. Windows XP Professional machines do not
accept remote connections by default. They must be enabled by an
administrator via the remote tab of System Properties.

Local administrators have access rights by default. All others must be granted
remote access privileges. This can also be done via the remote tab of system
properties. Remember that all external connections to Windows XP machines
are blocked if the user does not have a password.

RDC Connectivity behind NATs

Remote Desktop Connections are established by specifying the machine name
or the IP address of the remote computer. If the remote machine is behind a
NAT, its machine name is not exposed on the public side of the NAT. Its IP
address is similarly inaccessible, since the NAT uses its own external IP address
to handle the communication on the public side. This situation is not
insurmountable, but special configuration will be required to make it work.

A machine behind a NAT router or ICS cannot participate in an inbound Remote

Desktop connection without special accommodations. The NAT, by default, will
not traverse public to private address for inbound connections. The NAT, by
default, will not pass or forward traffic on port 3389 (used by Terminal Services
and Remote Desktop)

36
 Advanced Networking

NAT Variants
There are several types of NATs that may be encountered and each requires a
different process to troubleshoot failures. Each accepts Internet-bound
communication from its clients then uses its own IP address to communicate on
the public, or Internet side. The NAT tracks the communications, and sends the
return responses to the appropriate client. This allows multiple machines to use
a single external connection, and provides a measure of anonymity to the
clients. The most frequently encountered NAT types are:

● Internet Connection Sharing, or ICS, which is a simple NAT

● NAT enabled on a multi-homed server PC, such as Windows 2000 Server

● NAT implemented by hardware

RDC behind ICS

The best resolution in the ICS case is to establish a Remote Desktop
Connection to the ICS machine, which is exposed on the public side. From
within that session, a Remote Desktop Connection can then be made to the
target machine. There is some additional overhead in this approach, but it
addresses the issue with a supported method.

RDC behind a PC NAT

There are two possible workarounds when the remote machine is behind a PC
NAT.

The first is basically identical to the ICS workaround. Establish a Remote

Desktop Connection or Terminal Server Connection to the NAT machine which
is exposed on the public side. From within that session, a Remote Desktop
Connection can then be made to the target machine. The same additional
overhead as the ICS case will somewhat limit performance.

The second possibility is to use the NAT configuration tools to forward

communication on port 3389 to Machine A, then make the Remote Desktop
connection to the external IP address of the NAT router. The session
communication will be automatically forwarded to Machine A.

Figure 18: RDC Behind a PC NAT

37
 With this workaround, all Remote Desktop Connections from outside the NAT to
machines behind the NAT will be limited to Machine A, so Machine B in the
diagram could never receive a Remote Desktop connection.

Note: If a remote (Terminal Server or Remote Desktop) computer is

configured to use a port other than 3389, the appropriate port can be specified
in the Remote Desktop Connection. In the Computer field, follow the machine
name with a colon and the port (e.g. Servername:3390).

RDC Behind a Hardware NAT

Hardware NAT routers have become popular due to their low cost and virtually
automatic configuration in many instances.

The only option with a hardware NAT is the same as workaround 2 in the
previous case. Use the NAT configuration tools to forward communication on
port 3389 to Machine A, then make the Remote Desktop connection to the
external IP address of the NAT router. The session communication will be
automatically forwarded to Machine A.

Figure 19: RDC behind a Hardware NAT

Again, with this workaround, all (port 3389) Remote Desktop Connections from
outside the NAT to machines behind the NAT will be limited to Machine A.

Visual Issues in RDC Sessions

Visual issues may be encountered with Remote Desktop. A Remote Desktop
connection uses the display resolution and color depth specified in the
connection, or the current settings on the machines involved, whichever is
lowest.

Trying to transmit a 32-bit desktop wallpaper at a lower color depth can result
in poor appearance. Disabling the transmission of the desktop background is
the easiest resolution.

38
 Advanced Networking

Feature Issues in RDC Sessions

When connecting from a machine other than Windows XP, you will be unable to
redirect disk drives, redirect audio, use color depths above 256, redirect
network printers, or cache logon credentials.

Important: Only those features listed in the Remote Desktop Connection

dialogs are available over Remote Desktop. There are Windows XP features
that are not available, such as ClearType or MIDI audio, primarily for
performance reasons.

Performance Issues with RDC

When using the Remote Desktop Connection, after the screen is initially drawn,
the server only sends changes on the display to the client. High resolutions and
color depths require more information to draw the screen. Animation requires
constant updates to be sent to the client. Using images as wallpaper also
effects performance because as items are moved on the desktop parts of the
wallpaper image must be resent to the client. Viewing web pages with
animation will also degrade performance due to increased screen update
requirements.

If the client is connecting over a dial-up connection, but the connection is

configured as LAN, the additional default feature inclusion will result in very
poor performance.

Resolution for Performance Issues

Resolving performance issues with Remote Desktop is generally a matter of
disabling bandwidth-consuming features until the performance reaches
acceptable levels. To access the Remote Desktop Connection dialog box, click
Start > All Programs > Accessories > Communications > Remote Desktop
Connection

The Experience tab has a connection speed setting that automatically changes
the visuals transmitted during the session. Make sure the connection speed is
set to the actual speed, or lower. Using the Custom setting and manually
disabling features may be appropriate.

● On the Display tab, consider reducing screen resolution and color depth.

● On the Local Resources tab, turn off audio redirection if it is not needed
for the task being performed.

39
40
 Advanced Networking

VPN
Virtual Private Networking (VPN) offers affordable, secure access for home and
small offices operating over any networking technology over which IP packets
can be sent.

VPN Connection
A VPN is a simulated private network that has links across shared or public
networks, such as the Internet or a corporate network. Although VPN
connections go through these public networks, their data is encapsulated and
secured while crossing these shared paths.

Figure 20: Create VPN

41
 VPN Configuration
To configure a VPN client connection, right click the icon and choose Properties.

Figure 21: VPN Configuration

42
 Advanced Networking

Incoming VPN Connections

In addition to acting as a VPN Client, Windows XP Professional Edition can act
as a VPN server, accepting incoming VPN connections for connectivity to a
home network.

To allow incoming connections on a Windows XP computer, use the New

Connection Wizard to create an incoming connection icon. The wizard, of
course, can be run from the Network Connections folder. You can access it
from the Control Panel, click Network and Internet Connections, and then click
the Network Connections control panel icon. To launch the New Connection
Wizard, click the Create a new connection link under Network Tasks.

The first screen of the wizard is an introductory one; click Next to create an
incoming connection icon; choose Set up an advanced Connection, and click
Next. The wizard gives two choices, to Accept incoming connections or to
Connect directly to another computer. Choose the first option and click Next.

The next screen allows you choose which devices will allow incoming
connections. You can do it with Direct connections via a parallel port or by a
serial port or you can choose a modem if you have one. If you have an infrared
port, that will be listed here as well. You can also choose to configure the
properties of these devices at this point. Clicking Next, you are prompted
whether you want to allow virtual private connections to this computer. Choose
to allow it and click Next.

The next screen lists the users that are configured on this computer. You can
check the boxes of the users that you want to allow to connect to this box. At
this point, you can also configure the properties of some of these users
changing their passwords. You can configure the call back options, which allows
the user to call in to this computer. They will then be disconnected and this
computer can then call them back at a specific call back number or at a
number that a caller specifies. This will help to save toll charges for the user.

Clicking Next goes to the Networking Software screen. Here, you can enable or
disable the items that you want to be used for this connection. For example,
the Internet Protocol (TCP/IP), File and Printer Sharing, Client for Microsoft
Networks. From here, you can also configure the properties of these items. For
example, with Internet Protocol (TCP/IP), you can specify to either assign IP
addresses to the people calling in using a DHCP server on the network or you
can specify a set of IP addresses that will be assigned to these users. You can
also check to allow the calling computer to specify its own IP address. Once
these items are selected, click Next. You get a summary screen and then you
can click Finish.

43
 You now have an incoming connections icon. The Properties dialog has three
tabs: General, Users and Networking.

Figure 22: Configure Incoming Connection

The General tab provides some of the same options that available during the
wizard. You can choose which devices to allow incoming connections on and
you can configure the properties of these devices. You can also choose to allow
VPN connections by checking or un-checking the box or you can check the icon
at the bottom of the dialog box, which will show an icon in the Notification
Area, or System Tray, when this connection is alive.

The Users screen for incoming connections allows you to select which users will
be allowed to connect to this machine. Again, you can change the properties of
this user or you can create a new user at this point from this screen, giving a
user name, full name and a password for that user. You also have two other
options down here. The first of which will require all users to secure their
passwords and data and the other which will always allow directly connected
devices, such as Palm Talk computers, to connect without providing a
password.

Finally, on the Networking tab you can select which network components to
enable or disable by checking the box. You can configure the properties of
those items or install new items, clients, services or other protocols.

44
 Advanced Networking

Configuring Direct Connections

To configure Direct connections, right-click the icon created by the New
Connection Wizard and choose Properties. These configuration options are
explored in the accompanying demonstration. Please view this demonstration
now.

Figure 23: Configure Direct connection

45
Troubleshooting
Troubleshooting for VPN connections involves the following components:

● Client VPN Connection Configuration

● Network Connectivity

● Support for PPTP Traffic on the Connection

● Server VPN Configuration

The following sections provide guidance on specific troubleshooting steps for

isolating each of these components of the VPN configuration.

The steps below assume a Point to Point Tunneling Protocol (PPTP) VPN, which
is the type of VPN server provided by Windows XP Professional. If the customer
is using an alternate type of VPN (Layer 2 Tunneling Protocol – L2TP), or using
third party VPN client software, only the first two troubleshooting processes
apply. This is because there are different requirements for PPTP and L2TP.

Client VPN Connection Configuration

Start your troubleshooting by checking that the Network Connection on the
client computer has the correct information for the server name and protocol –
the default is PPTP, which is the type of VPN server provided by Windows XP
Professional.

As a test, create a new network connection for the VPN and test. Note any
error messages and use the Knowledge Base for further troubleshooting.

Network Connectivity
Once you have determined that the connection is set up properly on the client,
test basic connectivity between the client and server using ping. Resolve any
connectivity issues before continuing with further troubleshooting.

Support for PPTP Traffic on the Connection

The Windows XP Support Tools provide two tools for verifying PPTP connectivity
requirements are in place:

● pptpsrv.exe: acts as a server to verify the two types of network traffic

from the client can be received.

● pptpclnt.exe: acts as a test client for the above tool.

Note that these two tools do not establish a VPN connection – they just verify
that the two computers can pass the right types of traffic for a PPTP VPN
connection to succeed. PPTP uses TCP port 1723 and that GRE 47 packets.

Also note that if the connection uses L2TP or third party VPN software, you will
need to collaborate with the support organization for the VPN server software
to troubleshoot further. The following steps do not apply.

46
 Advanced Networking

To use these tools for troubleshooting:

1. Install the Windows XP Support Tools on both computers. The

installation is done using \Support\Tools\Suptools.msi on the Windows
XP CD ROM.

2. First, disable the Incoming Connection on the Windows XP Professional

computer which is acting as the server. This ensures that the utility can
bind to the right port.

3. Next, open a CMD window on the server computer and run the pptpsrv
command.

4. Then open a CMD window on the client and run the command: pptpclnt
<servername>, replacing “<servername>” with the computer name or
IP address of the server computer.

5. Watch the prompts on both computers, noting the results.

a. If the connection succeeds, this means the network or Internet

connections support the right kind of traffic for a PPTP VPN
connection to succeed.

b. If the connection fails, but you don’t see any indication of why it
fails on the server, troubleshoot basic connectivity.

c. If you receive the following error message, this indicates a name

resolution problem. Test using the IP address of the server with the
pptpclnt command:
Error 11001 getting Host information:
WSAHOST_NOT_FOUND: Host not found

d. If the initial connection succeeds, but there is an indication of a

problem with the kind of traffic received, use the information
returned to troubleshoot the connection.

This last type of failure indicates that a firewall or router between the
computers is likely not passing the type of traffic required to establish the
connection. If the two computers are on home networks, consider the
following:

● Check the configuration and documentation for any routers in use at the
edge of the home networks. You may need to recommend that the
customer check the configuration of the routers, and configure them to
pass VPN traffic. Configuration for TCP 1723 passthrough is
straightforward, but it is less common to have an option for GRE 47. In
most cases home routers enable this when you choose to allow VPN
traffic.

● Try connecting each computer directly to the Internet rather than through
a router as a test. Before doing this, verify the computers are configured
with a software firewall.

47
 ● If third party firewall software is in use, consider disabling that protection
and testing with the Windows XP firewall, either Internet Connection
Firewall or Windows Firewall, depending on the service pack level of the
computer.

Server VPN Configuration

If the previous test is successful, this means that connectivity and firewalls are
not the problem. It is more likely that the server is misconfigured in some way.

If the server is a Windows XP Professional computer, delete the Incoming

Connection icon in the Network Connections Folder and go through the Create
New Connection wizard to create a new VPN connection.

If the server is another type, consult with the support organization for that
operating system or device for further assistance.

48
 Advanced Networking

Windows Messenger
Windows Messenger is an Instant Messaging client that includes real time
communications tools for Instant Messaging to other Internet users, voice and
video communication, and online collaboration. It is installed by default on
Windows XP Home edition and Windows XP Professional edition. Windows
Messenger is comparable to version 4.0 of MSN Messenger.

Because MSN Messenger has been updated several times with new features
and functionality, it is the recommended Instant Messaging client for home
users.

For this reason, this document focuses only on a few key elements of Windows
Messenger that could impact support.

Login Issues
Failures with logon to the Passport service are a top support issue. For
information on resolving these issues, see the following Knowledge Base
article:
Common Solutions for Windows Messenger Account Logon Problems (307294)

Audio/Video Conferencing Considerations

There are some hardware requirements for conferencing in Windows
Messenger. Typically, audio capabilities are considered a minimum requirement
for a conference, while video is always optional.

Audio requirements:
Both parties should have a full duplex sound card and one of the following:

● PC speakers and an external microphone plugged into the sound card

● Audio headset with microphone that plugs into the sound card

● Soundcards on the Windows XP HCL will work with Windows Messenger

audio conferencing.

Video requirements:
● For video conferencing, one or both parties need a supported video
capture device such as a USB webcam.

Audio and Video Tuning Wizard

The Audio Tuning Wizard will launch the first time you attempt to establish and
audio session with another contact. Additionally, the wizard can be launched at
any time by selecting Audio and Video Tuning Wizard from the Tools menu.

49
 Before launching the wizard, you should make sure all programs that utilize
A/V devices are closed. Also, make sure any cameras, speakers, and
microphones are properly plugged-in and powered on. The wizard helps the
user configure the following:

● Selection of microphone or speaker device (sound card)

● Use of speakers/microphone vs. headset

● Speaker volume calibration

● Microphone volume calibration

● Video device selection

Note:

Any time you change the configuration of the A/V system, the Audio and Video
Wizard should be re-run. For example, if you specify that you are using a
headset, AEC will be disabled to conserve system resources. If you switch, to a
speaker/microphone setup, re-run the wizard to enable AEC and recalibrate the
volume.

50