SSDP Hack doesn't need wireless

wireless card removed and still hacked
I saw a UPN  CONNECTION VIA NETSTAT, everything transferred over.

http://msdn.microsoft.com/en-us/library/bb870632(VS.85).aspx

SSDP Provider

This topic has not yet been rated - Rate this topic[Function Discovery is available for use in the following versions of Windows: Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista. It may be altered or unavailable in subsequent versions.]The Simple Search and Discovery Protocol (SSDP) provider is an asynchronous Function Discovery provider that enumerates UPnP devices that use SSDP for discovery. Any UPnP device that supports SSDP for discovery and is compatible with the Microsoft SSDP media stack is discoverable by the SSDP provider. Once a device is discovered, the SSDP provider gets the device description document from the device, processes it, and returns a function instance that represents the root device.

Query Results

The SSDP provider supports collection queries and instance queries. This means that the provider supports both the IFunctionInstanceCollectionQuery::Execute and IFunctionInstanceQuery::Execute methods. Because the SSDP provider is asynchronous, Execute always returns E_PENDING for a successful query.When a query is executed, the provider sends a SSDP M-SEARCH request. This request is used to search for devices or device types that match the parameters specified in the Function Discovery query. The SSDP provider gets the description documents from devices that respond to the M-SEARCH request. After processing the description documents, the SSDP provider returns the function instances corresponding to the root devices. Although the description documents describe both services and devices, the services are ignored and only the devices are enumerated.Function instances are returned using theIFunctionDiscoveryNotification::OnUpdate method. Also, after the SSDP provider has finished enumerating resources, the provider sends a FD_EVENTID_SEARCHCOMPLETE notification using IFunctionDiscoveryNotification::OnEvent.After the initial query results have been returned, the SSDP provider continues to listen for messages from devices on the network. When a device sends a ssdp:alive message, the SSDP provider sends a QUA_ADD notification to the Function Discovery client. When a device sends a ssdp:byebye message, the SSDP provider sends a QUA_REMOVE notification to the Function Discovery client. This means that the client application is notified whenever a device comes online or goes offline until the client releases the query object by calling Release on the IFunctionInstanceCollectionQuery or on the IFunctionInstanceQuery object.Function Discovery applications can query the SSDP provider for different types of UPnP devices by specifying the PROVIDERSSDP_QUERYCONSTRAINT_TYPE query constraint. For more information, see the Query Constraints section below.If the SSDP provider finds a multi-function device in response to a query, the returned function instance corresponds to the root device. Applications can then call IFunctionInstance::QueryService on the returned function instance to get the collection of function instances corresponding to each child device. For multi-function devices, each child device corresponds to a function on the multi-function device.

Query Constraints

Query constraint can be added by calling IFunctionInstanceCollectionQuery::AddQueryConstraint on an IFunctionInstanceCollectionQuery object before executing the query.The following table shows the query constraints supported by the SSDP provider. The table also shows possible values to pass to the pszConstraintValue parameter of the AddQueryConstraint method.Note  The SSDP provider always returns function instances that correspond to the matching root devices. If a multi-function device has at least one child device that matches the specified query constraints, the function instance representing the root device is returned. An application must call IFunctionInstance::QueryService and pass the appropriate service identifier to get the function instances associated with the child devices. All child devices of the root device are returned, not just child devices that match the original query constraints.Constraint namePossible valuesRemarksFD_QUERYCONSTRAINT_PROVIDERINSTANCEIDA device UUID.This constraint limits query results to a single device. The SSDP provider returns a function instance representing the device matching the specified UUID, if there is such a device.This constraint takes precedence over all other query constraints. If this constraint is specified, all other query constraints are ignored.PROVIDERSSDP_QUERYCONSTRAINT_TYPEAny string corresponding to a device type supported by a SSDP device.This constraint limits query results to the specified UPnP device type. If this constraint is not specified, the SSDP provider searches for devices of type SSDP_CONSTRAINTVALUE_TYPE_ROOT.Some supported device type strings are predefined in FunctionDiscoveryConstraints.h. For a list of predefined types, see the SSDP_CONSTRAINTVALUE_TYPE_* constants in the topic Constraint Definitions. For more information about a named constraint, see Constraint Definitions. For general information about query constraints, see Constraints.

Notifications

