-->
-->
Apr 18, 2011 I started listening to Dr. Stafford’s TCP/IP Podcasts to augment my CISCO network Fundamental class this week. I see that he left several other audio lectures for networking- priceless for me! It is next to impossible for me to find a great professor in computer science or the programming languages such as Dr. Oct 08, 2016 Docker for Mac should listen on 2375, providing an HTTP API server. Actual behavior ± telnet 127.0.0.1 2375 Trying 127.0.0.1. Telnet: connect to address 127.0.0.1: Connection refused telnet: Unable to connect to remote host Information.
Mar 19, 2020 Office for Mac 2004 will not run on Lion. Previous MacOS versions supported Rosetta, an Apple Mac OSX bridge technology that enabled applications such as Office for Mac 2004 to run on the latest chip architecture for Mac. Because Lion no longer supports Rosetta, applications that relied on it will no longer function under the new MacOS. Mar 19, 2020 Microsoft has been working with Apple from the early days of Lion, and collectively have been able to address many issues leading up to the Lion release. Many of our Office for Mac engineers have been running Lion for months, and are generally having no problems running Office 2011 on it. Microsoft office for mac os x lion. Oct 27, 2018 Amazon.com: Microsoft Office Home and Business 2019 Download 1 Person Compatible on Windows 10 and Apple macOS: Software. There are two major Office for Mac issues Microsoft is aware of running on Lion: Communicator for Mac crashes when you send an IM or start an audio/visual call. Many of our Office for Mac engineers have been running Lion for months, and are generally having no problems running Office 2011 on it. The Office for Mac team recently posted a blog post concerning Lion compatibility. You can find that blog post by following the link below: Office for Mac 2011 and Mac OS X 10.7 Lion.
The management filtering layer identifiers are generally used by user-mode applications and are each represented by a GUID, which is 128 bits in size. These identifiers are defined as follows.
Note
The V4 and V6 suffixes at the end of the layer identifiers indicate whether the layer is located in the IPv4 network stack or in the IPv6 network stack.
Management filtering layer identifier | Filtering layer description |
---|---|
FWPM_LAYER_INBOUND_IPPACKET_V4 FWPM_LAYER_INBOUND_IPPACKET_V6 | This filtering layer is located in the receive path just after the IP header of a received packet has been parsed but before any IP header processing takes place. No IPsec decryption or reassembly has occurred. |
FWPM_LAYER_INBOUND_IPPACKET_V4_DISCARD FWPM_LAYER_INBOUND_IPPACKET_V6_DISCARD Microsoft word mac default save to the desktop download. NoteOffice 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. IntroductionThis article describes how to change the default view to Draft view in Microsoft Office Word. For more information about this change,. | This filtering layer is located in the receive path for processing any received packets that have been discarded at the network layer. |
FWPM_LAYER_OUTBOUND_IPPACKET_V4 FWPM_LAYER_OUTBOUND_IPPACKET_V6 | This filtering layer is located in the send path just before the sent packet is evaluated for fragmentation. All IP header processing is complete and all extension headers are in place. Any IPsec authentication and encryption has already occurred. |
FWPM_LAYER_OUTBOUND_IPPACKET_V4_DISCARD FWPM_LAYER_OUTBOUND_IPPACKET_V6_DISCARD | This filtering layer is located in the send path for processing any sent packets that have been discarded at the network layer. |
FWPM_LAYER_IPFORWARD_V4 FWPM_LAYER_IPFORWARD_V6 | This filtering layer is located in the forwarding path at the point where a received packet is forwarded. |
FWPM_LAYER_IPFORWARD_V4_DISCARD FWPM_LAYER_IPFORWARD_V6_DISCARD | This filtering layer is located in the forwarding path for processing any forwarded packets that have been discarded at the forward layer. |
FWPM_LAYER_INBOUND_TRANSPORT_V4 FWPM_LAYER_INBOUND_TRANSPORT_V6 | This filtering layer is located in the receive path just after a received packet's header has been parsed by the network stack at the transport layer, but before any transport layer processing takes place. |
FWPM_LAYER_INBOUND_TRANSPORT_V4_DISCARD FWPM_LAYER_INBOUND_TRANSPORT_V6_DISCARD | This filtering layer is located in the receive path for processing any received packets that have been discarded at the transport layer. |
FWPM_LAYER_OUTBOUND_TRANSPORT_V4 FWPM_LAYER_OUTBOUND_TRANSPORT_V6 | This filtering layer is located in the send path just after a sent packet has been passed to the network layer for processing but before any network layer processing takes place. This filtering layer is located at the top of the network layer instead of at the bottom of the transport layer so that any packets that are sent by third-party transports or as raw packets are filtered at this layer. |
FWPM_LAYER_OUTBOUND_TRANSPORT_V4_DISCARD FWPM_LAYER_OUTBOUND_TRANSPORT_V6_DISCARD | This filtering layer is located in the send path for processing any sent packets that have been discarded at the transport layer. |
FWPM_LAYER_STREAM_V4 FWPM_LAYER_STREAM_V6 | This filtering layer is located in the stream data path. This layer allows for processing network data on a per stream basis. At the stream layer, the network data is bidirectional. |
FWPM_LAYER_STREAM_V4_DISCARD FWPM_LAYER_STREAM_V6_DISCARD | This filtering layer is reserved for future use. |
FWPM_LAYER_DATAGRAM_DATA_V4 FWPM_LAYER_DATAGRAM_DATA_V6 | This filtering layer is located in the datagram data path. This layer allows for processing network data on a per datagram basis. At the datagram layer, the network data is bidirectional. |
FWPM_LAYER_DATAGRAM_DATA_V4_DISCARD FWPM_LAYER_DATAGRAM_DATA_V6_DISCARD | This filtering layer is located in the datagram data path for processing any datagrams that have been discarded. |
FWPM_LAYER_INBOUND_ICMP_ERROR_V4 FWPM_LAYER_INBOUND_ICMP_ERROR_V6 | This filtering layer is located in the receive path for processing received ICMP messages for the transport protocol. |
FWPM_LAYER_INBOUND_ICMP_ERROR_V4_DISCARD FWPM_LAYER_INBOUND_ICMP_ERROR_V6_DISCARD | This filtering layer is located in the receive path for processing received ICMP messages that have been discarded. |
FWPM_LAYER_OUTBOUND_ICMP_ERROR_V4 FWPM_LAYER_OUTBOUND_ICMP_ERROR_V6 | This filtering layer is located in the send path for processing sent ICMP messages for the transport protocol. |
FWPM_LAYER_OUTBOUND_ICMP_ERROR_V4_DISCARD FWPM_LAYER_OUTBOUND_ICMP_ERROR_V6_DISCARD | This filtering layer is located in the send path for processing sent ICMP messages that have been discarded. |
FWPM_LAYER_ALE_AUTH_CONNECT_V4 FWPM_LAYER_ALE_AUTH_CONNECT_V6 | This filtering layer allows for authorizing connect requests for outgoing TCP connections, as well as authorizing outgoing non-TCP traffic based on the first packet sent. |
FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD FWPM_LAYER_ALE_AUTH_CONNECT_V6_DISCARD | This filtering layer allows for processing connect requests for outgoing TCP connections that have been discarded, as well as processing authorizations for outgoing non-TCP traffic that have been discarded. |
FWPM_LAYER_ALE_FLOW_ESTABLISHED_V4 FWPM_LAYER_ALE_FLOW_ESTABLISHED_V6 | This filtering layer allows for notification of when a TCP connection has been established, or when non-TCP traffic has been authorized. |
FWPM_LAYER_ALE_FLOW_ESTABLISHED_V4_DISCARD FWPM_LAYER_ALE_FLOW_ESTABLISHED_V6_DISCARD | This filtering layer allows for processing when an established TCP connection has been discarded at the flow established layer, as well as when authorized non-TCP traffic has been discarded at the flow established layer. |
FWPM_LAYER_ALE_AUTH_LISTEN_V4 FWPM_LAYER_ALE_AUTH_LISTEN_V6 | This filtering layer allows for authorizing TCP listen requests. |
FWPM_LAYER_ALE_AUTH_LISTEN_V4_DISCARD FWPM_LAYER_ALE_AUTH_LISTEN_V6_DISCARD | This filtering layer allows for processing TCP listen requests that have been discarded. |
FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4 FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 | This filtering layer allows for authorizing accept requests for incoming TCP connections, as well as authorizing incoming non-TCP traffic based on the first packet received. |
FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4_DISCARD FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6_DISCARD | This filtering layer allows for processing accept requests for incoming TCP connections that have been discarded, as well as processing authorizations for incoming non-TCP traffic that have been discarded. |
FWPM_LAYER_ALE_AUTH_ROUTE_V4 FWPM_LAYER_ALE_AUTH_ROUTE_V6 | This filtering layer allows for inspecting and filtering the route and path parameters of bind and connect requests. |
FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V6 | This filtering layer is used as an opportunity to reclaim resources allocated by the callout driver in any of the ALE_AUTH_CONNECT or ALE_AUTH_RECV_ACCEPT layers. |
FWPM_LAYER_ALE_RESOURCE_ASSIGNMENT_V4 FWPM_LAYER_ALE_RESOURCE_ASSIGNMENT_V6 | This filtering layer allows for authorizing transport port assignments, bind requests, promiscuous mode requests, and raw mode requests. |
FWPM_LAYER_ALE_RESOURCE_ASSIGNMENT_V4_DISCARD FWPM_LAYER_ALE_RESOURCE_ASSIGNMENT_V6_DISCARD | This filtering layer allows for processing the following discarded items: transport port assignments, bind requests, promiscuous mode requests, and raw mode requests. |
FWPM_LAYER_ALE_RESOURCE_RELEASE_V4 FWPM_LAYER_ALE_RESOURCE_RELEASE_V6 | This filtering layer is used as an opportunity to reclaim resources allocated by the callout driver in any of the ALE_RESOURCE_ASSIGNMENT layers. |
FWPM_LAYER_IPSEC_KM_DEMUX_V4 FWPM_LAYER_IPSEC_KM_DEMUX_V6 | This filtering layer is used to determine which keying modules are invoked when the local system is the initiator. This is a user-mode filtering layer. |
FWPM_LAYER_IPSEC_V4 FWPM_LAYER_IPSEC_V6 | This filtering layer allows the keying module to look up quick-mode policy information when negotiating quick-mode security associations. This is a user-mode filtering layer. |
FWPM_LAYER_IKEEXT_V4 FWPM_LAYER_IKEEXT_V6 | This filtering layer allows the IKE and authenticated IP modules to look up main-mode policy information when negotiating main-mode security associations. This is a user-mode filtering layer. |
FWPM_LAYER_RPC_UM | This filtering layer allows for inspecting the RPC data fields that are available in user mode. This is a user-mode filtering layer. |
FWPM_LAYER_RPC_EPMAP | This filtering layer allows for inspecting the RPC data fields that are available in user mode during endpoint resolution. This is a user-mode filtering layer. |
FWPM_LAYER_RPC_EP_ADD | This filtering layer allows for inspecting the RPC data fields that are available in user mode when a new endpoint is added. This is a user-mode filtering layer. |
FWPM_LAYER_RPC_PROXY_CONN | This filtering layer allows for inspecting RpcProxy connection requests. This is a user-mode filtering layer. |
FWPM_LAYER_RPC_PROXY_IF | This filtering layer allows for inspecting the interface used for RpcProxy connections. This is a user-mode filtering layer. |
FWPM_LAYER_INBOUND_MAC_FRAME_ETHERNET | This filtering layer allows for inspecting the MAC frame data at the inbound lower (to the NDIS protocol driver) layer. Note: Available only on Windows 8 and later. |
FWPM_LAYER_OUTBOUND_MAC_FRAME_ETHERNET | This filtering layer allows for inspecting the MAC frame data at the outbound upper (to the NDIS protocol driver) layer. Note: Available only on Windows 8 and later. |
FWPM_LAYER_INBOUND_MAC_FRAME_NATIVE | This filtering layer allows for inspecting the MAC frame data at the inbound lower (to the NDIS miniport driver) layer. Note: Available only on Windows 8 and later. |
FWPM_LAYER_OUTBOUND_MAC_FRAME_NATIVE | This filtering layer allows for inspecting the MAC frame data at the outbound lower (to the NDIS miniport driver) layer. Note: Available only on Windows 8 and later. |
FWPM_LAYER_INGRESS_VSWITCH_ETHERNET | This filtering layer allows for inspecting the ingress 802.3 data of the Hyper-V extensible switch. Note: Available only on Windows 8 and later. |
FWPM_LAYER_EGRESS_VSWITCH_ETHERNET | This filtering layer allows for inspecting the egress 802.3 data of the Hyper-V extensible switch. Note: Available only on Windows 8 and later. |
FWPM_LAYER_INGRESS_VSWITCH_TRANSPORT_V4 FWPM_LAYER_INGRESS_VSWITCH_TRANSPORT_V6 | This filtering layer allows for inspecting the ingress transport data of the Hyper-V extensible switch. Note: Available only on Windows 8 and later. |
FWPM_LAYER_EGRESS_VSWITCH_TRANSPORT_V4 FWPM_LAYER_EGRESS_VSWITCH_TRANSPORT_V6 | This filtering layer allows for inspecting the egress transport data of the Hyper-V extensible switch. Note: Available only on Windows 8 and later. |
By Mark Russinovich
Published: July 25, 2011
Download TCPView(285 KB)
Run now from Sysinternals Live.
Run now from Sysinternals Live.
Introduction
TCPView is a Windows program that will show you detailed listings of allTCP and UDP endpoints on your system, including the local and remoteaddresses and state of TCP connections. On Windows Server 2008, Vista,and XP, TCPView also reports the name of the process that owns theendpoint. TCPView provides a more informative and conveniently presentedsubset of the Netstat program that ships with Windows. The TCPViewdownload includes Tcpvcon, a command-line version with the samefunctionality.
Using TCPView
When you start TCPView it will enumerate all active TCP and UDPendpoints, resolving all IP addresses to their domain name versions. Youcan use a toolbar button or menu item to toggle the display of resolvednames. On Windows XP systems, TCPView shows the name of the process thatowns each endpoint.
By default, TCPView updates every second, but you can use theOptions|Refresh Rate menu item to change the rate. Endpoints thatchange state from one update to the next are highlighted in yellow;those that are deleted are shown in red, and new endpoints are shown ingreen.
You can close established TCP/IP connections (those labeled with a stateof ESTABLISHED) by selecting File|Close Connections, or byright-clicking on a connection and choosing Close Connections fromthe resulting context menu.
You can save TCPView's output window to a file using the Save menuitem.
Using Tcpvcon
Tcpvcon usage is similar to that of the built-in Windows netstatutility:
Usage: tcpvcon [-a] [-c] [-n] [process name or PID]
Mac Tcp Microsoft-ds Listen Live
Parameter | Description |
---|---|
-a | Show all endpoints (default is to show established TCP connections). |
-c | Print output as CSV. |
-n | Don't resolve addresses. |
Microsoft TCPView KB Article
This Microsoft KB article references TCPView:
Download TCPView(285 KB)
Run now from Sysinternals Live.
Runs on:
Mac Tcp Microsoft-ds Listen Live
- Client: Windows Vista and higher.
- Server: Windows Server 2008 and higher.