DonatShell
Server IP : 180.180.241.3  /  Your IP : 216.73.216.252
Web Server : Microsoft-IIS/7.5
System : Windows NT NETWORK-NHRC 6.1 build 7601 (Windows Server 2008 R2 Standard Edition Service Pack 1) i586
User : IUSR ( 0)
PHP Version : 5.3.28
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /Windows/SysWOW64/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME SHELL ]     

Current File : /Windows/SysWOW64/en-US/FirewallAPI.dll.mui
MZ@	!L!This program cannot be run in DOS mode.

$uEEELlDLl
DRichEPEL՜L!	>@<.rsrc@@x(@h i8Ph(@Xp0H`x ! "8+P.h/013456	Z(	[@	\X	]p	^	_	`	a	b	c

0
H
`
x





 %8&P4h5DETcdst(@Xp

0
H
`
x





 8Ph(@.X/p>?@N]^m}0HH	`W	xg	w	}					 	8	P	h	

"
2
B
Q
q
(
@
X
p




		(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h	x											(	8	H	X	h,0-x-.X/X023489>bPEHLSpY>\^>diF	rtt z @{$|LpdXЅBH\r\(Jtrijp̺txp\fdbtDJ
hvx@$,4`\2*pDXVL	

*$X%)p**.>4x:?BHE4GHOPDUZ,[\x`fclLg$kmnTs(w@x{ph؃`|܊\0N,dĨx` Z|tx 8(4\8@.@:MUI.a9\`tsrkGWJs+2
MUIen-US!Firewall log files (*.log)*.logBrowselog[The value entered for the log file size is not valid. Enter a value between 1 and 32767 k.PAFile and Printer SharingNetBIOS Name ServiceNetBIOS Datagram ServiceNetBIOS Session Service
SMB over TCPUPnP Framework!SSDP Component of UPnP FrameworkUPnP Framework over TCPRemote DesktopDomain Name Server (DNS)2Dynamic Host Configuration Protocol Server (DHCP)2Dynamic Host Configuration Protocol Client (DHCP)Incoming Connection VPN (PPTP)Incoming Connection VPN (L2TP)IP Security (IPsec - IKE) IP Security (IPsec - IKE/NAT-T)1Phase 1: Local address = %s, Remote address = %s1Phase 2: Local address = %s, Remote address = %s, Protocol = 0x%x, Protocol = Any, Local port = 0x%x, Local port = Any, Remote port = 0x%x, Remote port = AnyPAWindows FirewallWindows Firewall helps protect your computer by preventing unauthorized users from gaining access to your computer through the Internet or a network.&Windows Firewall Authorization DriverWindows Firewall Authorization Driver is a kernel mode driver that provides deep inspection services on inbound and outbound network traffic.!Allow authenticated IPsec bypass[Allows specific computers to have unrestricted, but authenticated, access to the computer.YesNoEnabled	DisabledPA
Group Policy
Local PolicyGroup and Local PolicyDomainPrivateAll interfacesOffOnDon't allow exceptionsAll subnetsLocal subnet onlyCustom subnetsAddRemoveModify'Allow outgoing destination unreachablePAAllow outgoing source quenchAllow redirectAllow incoming echo requestAllow incoming router requestAllow outgoing time exceeded!Allow outgoing parameter problem!Allow incoming timestamp requestAllow incoming mask requestAllow outgoing packet too big0The rule was parsed successfully from the store=The rule has fields that the service can successfully ignore;The rule has a higher version that the service must ignore/The name contains invalid characters or length6The description contains invalid characters or length6The application contains invalid characters or length2The service contains invalid characters or lengthJThe authorized remote machines list contains invalid characters or lengthGThe authorized remote users list contains invalid characters or length;The embedded context contains invalid characters or length'The rule failed to be parsed correctlyMA semantic error: End smaller than Begin, or the port specified was zero (0)EA property on Remote Addresses does not belong to the Remote Address6Number of interfaces and interface buffer don't match!Invalid interface type specified A rule must have a valid action&A rule must include a valid directionPA semantic error because the protocol and protocol dependent fields don't matchQThere is a semantic error when considering the fields of the rule in conjunctionAn error occurredEnable Windows FirewallDisable Stealth ModeWindows Firewall Shielded ModePA'Disable Unicast Responses to MulticastLog Dropped PacketsLog Successful ConnectionsLog Ignored RulesMaximum Log File SizeLog File PathDisable Inbound Notifications6Allow User preferred merge of Authorized Applications2Allow User preferred merge of Globally open portsAllow Local Policy MergeAllow Local IPsec Policy MergeDisabled InterfacesDefault Outbound ActionDefault Inbound ActionCurrent ProfileDisable Stateful FTPIgnored Disable Stateful PPTPIPsec SA Idle timeIPsec preshared key encoding
IPsec ExemptIPsec CRL Check<All>AllowBlock2The rule Id contains invalid characters or length=The Phase1 auth set Id contains invalid characters or length?The Phase2 crypto set Id contains invalid characters or length=The Phase2 auth set Id contains invalid characters or length+The application name could not be resolvedRuleId not specified-Mismatch in number of ports and ports bufferInvalid port keyword<Mismatch in number of V4 address subnets and subnets buffer<Mismatch in number of V6 address subnets and subnets buffer:Mismatch in number of V4 address ranges and ranges buffer:Mismatch in number of V6 address ranges and ranges buffer%Address range end is less than begin&Invalid Mask specified on a v4 SubNet(Invalid prefix specified on a V6 subnet)An invalid address keyword was specifiedBA property on Local Addresses does not belong to the LocalAddress+Mismatch in number of ICMP and ICMP bufferInvalid ICMP code specifiedAllow-Bypass action specified, but the rule does not meet allow-bypass criteria (inbound, authenticate/encrypt flags set, remote machine auth list specified)Invalid protocol specifiedInvalid flags specifiedOAutogenerate flag is set but Authenticate / Authenticate-encrypt flags not set1Autogenerate flag is set but the action is block5Autogenerate flag is set along with Dynamic RPC flag;Authenticate and Authenticate-encrypt flags both specified^Authorized remote machines or users list specified, but authenticate/encryption flags not setLNumber of valid OS Platforms and the list of valid OS Platforms don't match!Phase1 auth set Id not specified#Phase2 crypto set Id not specifiedSet Id not specifiedInvalid IPsec phase specifiedNo suites specified in the setInvalid Phase1 auth methodInvalid Phase2 auth method7Anonymous auth specified as sole auth proposal (suite)#Invalid auth suite flags specified1Machine cert must be Health cert for phase2 auth!Machine Shared Key not specifiedCA name not specified%Both machine and user auth specified)Phase 1 crypto set id is not the default Invalid Phase1 crypto set flags*Invalid Phase1 crypto set timeout minutes+Invalid Phase1 crypto set timeout sessions'Invalid Phase1 crypto set key exchange%Invalid Phase1 crypto set encryptionInvalid Phase1 crypto set hashInvalid Phase2 crypto set PFS#Invalid Phase2 crypto set protocol%Invalid Phase2 crypto set encryptionInvalid Phase2 crypto set hash*Invalid Phase2 crypto set timeout seconds)Invalid Phase2 crypto set timeout KBytes=Authorized remote users list specified on outbound directionLAn unspecified, multicast, broadcast or loopback Ipv6 address was specifiedPAJDoNotSecure action specified along with authentication and/or crypto sets4Crypto suite encryption and hash both not specifiedVBlock action was specified in conjunction with require security or require encryption,Main Mode authentication set was not found.-Quick Mode authentication set was not found.+Quick Mode cryptographic set was not foundSpecified Main Mode authentication set and Quick Mode authentication set contradict. Quick Mode authentication set cannot be specified when the Main Mode authentication set contains a pre-shared key as an authentication method.YA local address cannot be used in conjunction with either an interface or interface type
Program NameInterfacesLocal AddressesRemote AddressesLocal PortRemote PortEndPoint 1 AddressesEndPoint 2 AddressesPAEndpoint 1 PortEndpoint 2 PortNot ConfiguredInvalid Profile Type specifiedPublicLAn unspecified, multicast, broadcast or loopback Ipv4 address was specified=Health certs cannot be specified together with regular certsNone:Endpoint 'any' cannot be specified for a tunnel mode ruleIPsec Through NATPolicy VersionESchema version specified is lesser than the schema version supported4Duplicate auth methods not supported yet specified.TAll certificates from same CA type within a signing block must be grouped together.Port range is not supportedEAuthenticate-DynamicEncrypt flag is not valid for outbound directionIAuthenticate-DynamicEncrypt flag is set but Authenticate flag is not set2Authenticate-DynamicEncrypt flag is not supported%Allow-Bypass action is not supportedqAllow-Bypass action specified, but the rule does not meet allow-bypass criteria (authenticate/encrypt flags set)'Defer to user' setting can only be used in a firewall rule where program path and TCP/UDP protocol are specified with no additional scopesgA semantic error because port range is used when the connection security rule is not an exemption ruleASchema version does not support the platform operator specified.?DTM rule specified but all tunnel endpoints are also specifiedZA DTM tunnel exemption rule cannot be specified with tunnel endpoint (gateways) addresses7Schema version does not support Tunnel mode exemptionseAuthentication mode "Require inbound and clear outbound" can only be set when using IPSec tunneling.Q"Exempt IPsec protected connections" can only be set when using IPSec tunneling.+An invalid platform operator was specified'%s unregistered from Windows Firewall.a%s unregistered from Windows Firewall. Windows Firewall is now controlling the filtering for %s.FirewallRuleCategoryPAConSecRuleCategoryStealthRuleCategoryBootTimeRuleCategory, 7AuthNoEncap cannot be specified on a tunnel mode rule.EAuthNoEncap cannot be specified on a rule that uses a preshared key.PA0IPsec Policy Agent service hardening - LDAP/TCPGAllow IPsec Policy Agent outbound LDAP/TCP traffic to Active Directory0IPsec Policy Agent service hardening - LDAP/UDPGAllow IPsec Policy Agent outbound LDAP/UDP traffic to Active DirectoryUIPsec Policy Agent service hardening - Block any other traffic to IPsec Policy AgentWIPsec Policy Agent service hardening - Block any other traffic from IPsec Policy Agent=MpsSvc service hardening - Block any other traffic to MpsSvc?MpsSvc service hardening - Block any other traffic from MpsSvc+Inbound service restriction rule for %1!s!+Block all inbound traffic to service %1!s!,Outbound service restriction rule for %1!s!.Block all outbound traffic from service %1!s!9IPsec Policy Agent service hardening - Remote ManagementGAllow IPsec Policy Agent inbound RPC/TCP traffic for Remote ManagementmpssvcMicrosoft Corporation$Microsoft Windows Firewall Provider Windows Firewall Static SessionPA!Windows Firewall Dynamic SessionBoot Time Filter4This filter is in effect before the service starts.Logging Filter/This filter implements logging, if configured. Port Scanning Prevention Filter$This filter prevents port scanning.Loopback Permit Filter&This filter permits loopback traffic.Secondary Connections Filter=This filter permits secondary connections for FTP protocols. Deep Protocol Inspection Filter:This filter implements deep inspection for FTP protocols.FTP Inspection Filter'This filter enables inspection of FTP.Microsoft Corporation*Microsoft Windows Firewall IPsec ProviderState Management FilterMIndicates different options to WFP to allow customization of state creation."State Management Provider Context"Contains State Management OptionsPAUPnP Framework (TCP-In).Inbound rule for UPnP Framework traffic [TCP]UPnP Framework (TCP-Out)/Outbound rule for UPnP Framework traffic [TCP]UPnP Framework (UDP-In).Inbound rule for UPnP Framework traffic [UDP]UPnP Framework (UDP-Out)/Outbound rule for UPnP Framework traffic [UDP](Windows Firewall with Advanced SecurityQConfigure policies that provide enhanced network security for Windows computers.PACore Networking-Core Networking - Packet Too Big (ICMPv6-In).Core Networking - Packet Too Big (ICMPv6-Out)Packet Too Big error messages are sent from any node that a packet traverses which is unable to forward the packet because the packet is too large for the next link.PA3Core Networking - Router Solicitation (ICMPv6-Out)2Core Networking - Router Solicitation (ICMPv6-In)hRouter Solicitation messages are sent by nodes seeking routers to provide stateless auto-configuration.3Core Networking - Router Advertisement (ICMPv6-In)4Core Networking - Router Advertisement (ICMPv6-Out)cRouter Advertisement messages are sent by routers to other nodes for stateless auto-configuration.>Core Networking - Neighbor Discovery Solicitation (ICMPv6-In)?Core Networking - Neighbor Discovery Solicitation (ICMPv6-Out)tNeighbor Discovery Solicitations are sent by nodes to discover the link-layer address of another on-link IPv6 node.?Core Networking - Neighbor Discovery Advertisement (ICMPv6-In)@Core Networking - Neighbor Discovery Advertisement (ICMPv6-Out)Neighbor Discovery Advertisement messages are sent by nodes to notify other nodes of link-layer address changes or in response to a Neighbor Discovery Solicitation request.FCore Networking - Inverse Neighbor Discovery Solicitation (ICMPv6-In)GCore Networking - Inverse Neighbor Discovery Solicitation (ICMPv6-Out)Inverse Neighbor Discovery Solicitations are sent by nodes to discover the IP address of another IPv6 node given its link-layer address.GCore Networking - Inverse Neighbor Discovery Advertisement (ICMPv6-In)HCore Networking - Inverse Neighbor Discovery Advertisement (ICMPv6-Out)Inverse Neighbor Discovery Solicitations are sent by nodes to notify other nodes of IP address changes or in response to an Inverse Neighbor Discovery Solicitation request.<Core Networking - Certificate Path Solicitation (ICMPv6-In)=Core Networking - Certificate Path Solicitation (ICMPv6-Out)ySEND - Secure Neighbor Discovery - Certificate Path Solicitation is a secure version of Neighbor Discovery Solicitation.=Core Networking - Certificate Path Advertisement (ICMPv6-In)>Core Networking - Certificate Path Advertisement (ICMPv6-Out)PA{SEND - Secure Neighbor Discovery - Certificate Path Advertisement is a secure version of Neighbor Discovery Advertisement.7Core Networking - Multicast Listener Query (ICMPv6-In)8Core Networking - Multicast Listener Query (ICMPv6-Out){An IPv6 multicast-capable router uses the Multicast Listener Query message to query a link for multicast group membership.8Core Networking - Multicast Listener Report (ICMPv6-In)9Core Networking - Multicast Listener Report (ICMPv6-Out)The Multicast Listener Report message is used by a listening node to either immediately report its interest in receiving multicast traffic at a specific multicast address or in response to a Multicast Listener Query.;Core Networking - Multicast Listener Report v2 (ICMPv6-In)<Core Networking - Multicast Listener Report v2 (ICMPv6-Out)Multicast Listener Report v2 message is used by a listening node to either immediately report its interest in receiving multicast traffic at a specific multicast address or in response to a Multicast Listener Query.6Core Networking - Multicast Listener Done (ICMPv6-In)7Core Networking - Multicast Listener Done (ICMPv6-Out)PAMulticast Listener Done messages inform local routers that there are no longer any members remaining for a specific multicast address on the subnet.=Core Networking - Multicast Router Advertisement (ICMPv6-In)>Core Networking - Multicast Router Advertisement (ICMPv6-Out)rMulticast Router Advertisement messages are sent by routers to advertise that IP multicast forwarding is enabled.<Core Networking - Multicast Router Solicitation (ICMPv6-In)=Core Networking - Multicast Router Solicitation (ICMPv6-Out)sMulticast Router Solicitation messages are sent in order to discover routers with IP multicast forwarding enabled.;Core Networking - Multicast Router Termination (ICMPv6-In)PA<Core Networking - Multicast Router Termination (ICMPv6-Out)sMulticast Router Termination messages are sent when a router stops IP multicast routing functions on an interface.6Core Networking - Destination Unreachable (ICMPv6-In)7Core Networking - Destination Unreachable (ICMPv6-Out)Destination Unreachable error messages are sent from any node that a packet traverses which is unable to forward the packet for any reason except congestion.,Core Networking - Time Exceeded (ICMPv6-In)-Core Networking - Time Exceeded (ICMPv6-Out)Time Exceeded error messages are generated from any node that a packet traverses if the Hop Limit value is decremented to zero at any point on the path.0Core Networking - Parameter Problem (ICMPv6-In)1Core Networking - Parameter Problem (ICMPv6-Out)aParameter Problem error messages are sent by nodes as a result of incorrectly generated packets.KCore Networking - Destination Unreachable Fragmentation Needed (ICMPv4-In)LCore Networking - Destination Unreachable Fragmentation Needed (ICMPv4-Out)Destination Unreachable Fragmentation Needed error messages are sent from any node that a packet traverses which is unable to forward the packet because fragmentation was needed and the don t fragment bit was set.PA@Core Networking - Dynamic Host Configuration Protocol (DHCP-In)ACore Networking - Dynamic Host Configuration Protocol (DHCP-Out)\Allows DHCP (Dynamic Host Configuration Protocol) messages for stateful auto-configuration.JCore Networking - Dynamic Host Configuration Protocol for IPv6(DHCPV6-In)KCore Networking - Dynamic Host Configuration Protocol for IPv6(DHCPV6-Out)pAllows DHCPV6 (Dynamic Host Configuration Protocol for IPv6) messages for stateful and stateless configuration."Core Networking - Teredo (UDP-In)#Core Networking - Teredo (UDP-Out)PAInbound UDP rule to allow Teredo edge traversal, a technology that provides address assignment and automatic tunneling for unicast IPv6 traffic when an IPv6/IPv4 host is located behind an IPv4 network address translator.Outbound UDP rule to allow Teredo edge traversal, a technology that provides address assignment and automatic tunneling for unicast IPv6 traffic when an IPv6/IPv4 host is located behind an IPv4 network address translator.PA!Core Networking - IPv6 (IPv6-In)"Core Networking - IPv6 (IPv6-Out)Inbound rule required to permit IPv6 traffic for ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) and 6to4 tunneling services.Outbound rule required to permit IPv6 traffic for ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) and 6to4 tunneling services.?Core Networking - Internet Group Management Protocol (IGMP-In)@Core Networking - Internet Group Management Protocol (IGMP-Out)ZIGMP messages are sent and received by nodes to create, join and depart multicast groups.PA(Core Networking - Group Policy (NP-Out)GOutbound rule to allow SMB traffic for Group Policy updates. [TCP 445])Core Networking - Group Policy (TCP-Out)JOutbound rule to allow remote RPC traffic for Group Policy updates. [TCP] Core Networking - DNS (UDP-Out)Outbound rule to allow DNS requests. DNS responses based on requests that matched this rule will be permitted regardless of source address.  This behavior is classified as loose source mapping. [LSM] [UDP 53]+Core Networking - Group Policy (LSASS-Out)LOutbound rule to allow remote LSASS traffic for Group Policy updates [TCP].#Core Networking - IPHTTPS (TCP-In)$Core Networking - IPHTTPS (TCP-Out)rInbound TCP rule to allow IPHTTPS tunneling technology to provide connectivity across HTTP proxies and firewalls.sOutbound TCP rule to allow IPHTTPS tunneling technology to provide connectivity across HTTP proxies and firewalls.1Networking - Destination Unreachable (ICMPv4-In)2Networking - Destination Unreachable (ICMPv4-Out)Destination Unreachable error messages are sent from any node that a packet traverses which is unable to forward the packet for any reason except congestion.'Networking - Source Quench (ICMPv4-In)(Networking - Source Quench (ICMPv4-Out)Source Quench messages are sent from any node that a packet traverses which discards the datagram because they are arriving too fast or there are buffering issues."Networking - Redirect (ICMPv4-In)#Networking - Redirect (ICMPv4-Out)Redirect messages are sent to indicate that the node which the packet was sent to is no longer the best gateway to reach the network in question.PA'Networking - Time Exceeded (ICMPv4-In)(Networking - Time Exceeded (ICMPv4-Out)Time Exceeded error messages are generated from any node which a packet traverses if the Hop Limit value is decremented to zero at any point on the path.+Networking - Timestamp Request (ICMPv4-In),Networking - Timestamp Request (ICMPv4-Out)iTimestamp Request messages are sent by nodes who wish to obtain the current timestamp from another node.+Networking - Parameter Problem (ICMPv4-In),Networking - Parameter Problem (ICMPv4-Out)aParameter Problem error messages are sent by nodes as a result of incorrectly generated packets.PA"Networking - Redirect (ICMPv6-In)#Networking - Redirect (ICMPv6-Out)PARedirect messages are sent to indicate that the node which the packet was sent to is no longer the best gateway to reach the network in question.-Networking - Router Solicitation (ICMPv6-In)hRouter Solicitation messages are sent by nodes seeking routers to provide stateless auto-configuration.PA4Networking - Generic Routing Encapsulation (GRE-In)5Networking - Generic Routing Encapsulation (GRE-Out)Generic Routing Encapsulation is used for encapsulation of an arbitrary network layer protocol over another arbitrary network layer protocol.6Networking - PGM Reliable Transport Protocol (PGM-In)7Networking - PGM Reliable Transport Protocol (PGM-Out)Pragmatic General Multicast is a reliable multicast transport protocol used for applications that require ordered or unordered, duplicate-free, multicast data delivery from multiple sources to multiple receivers.(Networking - Packet Too Big (ICMPv4-In))Networking - Packet Too Big (ICMPv4-Out)Packet Too Big error messages are sent from any node that a packet traverses which is unable to forward the packet because the packet is too large for the next link.-Networking - Router Solicitation (ICMPv4-In).Networking - Router Solicitation (ICMPv4-Out)hRouter Solicitation messages are sent by nodes seeking routers to provide stateless auto-configuration..Networking - Address Mask Request (ICMPv4-In)/Networking - Address Mask Request (ICMPv4-Out)oAddress Mask Request messages are sent by nodes who wish to obtain the subnet mask for their assigned address.&Networking - Echo Request (ICMPv4-In)'Networking - Echo Request (ICMPv4-Out)&Networking - Echo Request (ICMPv6-In)'Networking - Echo Request (ICMPv6-Out)PA@Echo Request messages are sent as ping requests to other nodes.Key Management Service Key Management Service (TCP-In)mInbound rule for the Key Management Service to allow for machine counting and license compliance. [TCP 1688]BITS PeercachingBITS Peercaching (WSD-In)PAdInbound rule for BITS Peercaching to discover neighbors who may have content via WSDAPI. [UDP 3702]BITS Peercaching (WSD-Out)eOutbound rule for BITS Peercaching to discover neighbors who may have content via WSDAPI. [UDP 3702]BITS Peercaching (Content-In)DInbound rule for BITS Peercaching content transfer port. [TCP 2178]BITS Peercaching (Content-Out)EOutbound rule for BITS Peercaching content transfer port. [TCP 2178]BITS Peercaching (RPC)PARInbound rule for the Peercaching authorization exchange port via dynamic RPC/TCP.BITS Peercaching (RPC-EPMAP)[Inbound rule for the RPCSS service in order to allow RPC/TCP traffic for BITS Peercaching.File and Printer Sharing)File and Printer Sharing (NB-Session-In)bInbound rule for File and Printer Sharing to allow NetBIOS Session Service connections. [TCP 139]*File and Printer Sharing (NB-Session-Out)cOutbound rule for File and Printer Sharing to allow NetBIOS Session Service connections. [TCP 139]"File and Printer Sharing (SMB-In)PA~Inbound rule for File and Printer Sharing to allow Server Message Block transmission and reception via Named Pipes. [TCP 445]#File and Printer Sharing (SMB-Out)Outbound rule for File and Printer Sharing to allow Server Message Block transmission and reception via Named Pipes. [TCP 445]&File and Printer Sharing (NB-Name-In)VInbound rule for File and Printer Sharing to allow NetBIOS Name Resolution. [UDP 137]'File and Printer Sharing (NB-Name-Out)WOutbound rule for File and Printer Sharing to allow NetBIOS Name Resolution. [UDP 137]*File and Printer Sharing (NB-Datagram-In)jInbound rule for File and Printer Sharing to allow NetBIOS Datagram transmission and reception. [UDP 138]+File and Printer Sharing (NB-Datagram-Out)kOutbound rule for File and Printer Sharing to allow NetBIOS Datagram transmission and reception. [UDP 138]1File and Printer Sharing (Spooler Service - RPC)iInbound rule for File and Printer Sharing to allow the Print Spooler Service to communicate via TCP/RPC.7File and Printer Sharing (Spooler Service - RPC-EPMAP)UInbound rule for the RPCSS service to allow RPC/TCP traffic for the Spooler Service.4File and Printer Sharing (Echo Request - ICMPv4-In)5File and Printer Sharing (Echo Request - ICMPv4-Out)4File and Printer Sharing (Echo Request - ICMPv6-In)5File and Printer Sharing (Echo Request - ICMPv6-Out)@Echo Request messages are sent as ping requests to other nodes.(File and Printer Sharing (LLMNR-UDP-In)dInbound rule for File and Printer Sharing to allow Link Local Multicast Name Resolution. [UDP 5355])File and Printer Sharing (LLMNR-UDP-Out)eOutbound rule for File and Printer Sharing to allow Link Local Multicast Name Resolution. [UDP 5355]Remote DesktopRemote Desktop (TCP-In)MInbound rule for the Remote Desktop service to allow RDP traffic. [TCP 3389]Remote Desktop - RemoteFX#Remote Desktop - RemoteFX (TCP-In)MInbound rule for the Remote Desktop service to allow RDP traffic. [TCP 3389]iSCSI ServiceiSCSI Service (TCP-In)aInbound rule for the iSCSI Service to allow communications with an iSCSI server or device. [TCP]iSCSI Service (TCP-Out)bOutbound rule for the iSCSI Service to allow communications with an iSCSI server or device. [TCP]Remote Event Log Management"Remote Event Log Management (RPC)QInbound rule for the local Event Log service to be remotely managed via RPC/TCP.$Remote Event Log Management (NP-In)VInbound rule for the local Event Log service to be remotely managed over Named Pipes.PA(Remote Event Log Management (RPC-EPMAP)]Inbound rule for the RPCSS service to allow RPC/TCP traffic for the local Event Log Service.PARemote Service Management Remote Service Management (RPC)WInbound rule for the local Service Control Manager to be remotely managed via RPC/TCP."Remote Service Management (NP-In)\Inbound rule for the local Service Control Manager to be remotely managed over Named Pipes.&Remote Service Management (RPC-EPMAP)cInbound rule for the RPCSS service to allow RPC/TCP traffic for the local Service Control Manager.Remote AdministrationRemote Administration (RPC)BInbound rule for all services to be remotely managed via RPC/TCP.Remote Administration (NP-In)GInbound rule for all services to be remotely managed over Named Pipes."Remote Administration (RPC-EPMAP)XInbound rule for the RPCSS service to allow RPC/TCP traffic for all the local services.PA#Windows Firewall Remote Management)Windows Firewall Remote Management (RPC)JInbound rule for the Windows Firewall to be remotely managed via RPC/TCP./Windows Firewall Remote Management (RPC-EPMAP)VInbound rule for the RPCSS service to allow RPC/TCP traffic for the Windows Firewall.PAWindows Remote Management$Windows Remote Management (HTTP-In)IInbound rule for Windows Remote Management via WS-Management. [TCP 5985]PAWireless Portable Devices$Wireless Portable Devices (TCP-Out)aOutbound rule for Wireless Portable Devices to allow use of the Usermode Driver Framework. [TCP]$Wireless Portable Devices (SSDP-In)mInbound rule for Wireless Portable Devices to allow use of the Simple Service Discovery Protocol. [UDP 1900]%Wireless Portable Devices (SSDP-Out)PAnOutbound rule for Wireless Portable Devices to allow use of the Simple Service Discovery Protocol. [UDP 1900]$Wireless Portable Devices (UPnP-In)_Inbound rule for Wireless Portable Devices to allow use of Universal Plug and Play. [TCP 2869]%Wireless Portable Devices (UPnP-Out)[Outbound rule for Wireless Portable Devices to allow use of Universal Plug and Play. [TCP])Wireless Portable Devices (UPnPHost-Out)[Outbound rule for Wireless Portable Devices to allow use of Universal Plug and Play. [TCP]PAMedia Center Extenders'Media Center Extenders - SSDP (UDP-In)jInbound rule for Media Center Extenders to allow use of the Simple Service Discovery Protocol. [UDP 1900](Media Center Extenders - SSDP (UDP-Out)kOutbound rule for Media Center Extenders to allow use of the Simple Service Discovery Protocol. [UDP 1900]'Media Center Extenders - RTSP (TCP-In)[Inbound rule for Media Center Extenders to allow RTSP AV Control. [TCP 554, TCP 8554-8558](Media Center Extenders - RTSP (TCP-Out)PAVOutbound rule for Media Center Extenders to allow WMDRM-ND and RTSP AV Control. [TCP](Media Center Extenders - qWave (UDP-In)wInbound rule for Media Center Extenders to allow use of the Quality Windows Audio Video Experience Service. [UDP 2177])Media Center Extenders - qWave (UDP-Out)xOutbound rule for Media Center Extenders to allow use of the Quality Windows Audio Video Experience Service. [UDP 2177](Media Center Extenders - qWave (TCP-In)wInbound rule for Media Center Extenders to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177])Media Center Extenders - qWave (TCP-Out)xOutbound rule for Media Center Extenders to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177]1Media Center Extenders - HTTP Streaming (TCP-In)SInbound rule for Media Center Extenders to allow HTTP Media Streaming. [TCP 10244]&Media Center Extenders - XSP (TCP-In)OInbound rule for Media Center Extenders to allow terminal sessions. [TCP 3390]PA4Media Center Extenders - WMDRM-ND/RTP/RTCP (UDP-In)Inbound rule for Media Center Extenders to allow WMDRM-ND and RTP/RTCP AV Streaming. [UDP 7777-7781, UDP 5004-5005, UDP 50004-50013]5Media Center Extenders - WMDRM-ND/RTP/RTCP (UDP-Out)\Outbound rule for Media Center Extenders to allow WMDRM-ND and RTP/RTCP AV Streaming. [UDP]+Media Center Extenders - Service (TCP-Out)pOutbound rule for Media Center Extenders to allow extender devices to locate and connect to the computer. [TCP]7Media Center Extenders - Device Provisioning (TCP-Out)YOutbound rule for Media Center Extenders to allow traffic for Device Provisioning. [TCP]2Media Center Extenders - Media Streaming (TCP-In)^Inbound rule for Media Center Extenders to allow UPnP traffic for Media Streaming. [TCP 2869]PA3Media Center Extenders - Media Streaming (TCP-Out)ZOutbound rule for Media Center Extenders to allow UPnP traffic for Media Streaming. [TCP]5Media Center Extenders - Device Validation (TCP-Out)WOutbound rule for Media Center Extenders to allow traffic for Device Validation. [TCP]3Media Center Extenders - Media Streaming (UDP-Out)sOutbound rule for Media Center Extenders to allow Media Streaming devices to respond to an SSDP search. [UDP 1900](Media Center Extenders - UPnP (TCP-Out)eOutbound rule for Media Center Extenders to allow UPnP devices to transmit device information. [TCP]Windows Media PlayerWindows Media Player (UDP-In)JInbound rule for Windows Media Player to allow UDP Media Streaming. [UDP]Windows Media Player (UDP-Out)KOutbound rule for Windows Media Player to allow UDP Media Streaming. [UDP]Windows Media Player (TCP-Out)POutbound rule for Windows Media Player to allow TCP/HTTP Media Streaming. [TCP]DWindows Media Player - Internet Group Management Protocol (IGMP-In)>Inbound rule for Windows Media Player to allow IGMP messages.EWindows Media Player - Internet Group Management Protocol (IGMP-Out)?Outbound rule for Windows Media Player to allow IGMP messages."Windows Media Player x86 (UDP-In)#Windows Media Player x86 (UDP-Out)#Windows Media Player x86 (TCP-Out)-Windows Media Player Network Sharing Service<Windows Media Player Network Sharing Service (qWave-UDP-In)Inbound rule for the Windows Media Player Network Sharing Service to allow use of the Quality Windows Audio Video Experience Service. [UDP 2177]=Windows Media Player Network Sharing Service (qWave-UDP-Out)Outbound rule for the Windows Media Player Network Sharing Service to allow use of the Quality Windows Audio Video Experience Service. [UDP 2177]<Windows Media Player Network Sharing Service (qWave-TCP-In)PAInbound rule for the Windows Media Player Network Sharing Service to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177]=Windows Media Player Network Sharing Service (qWave-TCP-Out)Outbound rule for the Windows Media Player Network Sharing Service to allow use of the Quality Windows Audio Video Experience Service. [TCP 2177]7Windows Media Player Network Sharing Service (SSDP-In)Inbound rule for the Windows Media Player Network Sharing Service to allow use of the Simple Service Discovery Protocol. [UDP 1900]8Windows Media Player Network Sharing Service (SSDP-Out)Outbound rule for the Windows Media Player Network Sharing Service to allow use of the Simple Service Discovery Protocol. [UDP 1900]7Windows Media Player Network Sharing Service (UPnP-In)PAvInbound rule for the Windows Media Player Network Sharing Service to allow use of Universal Plug and Play. [TCP 2869]8Windows Media Player Network Sharing Service (UPnP-Out)rOutbound rule for the Windows Media Player Network Sharing Service to allow use of Universal Plug and Play. [TCP]AWindows Media Player Network Sharing Service (HTTP-Streaming-In)mInbound rule for the Windows Media Player Network Sharing Service to allow HTTP Media Streaming. [TCP 10243]BWindows Media Player Network Sharing Service (HTTP-Streaming-Out)nOutbound rule for the Windows Media Player Network Sharing Service to allow HTTP Media Streaming. [TCP 10243]@Windows Media Player Network Sharing Service (Streaming-UDP-In)JInbound rule for Windows Media Player to allow UDP Media Streaming. [UDP]AWindows Media Player Network Sharing Service (Streaming-UDP-Out)KOutbound rule for Windows Media Player to allow UDP Media Streaming. [UDP]AWindows Media Player Network Sharing Service (Streaming-TCP-Out)POutbound rule for Windows Media Player to allow TCP/HTTP Media Streaming. [TCP]6Windows Media Player Network Sharing Service (UDP-In)bInbound rule for the Windows Media Player Network Sharing Service to allow sharing traffic. [UDP]7Windows Media Player Network Sharing Service (UDP-Out)cOutbound rule for the Windows Media Player Network Sharing Service to allow sharing traffic. [UDP]6Windows Media Player Network Sharing Service (TCP-In)bInbound rule for the Windows Media Player Network Sharing Service to allow sharing traffic. [TCP]7Windows Media Player Network Sharing Service (TCP-Out)cOutbound rule for the Windows Media Player Network Sharing Service to allow sharing traffic. [TCP]<Windows Media Player Network Sharing Service (UPnPHost-Out)rOutbound rule for the Windows Media Player Network Sharing Service to allow use of Universal Plug and Play. [TCP]DWindows Media Player Network Sharing Service x86 (Streaming-UDP-In)EWindows Media Player Network Sharing Service x86 (Streaming-UDP-Out)EWindows Media Player Network Sharing Service x86 (Streaming-TCP-Out)PA8Windows Media Player Network Sharing Service (Internet)AWindows Media Player Network Sharing Service (HTTP-Streaming-In)mInbound rule for the Windows Media Player Network Sharing Service to allow HTTP Media Streaming. [TCP 10245]Connect to a Network Projector(Connect to a Network Projector (WSD-In)[Inbound rule for Connect to a Network Projector to discover devices via WSDAPI. [UDP 3702])Connect to a Network Projector (WSD-Out)PA\Outbound rule for Connect to a Network Projector to discover devices via WSDAPI. [UDP 3702](Connect to a Network Projector (TCP-In)bInbound rule for Connect to a Network Projector to communicate with devices on the network. [TCP])Connect to a Network Projector (TCP-Out)cOutbound rule for Connect to a Network Projector to communicate with devices on the network. [TCP]/Connect to a Network Projector (WSD Events-In)]Inbound rule for Connect to a Network Projector to allow WSDAPI Events Discovery. [TCP 5357]0Connect to a Network Projector (WSD Events-Out)^Outbound rule for Connect to a Network Projector to allow WSDAPI Events Discovery. [TCP 5358]5Connect to a Network Projector (WSD EventsSecure-In)ZInbound rule for Connect to a Network Projector to allow Secure WSDAPI Events. [TCP 5358]6Connect to a Network Projector (WSD EventsSecure-Out)PA[Outbound rule for Connect to a Network Projector to allow Secure WSDAPI Events. [TCP 5358]PA.Windows Peer to Peer Collaboration Foundation7Windows Peer to Peer Collaboration Foundation (TCP-In)iInbound rule for the Windows Peer to Peer Collaboration Foundation for Peer to Peer Communication. [TCP]8Windows Peer to Peer Collaboration Foundation (TCP-Out)jOutbound rule for the Windows Peer to Peer Collaboration Foundation for Peer to Peer Communication. [TCP]7Windows Peer to Peer Collaboration Foundation (WSD-In)nInbound rule for the Windows Peer to Peer Collaboration Foundation to discover devices via WSDAPI. [UDP 3702]8Windows Peer to Peer Collaboration Foundation (WSD-Out)PAoOutbound rule for the Windows Peer to Peer Collaboration Foundation to discover devices via WSDAPI. [UDP 3702]8Windows Peer to Peer Collaboration Foundation (PNRP-In)mInbound rule for the Windows Peer to Peer Collaboration Foundation to allow Peer Name Resolution. [UDP 3540]9Windows Peer to Peer Collaboration Foundation (PNRP-Out)nOutbound rule for the Windows Peer to Peer Collaboration Foundation to allow Peer Name Resolution. [UDP 3540]8Windows Peer to Peer Collaboration Foundation (SSDP-In)Inbound rule for the Windows Peer to Peer Collaboration Foundation to allow use of the Simple Service Discovery Protocol. [UDP 1900]9Windows Peer to Peer Collaboration Foundation (SSDP-Out)PAOutbound rule for the Windows Peer to Peer Collaboration Foundation to allow use of the Simple Service Discovery Protocol. [UDP 1900]Windows Meeting Space Windows Meeting Space (DFSR-In)hInbound rule for Windows Meeting Space to allow Distributed File System Replication traffic. [TCP 5722]!Windows Meeting Space (DFSR-Out)iOutbound rule for Windows Meeting Space to allow Distributed File System Replication traffic. [TCP 5722]Windows Meeting Space (TCP-In)MInbound rule for Windows Meeting Space to allow collaboration traffic. [TCP] Windows Meeting Space (TCP-Out)NOutbound rule for Windows Meeting Space to allow collaboration traffic. [TCP]Windows Meeting Space (UDP-In)PAMInbound rule for Windows Meeting Space to allow collaboration traffic. [UDP] Windows Meeting Space (UDP-Out)NOutbound rule for Windows Meeting Space to allow collaboration traffic. [UDP]Windows Meeting Space (P2P-In)TInbound rule for Windows Meeting Space to allow Peer Networking traffic. [TCP 3587] Windows Meeting Space (P2P-Out)UOutbound rule for Windows Meeting Space to allow Peer Networking traffic. [TCP 3587]PANetwork DiscoveryNetwork Discovery (SSDP-In)eInbound rule for Network Discovery to allow use of the Simple Service Discovery Protocol. [UDP 1900]Network Discovery (SSDP-Out)fOutbound rule for Network Discovery to allow use of the Simple Service Discovery Protocol. [UDP 1900]Network Discovery (UPnP-In)WInbound rule for Network Discovery to allow use of Universal Plug and Play. [TCP 2869]Network Discovery (UPnP-Out)SOutbound rule for Network Discovery to allow use of Universal Plug and Play. [TCP]Network Discovery (NB-Name-In)OInbound rule for Network Discovery to allow NetBIOS Name Resolution. [UDP 137] Network Discovery (NB-Name-Out)POutbound rule for Network Discovery to allow NetBIOS Name Resolution. [UDP 137]#Network Discovery (NB-Datagram-In)cInbound rule for Network Discovery to allow NetBIOS Datagram transmission and reception. [UDP 138]$Network Discovery (NB-Datagram-Out)PAdOutbound rule for Network Discovery to allow NetBIOS Datagram transmission and reception. [UDP 138]Network Discovery (WSD-In)ZInbound rule for Network Discovery to discover devices via Function Discovery. [UDP 3702]Network Discovery (WSD-Out)[Outbound rule for Network Discovery to discover devices via Function Discovery. [UDP 3702]!Network Discovery (LLMNR-UDP-In)]Inbound rule for Network Discovery to allow Link Local Multicast Name Resolution. [UDP 5355]"Network Discovery (LLMNR-UDP-Out)^Outbound rule for Network Discovery to allow Link Local Multicast Name Resolution. [UDP 5355]Network Discovery (Pub-WSD-In)ZInbound rule for Network Discovery to discover devices via Function Discovery. [UDP 3702] Network Discovery (Pub WSD-Out)[Outbound rule for Network Discovery to discover devices via Function Discovery. [UDP 3702](Network Discovery (WSD EventsSecure-In)dInbound rule for Network Discovery to allow Secure WSDAPI Events via Function Discovery. [TCP 5358])Network Discovery (WSD EventsSecure-Out)PAeOutbound rule for Network Discovery to allow Secure WSDAPI Events via Function Discovery. [TCP 5358]"Network Discovery (WSD Events-In)]Inbound rule for Network Discovery to allow WSDAPI Events via Function Discovery. [TCP 5357]#Network Discovery (WSD Events-Out)^Outbound rule for Network Discovery to allow WSDAPI Events via Function Discovery. [TCP 5357]!Network Discovery (UPnPHost-Out)SOutbound rule for Network Discovery to allow use of Universal Plug and Play. [TCP]PARemote AssistanceRemote Assistance (TCP-In)2Inbound rule for Remote Assistance traffic. [TCP]Remote Assistance (TCP-Out)PA3Outbound rule for Remote Assistance traffic. [TCP]%Remote Assistance (RA Server TCP-In)IInbound rule for Remote Assistance to allow offers for assistance. [TCP]&Remote Assistance (RA Server TCP-Out)JOutbound rule for Remote Assistance to allow offers for assistance. [TCP] Remote Assistance (SSDP UDP-In)eInbound rule for Remote Assistance to allow use of the Simple Service Discovery Protocol. [UDP 1900]!Remote Assistance (SSDP UDP-Out)PAfOutbound rule for Remote Assistance to allow use of the Simple Service Discovery Protocol. [UDP 1900] Remote Assistance (SSDP TCP-In)WInbound rule for Remote Assistance to allow use of Universal Plug and Play. [TCP 2869]!Remote Assistance (SSDP TCP-Out)SOutbound rule for Remote Assistance to allow use of Universal Plug and Play. [TCP]Remote Assistance (DCOM-In)VInbound rule for Remote Assistance to allow offers for assistance via DCOM. [TCP 135]Remote Assistance (PNRP-Out)YOutbound rule for Remote Assistance to allow use of Peer Name Resolution Protocol. [UDP]Remote Assistance (PNRP-In)PAZInbound rule for Remote Assistance to allow use Peer Name Resolution Protocol. [UDP 3540]"Remote Scheduled Tasks Management(Remote Scheduled Tasks Management (RPC)PInbound rule for the Task Scheduler service to be remotely managed via RPC/TCP..Remote Scheduled Tasks Management (RPC-EPMAP)\Inbound rule for the RPCSS service to allow RPC/TCP traffic for the Task Scheduler service.$Distributed Transaction Coordinator-Distributed Transaction Coordinator (TCP-In)PAQInbound rule to allow traffic for the Distributed Transaction Coordinator. [TCP].Distributed Transaction Coordinator (TCP-Out)ROutbound rule to allow traffic for the Distributed Transaction Coordinator. [TCP]*Distributed Transaction Coordinator (RPC)Inbound rule for the Kernel Transaction Resource Manager for Distributed Transaction Coordinator service to be remotely managed via RPC/TCP.0Distributed Transaction Coordinator (RPC-EPMAP)Inbound rule for the RPCSS service to allow RPC/TCP traffic for the Kernel Transaction Resource Manager for Distributed Transaction Coordinator service.PARouting and Remote Access$Routing and Remote Access (L2TP-In)KInbound rule for RRAS to allow Layer 2 Tunnel Protocol traffic. [UDP 1701]%Routing and Remote Access (L2TP-Out)LOutbound rule for RRAS to allow Layer 2 Tunnel Protocol traffic. [UDP 1701]%Routing and Remote Access (PPTP-Out)SOutbound rule for RRAS to allow Point-to-Point Tunnel Protocol traffic. [TCP 1723]$Routing and Remote Access (PPTP-In)RInbound rule for RRAS to allow Point-to-Point Tunnel Protocol traffic. [TCP 1723]#Routing and Remote Access (GRE-In)OInbound rule for RRAS to allow Generic Routing Encapsulation Protocol traffic.$Routing and Remote Access (GRE-Out)OOutbound rule for RRAS to allow Generic Routing Encapsulation Protocol TrafficPA9Windows Collaboration Computer Name Registration ServiceCWindows Collaboration Computer Name Registration Service (PNRP-In)xInbound rule for the Windows Collaboration Computer Name Registration Service to allow Peer Name Resolution. [UDP 3540]DWindows Collaboration Computer Name Registration Service (PNRP-Out)yOutbound rule for the Windows Collaboration Computer Name Registration Service to allow Peer Name Resolution. [UDP 3540]CWindows Collaboration Computer Name Registration Service (SSDP-In)Inbound rule for the Windows Collaboration Computer Name Registration Service to allow use of the Simple Service Discovery Protocol. [UDP 1900]DWindows Collaboration Computer Name Registration Service (SSDP-Out)Outbound rule for the Windows Collaboration Computer Name Registration Service to allow use of the Simple Service Discovery Protocol. [UDP 1900]PA)Windows Management Instrumentation (WMI)-Windows Management Instrumentation (DCOM-In)\Inbound rule to allow DCOM traffic for remote Windows Management Instrumentation. [TCP 135],Windows Management Instrumentation (WMI-In)WInbound rule to allow WMI traffic for remote Windows Management Instrumentation. [TCP]PA.Windows Management Instrumentation (ASync-In)dInbound rule to allow Asynchronous WMI traffic for remote Windows Management Instrumentation. [TCP]-Windows Management Instrumentation (WMI-Out)XOutbound rule to allow WMI traffic for remote Windows Management Instrumentation. [TCP]PARemote Volume Management6Remote Volume Management - Virtual Disk Service (RPC)iInbound rule for the Remote Volume Management - Virtual Disk Service to be remotely managed via RPC/TCP.=Remote Volume Management - Virtual Disk Service Loader (RPC)pInbound rule for the Remote Volume Management - Virtual Disk Service Loader to be remotely managed via RPC/TCP.%Remote Volume Management (RPC-EPMAP)ZInbound rule for the RPCSS service to allow RPC/TCP traffic for Remote Volume Management.Performance Logs and Alerts%Performance Logs and Alerts (TCP-In)?Inbound rule for Performance Logs and Alerts traffic. [TCP-In]&Performance Logs and Alerts (DCOM-In)XInbound rule for Performance Logs and Alerts to allow remote DCOM activation. [TCP-135]jThe firewall rules that are part of Core Networking are required for reliable IPv4 and IPv6 connectivity.9Windows Remote Management - Compatibility Mode (HTTP-In)ZCompatibility mode inbound rule for Windows Remote Management via WS-Management. [TCP 80]PA]This feature is used for machine counting and license compliance in enterprise environments.PAThis feature allows Background Intelligent Transfer Service (BITS) clients that are in the same subnet to locate and share files that are stored in the BITS cache. (Uses WSDAPI and RPC)~This feature is used for sharing local files and printers with other users on the network. (Uses NetBIOS, LLMNR, SMB and RPC)EThis feature is used for accessing the desktop from a remote system.PAEThis feature is used for accessing the desktop from a remote system.PAIThis feature is used for connecting to iSCSI target servers and devices.PAeThis feature allows remote viewing and management of the local event log. (Uses Named Pipes and RPC)PATThis feature allows remote management of local services. (Uses Named Pipes and RPC)cThe feature allows remotely manageable services to receive RPC traffic. (Uses Named Pipes and RPC)PAPThis feature allows remote management of the local Windows Firewall. (Uses RPC)This feature allows remote management of the system via WS-Management, a web services-based protocol for remote management of operating systems and devices.PAThis feature allows the transfer of media from your network enabled camera or media device to your computer using the Media Transfer Protocol (MTP). (Uses UPnP and SSDP)~This feature allows Media Center Extenders to communicate with a computer running Windows Media Center. (Uses SSDP and qWave)?This feature allows users to receive streaming media over UDP.PAVThis feature enables users to share media over a network. (Uses UPnP, SSDP and qWave)DThis feature allows users to share out home media over the Internet|This feature enables users to connect to projectors over wired or wireless networks to project presentations. (Uses WSDAPI)hThis feature is required to enable various peer-to-peer programs and technologies. (Uses SSDP and PNRP)This feature is used for collaborating over a network to share documents, programs or your desktop with other people. (Uses DFSR and P2P)This feature allows this computer to discover other devices and be discovered by other devices on the network. (Uses Function Discovery Host and Publication Services, UPnP, SSDP, NetBIOS and LLMNR)This feature allows users of this computer to request remote assistance from other users on the network. (Uses UPnP, SSDP, PNRP and Teredo)WThis feature allows remote management of the local task scheduling service. (Uses RPC)PAThis feature coordinates transactions that update transaction-protected resources, such as databases, message queues and file systems.PA@This feature is used to allow incoming VPN and RAS connections.This feature allows other computers to find and communicate with your computer using the Peer Name Resolution Protocol. (Uses SSDP and PNRP)PAThis feature allows remote management of Windows by exposing a set of manageable components in a set of classes defined by the Common Information Model (CIM) of the distributed management task force. (Uses DCOM)VThis feature provides remote software and hardware disk volume management. (Uses RPC)]This feature allows remote management of the Performance Logs and Alerts service. (Uses RPC)PA4VS_VERSION_INFOjDjD?StringFileInfo040904B0LCompanyNameMicrosoft CorporationRFileDescriptionWindows Firewall APIr)FileVersion6.1.7601.17514 (win7sp1_rtm.101119-1850)@InternalNameFirewallAPI.DLL.LegalCopyright Microsoft Corporation. All rights reserved.POriginalFilenameFirewallAPI.DLL.MUIj%ProductNameMicrosoft Windows Operating SystemBProductVersion6.1.7601.17514DVarFileInfo$Translation	PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD

Anon7 - 2022
AnonSec Team