Peer Client NAT Compatibility Reference

The following section outlines peer client Network Address Translation (NAT) compatibility for applications that follow the guidelines recommended in previous sections.

Windows 98 Second Edition Internet Connection Sharing

Any number of peer clients behind or on the same Microsoft® Windows® 98 Second Edition Internet Connection Sharing (ICS) system is supported. Peer clients behind different Windows 98 Second Edition ICS computers are not supported.

A player behind or on the Windows 98 Second Edition ICS computer that receives a DPN_MSGID_HOST_MIGRATE message indicating that the host has migrated to the local player becomes a peer host. See the Windows 98 Second Edition Internet Connection Sharing section in the Peer Host NAT Compatibility Reference topic.

Windows 2000 Internet Connection Sharing

Any number of peer clients behind or on the same Windows 2000 ICS system is supported. Peer clients behind different Windows 2000 ICS computers are not supported.

A player behind or on the Windows 2000 ICS computer that receives a DPN_MSGID_HOST_MIGRATE message indicating that the host has migrated to the local player becomes a peer host. See the Windows 2000 Internet Connection Sharing section in the Peer Host NAT Compatibility Reference topic.

Windows Millennium Edition Internet Connection Sharing

Any number of peer clients behind or on the same or different Windows Millennium Edition (Windows Me) ICS computers is fully supported using Microsoft DirectPlay®'s automatic traversal.

Windows XP Internet Connection Sharing

Any number of peer clients behind or on the same or different Windows XP ICS computers is fully supported using DirectPlay's automatic traversal.

Non-Microsoft NAT Device with Universal Plug and Play

Any number of peer clients behind the same or different non-Microsoft NAT devices that are compatible with DirectPlay's automatic traversal using Universal Plug and Play (UPnP) is supported. Refer to the NAT device's documentation for UPnP compatibility information.

Non-Microsoft NAT Device without Universal Plug and Play

Any number of peer clients behind the same NAT device without UPnP is supported. Peer clients behind different NAT devices without UPnP are not supported but might work, depending on the device implementation.

The Advanced NAT Techniques for Peer Clients describes methods that can be used to allow clients to join sessions in some scenarios that do not work using default settings.

A player behind a non-Microsoft NAT device that receives a DPN_MSGID_HOST_MIGRATE message indicating that the host has migrated to the local player becomes a peer host. See the Third-Party NAT Device Without Universal Plug-and-Play section in the Peer Host NAT Compatibility Reference topic.