| • | IPC$ Connections Do Not Disconnect |
| (153066) - When a connection is made to a Windows NT 3.51 server to which the user has had no prior connection, a connection is made to IPC$ as well as to the share. After disconnecting from ...
http://support.microsoft.com/kb/153066 |
| • | Some IPC$ Connections Cannot Be Disconnected |
| (153070) - When you connect to a Microsoft Windows NT version 3.51 server share, an initial connection is made to IPC$ and the connection is assigned to the username in Server Manager.
http://support.microsoft.com/kb/153070 |
| • | Net Use to IPC$ Share from Multihomed Computer Does Not Complete |
| (219318) - When you use the command (where x.x.x.x is the TCP/IP address of a computer running Windows NT 3.51) on a computer running Windows NT 4.0 with multiple network adapters, the ...
http://support.microsoft.com/kb/219318 |
| • | Admin$ and IPC$ Shares Missing at Domain Controller Startup |
| (246752) - When you start a domain controller that is running Microsoft Windows NT Server 4.0, Terminal Server Edition, the admin$ and C$ shares may be lost. You may not be able to recreate ...
http://support.microsoft.com/kb/246752 |
| • | How to create and delete hidden or administrative shares on client ... |
| (314984) - The IPC$ share; The PRINT$ share; Root partitions and volumes are shared as the drive letter name appended with the $ sign. For example, drive letters C and D are shared as C ...
http://support.microsoft.com/kb/314984 |
| • | INFO: Interprocess Communication on Windows Platforms |
| (95900) - The following are some of the standard mechanisms available for interprocess communication (IPC): NetBIOS, mailslots, windows sockets (winsock), named pipes, anonymous pipes ...
http://support.microsoft.com/kb/95900 |
| • | SMB Traffic During Windows NT Domain Logon |
| (139608) - The workstation connects to the IPC$ share on the DC so the computer name can be validated as existing on the domain: Windows NT Workstation to the Windows NT DC:
http://support.microsoft.com/kb/139608 |
| • | How to remove administrative shares in Windows Server 2008 |
| (954422) - IPC$: This is a resource that shares the named pipes that you must have for communication between programs. This resource cannot be deleted. NETLOGON: This is a resource that ...
http://support.microsoft.com/kb/954422 |
| • | "You do not have sufficient permissions in the Domain" error message ... |
| (319966) - Describes how adding the Exchange Domain Servers group to built-in Active Directory security groups can cause Setup failures because of missing permissions.
http://support.microsoft.com/kb/319966 |
| • | No Mouse/Keyboard After Updating Microsoft Natural Keyboard Pro ... |
| (257729) - ... IPC$ share by using that computer's local administrator credentials before you can attach with Regedt32.exe as described below. To map a connection to the computer's IPC ...
http://support.microsoft.com/kb/257729 |
| • | How to use named pipe filters in Windows XP SP2, in Windows Server ... |
| (925890) - Unlike other forms of inter-process communication (IPC), a pipe is a one-way communication. For example, a pipe passes a parameter, such as the output of a process, to a second ...
http://support.microsoft.com/kb/925890 |
| • | The remote.exe command does not generate a connection to a Windows XP ... |
| (920706) - These approaches will have the same outcome as mapping to the IPC$ share on the client. Method 3 Important These steps may increase your security risk.
http://support.microsoft.com/kb/920706 |
| • | DirectPlay 6.1a Supports Ripple Launch Technology |
| (236614) - Before DPlay 6.1a, an IPC connection was established by including the process ID of the program being started in the shared IPC object name.
http://support.microsoft.com/kb/236614 |
| • | Troubleshooting Server Message Block inbound connection limit in ... |
| (328459) - Temporary null sessions are usually caused by IPC$ connections as the first step in establishing a connection. They stay active for 30 seconds to 90 seconds.
http://support.microsoft.com/kb/328459 |
| • | How to troubleshoot orphaned connections in SQL Server |
| (137983) - An IPC typically has its own mechanism to manage the client connections. When client connections become non-responsive for a certain amount of time, typically the Windows ...
http://support.microsoft.com/kb/137983 |
| • | How to Test Microsoft Remote Procedure Call Performance |
| (177446) - RPC uses IPC mechanisms to establish communications between the client and server to call program functions on a remote computer. The complex programs that use this level of ...
http://support.microsoft.com/kb/177446 |
| • | How to troubleshoot monitoring and logging issues for performance ... |
| (922775) - However, if the monitored process restarts, a new IPC block is opened by an auxiliary thread in the Remote Registry service. This auxiliary thread does not impersonate the user on ...
http://support.microsoft.com/kb/922775 |
| • | How to manage computer domain membership programmatically on Windows ... |
| (170620) - ... BOOL bEstablish, LPWSTR DomainName, LPWSTR UserName, LPWSTR Password ) { LPCWSTR szIpc = L"\\IPC$"; WCHAR RemoteResource[UNCLEN + 5 + 1]; // UNC len + \IPC ...
http://support.microsoft.com/kb/170620 |
| • | Detailed Usage of the Event Viewer /AUXSOURCE Switch Option |
| (312216) - In place of the IPC$ connection, you can create matching user names and passwords in the domain of the server in /auxsource= server.
http://support.microsoft.com/kb/312216 |
| • | How To Determine from Which Computer a User Logged On |
| (175062) - Src Mac Addr: Dst Mac Addr: Description WKS1 SUNKING C session setup & X, Username = MariaH, and C tree connect & X, Share = \\SUNKING\IPC$ WKS2 SUNKING ...
http://support.microsoft.com/kb/175062 |
|
