Abstract: A diagnostic tool for identifying a configuration of a private network that may disrupt operations involving communication between two devices on the network. The tool, when run on a device in the network, can identify a “double NAT” configuration in which the device may be separated from other devices on the private network by a NAT device. The tool, when run on a computing device, identifies a NAT device, such as a router, to which the device is connected. The tool then identifies a list containing one or more other devices that may be connected to the NAT device. The tool tests whether these other devices also perform NAT functions and are on the private network. Both the NAT device and the devices that may be connected to the NAT device are identified and a determination is made of whether those devices are on the private network by sending requests using one or more protocols that devices on a private network conventionally use but are not conventionally used by devices on other networks.

Abstract: A wireless access point may be configured to advertise, to mobile user devices, multiple wireless networks available through the wireless access point. For example, service set identifiers (SSIDs) may be specified within an information element (IE) of a communication such as, for example, an 802.11 beacon, broadcasted to mobile user devices. Such an IE may utilize the capability provided by IEEE 802.11 itself to use additional and flexible numbers of information elements within a beacon. Accordingly, networks that would otherwise remain hidden due to limitations of known wireless access points are made visible to mobile user devices. Configuring a wireless access point to advertise multiple available wireless networks, for example, by firmware upgrades, may serve as a viable and cost-effective interim solution and/or alternative to replacing a wireless access point with a wireless access point configured to implement virtual wireless access points.

Abstract: A diagnostic tool for identifying a configuration of a private network that may disrupt operations involving communication between two devices on the network. The tool, when run on a device in the network, can identify a “double NAT” configuration in which the device may be separated from other devices on the private network by a NAT device. The tool, when run on a computing device, identifies a NAT device, such as a router, to which the device is connected. The tool then identifies a list containing one or more other devices that may be connected to the NAT device. The tool tests whether these other devices also perform NAT functions and are on the private network. Both the NAT device and the devices that may be connected to the NAT device are identified and a determination is made of whether those devices are on the private network by sending requests using one or more protocols that devices on a private network conventionally use but are not conventionally used by devices on other networks.

Abstract: To trace an activity through multiple components or applications that may be involved in the performance of the activity, an activity identifier can be generated and utilized by the various components or applications. Each can generate its own activity identifier to minimize changes to existing interfaces. When logging of events has been activated, each application or component can provide, to an event store, an indication of the activity identifier it is using for a given activity. If a preceding or subsequent component utilizes a different activity identifier for aspects of the same activity, a link between the two activity identifiers can be communicated to the event store. Subsequently, examination of the event store can filter out irrelevant entries based on the activity identifiers. A graph linking the various related activity identifiers can be created and only those events associated with activity identifiers not in the graph can be filtered out.

Abstract: A diagnostic tool for identifying a configuration of a private network that may disrupt operations involving communication between two devices on the network. The tool, when run on a device in the network, can identify a “double NAT” configuration in which the device may be separated from other devices on the private network by a NAT device. The tool, when run on a computing device, identifies a NAT device, such as a router, to which the device is connected. The tool then identifies a list containing one or more other devices that may be connected to the NAT device. The tool tests whether these other devices also perform NAT functions and are on the private network. Both the NAT device and the devices that may be connected to the NAT device are identified and a determination is made of whether those devices are on the private network by sending requests using one or more protocols that devices on a private network conventionally use but are not conventionally used by devices on other networks.

Abstract: A wireless access point may be configured to advertise, to mobile user devices, multiple wireless networks available through the wireless access point. For example, service set identifiers (SSIDs) may be specified within an information element (IE) of a communication such as, for example, an 802.11 beacon, broadcasted to mobile user devices. Such an IE may utilize the capability provided by IEEE 802.11 itself to use additional and flexible numbers of information elements within a beacon. Accordingly, networks that would otherwise remain hidden due to limitations of known wireless access points are made visible to mobile user devices. Configuring a wireless access point to advertise multiple available wireless networks, for example, by firmware upgrades, may serve as a viable and cost-effective interim solution and/or alternative to replacing a wireless access point with a wireless access point configured to implement virtual wireless access points.

Abstract: A diagnostic tool for identifying a configuration of a private network that may disrupt operations involving communication between two devices on the network. The tool, when run on a device in the network, can identify a “double NAT” configuration in which the device may be separated from other devices on the private network by a NAT device. The tool, when run on a computing device, identifies a NAT device, such as a router, to which the device is connected. The tool then identifies a list containing one or more other devices that may be connected to the NAT device. The tool tests whether these other devices also perform NAT functions and are on the private network. Both the NAT device and the devices that may be connected to the NAT device are identified and a determination is made of whether those devices are on the private network by sending requests using one or more protocols that devices on a private network conventionally use but are not conventionally used by devices on other networks.

Abstract: A wireless diagnostics framework that is non-intrusive and stays out of the way of a user is presented. In the case of a failure, prescriptive guidance is provided and/or the framework possibly automatically fixes the problem. The framework includes a wireless diagnostics module that interacts with the operating system's diagnostics framework, helper classes, and wireless components to collect and log wireless diagnostic events and notifications, and issues queries and requests for active diagnostics. The helper classes perform diagnosis and troubleshooting fore their expertise areas based on the information provided by the wireless diagnostics module.

Abstract: To trace an activity through multiple components or applications that may be involved in the performance of the activity, an activity identifier can be generated and utilized by the various components or applications. Each can generate its own activity identifier to minimize changes to existing interfaces. When logging of events has been activated, each application or component can provide, to an event store, an indication of the activity identifier it is using for a given activity. If a preceding or subsequent component utilizes a different activity identifier for aspects of the same activity, a link between the two activity identifiers can be communicated to the event store. Subsequently, examination of the event store can filter out irrelevant entries based on the activity identifiers. A graph linking the various related activity identifiers can be created and only those events associated with activity identifiers not in the graph can be filtered out.