Because the SSDP provider is asynchronous, a non-NULL IFunctionDiscoveryNotification pointer must be passed to the query creation method (either IFunctionDiscovery::CreateInstanceCollectionQuery or IFunctionDiscovery::CreateInstanceQuery). The SSDP provider will listen for ssdp:alive and ssdp:byebye messages and send QUA_ADD and QUA_REMOVE notifications to the IFunctionDiscoveryNotification interface as appropriate. An implementation of the IFunctionDiscoveryNotification::OnUpdate method should handle these two notifications. The QUA_CHANGE notification is not used.

Events

The FD_EVENTID_SEARCHCOMPLETE event is dispatched by the SSDP provider. This event notifies the application that the initial search for devices has been completed and that the application will receive function instances for added or removed devices that match the query constraints. The semantics are similar to IUPnPDeviceFinderCallback::SearchComplete. Applications that must return results synchronously can wait for this event to return the result set to their callers. For more information about FD_EVENTID_SEARCHCOMPLETE, see IFunctionDiscoveryNotification::OnEvent.

Services

The SSDP provider implements the SID_PNPXServiceCollection and SID_UPnPActivator services. The SSDP provider creates function instances that are returned by the SID_PNPXAssociation service.

SID_PNPXAssociation Service

Although the SSDP provider does not implement the SID_PNPXAssociation service, function instances created by the SSDP provider are returned when an application callsIFunctionInstance::QueryService on a function instance with the guidService parameter set to SID_PNPXAssociation and the riid parameter set to _uuidof(IPNPXAssociation).

SID_PNPXServiceCollection Service

The SSDP provider implements the SID_PNPXServiceCollection service.An application can use the SID_PNPXServiceCollection service to get the collection of child function instances (representing child devices) from a given function instance. To do this, the application calls IFunctionInstance::QueryService on a returned function instance with the guidService parameter set to SID_PNPXServiceCollection and the riid parameter set to _uuidof(IFunctionInstanceCollection). If a function instance does not have any child function instances, then an empty collection is returned.Although the UPnP device description document supports an arbitrary number of nested devices, the SSDP provider supports only one level of device nesting. That means that the collection of child devices returned by the SSDP provider is never nested. That means that direct children of the root device and children of these direct children appear in the same flat collection.

SID_UPnPActivator Service

The SSDP provider implements the SID_UPnPActivator service.An application can use the SID_UPnPActivator service to get the IUPnPDevice interface associated with a given function instance. To do this, the application calls IFunctionInstance::QueryService on a returned function instance with the guidService parameter set to SID_PNPXServiceCollection and the riid parameter set to _uuidof(IUPnPDevice).

Property Store

The SSDP provider implements read-only property stores.The IFunctionInstance::OpenPropertyStore method can be used to access the property keys (PKEYs) associated with a function instance. The methods of the IPropertyStoreinterface can be used to get the PKEYs associated with the function instance.

Supported PKEYs

The following PnP-X PKEYs are supported by the SSDP provider.PKEY_Device_CompatibleIdsPKEY_Device_DeviceDescPKEY_Device_FriendlyNamePKEY_Device_HardwareIdsPKEY_Device_LocationInfoPKEY_Device_ManufacturerPKEY_Device_ModelPKEY_DriverPackage_VendorWebSitePKEY_PNPX_CompatibleIdsPKEY_PNPX_CompatibleTypesPKEY_PNPX_DeviceCategoryPKEY_PNPX_FriendlyNamePKEY_PNPX_GlobalIdentityPKEY_PNPX_HardwareIdsPKEY_PNPX_IDPKEY_PNPX_InstallablePKEY_PNPX_IpAddressPKEY_PNPX_ManufacturerPKEY_PNPX_ManufacturerUrlPKEY_PNPX_ModelNamePKEY_PNPX_ModelNumberPKEY_PNPX_ModelUrlPKEY_PNPX_NetworkInterfaceGuidPKEY_PNPX_PhysicalAddressPKEY_PNPX_PresentationUrlPKEY_PNPX_SerialNumberPKEY_PNPX_TypesPKEY_PNPX_UpcPKEY_PNPX_XAddrsFor more information about these PKEYs, see PnP-X Provider PKEYs. For information about SSDP device metadata requirements in general, and also for information about the relationship between UPnP device elements and PKEYs, see PnP-X: Plug and Play Extensions for Windows Specification.

Related topics

Built-in Providers  Send comments about this topic to MicrosoftBuild date: 10/26/2012Did you find this helpful? Yes No

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/244d8984-be66-46ac-a732-d155dd16b38e/