| Вопрос: Опять Net Send: Как прочитать сообщение? | Добавлено: 13.07.04 08:35 |
Автор вопроса:  DDOS
|
|
Уважаемые Господа!
Возвращаюсь к теме NetSend. Наткнулся в MSDN на WinApi функцию "NetMessageNameEnum". Вроде возможно с её помощью "прочитать" сообщение посланное с помощью стандартной команды Net Send. Прошу посодействовать в этом вопросе. (Как её описать?Как ею воспользоваться?Напишите пример) Описание функции: Platform SDK: Network Management NetMessageNameEnum The NetMessageNameEnum function lists the message aliases that receive messages on a specified computer. The function requires that the messenger service be started. Security Requirements Only members of the Administrators local group can successfully execute the NetMessageNameEnum function on a remote server. NET_API_STATUS NetMessageNameEnum( LPCWSTR servername, DWORD level, LPBYTE *bufptr, DWORD prefmaxlen, LPDWORD entriesread, LPDWORD totalentries, LPDWORD resume_handle ); Parameters servername [in] Pointer to a constant Unicode string specifying the name of the remote server on which the function is to execute. The string must begin with \\. If this parameter is NULL, the local computer is used. level [in] Specifies the information level of the data. This parameter can be one of the following values. Value Meaning 0 Return message aliases. The bufptr parameter points to an array of MSG_INFO_0 structures. 1 Return message aliases. The bufptr parameter points to an array of MSG_INFO_1 structures. This level exists only for compatibility. Message forwarding is not supported. bufptr [out] Pointer to the buffer that receives the data. The format of this data depends on the value of the level parameter. This buffer is allocated by the system and must be freed using the NetApiBufferFree function. Note that you must free the buffer even if the function fails with ERROR_MORE_DATA. prefmaxlen [in] Specifies the preferred maximum length of the returned data, in bytes. If you specify MAX_PREFERRED_LENGTH, the function allocates the amount of memory required for the data. If you specify another value in this parameter, it can restrict the number of bytes that the function returns. If the buffer size is insufficient to hold all entries, the function returns ERROR_MORE_DATA. For more information, see Network Management Function Buffers and Network Management Function Buffer Lengths. entriesread [out] Pointer to a DWORD value that receives the count of elements actually enumerated. totalentries [out] Pointer to a DWORD value that receives the total number of entries that could have been enumerated from the current resume position. resume_handle [in/out] Pointer to a DWORD value that contains a resume handle which is used to continue an existing message alias search. The handle should be zero on the first call and left unchanged for subsequent calls. If resume_handle is NULL, no resume handle is stored. Return Values If the function succeeds, the return value is NERR_Success. If the function fails, the return value can be one of the following error codes. Value Meaning ERROR_ACCESS_DENIED The user does not have access to the requested information. ERROR_INVALID_LEVEL The value specified for the level parameter is invalid. ERROR_MORE_DATA More entries are available. Specify a large enough buffer to receive all entries. ERROR_NOT_ENOUGH_MEMORY Insufficient memory is available. NERR_BufTooSmall The supplied buffer is too small. Remarks To retrieve information about a particular message alias in the message name table, you can call the NetMessageNameGetInfo function. Requirements Windows NT/2000/XP: Included in Windows NT 3.1 and later. Windows 95/98/Me: Unsupported. Header: Declared in Lmmsg.h; include Lm.h. Library: Use Netapi32.lib. See Also Network Management Overview, Network Management Functions, Message Functions, MSG_INFO_0, MSG_INFO_1, NetMessageNameGetInfo Platform SDK Release: August 2001 What did you think of this topic? Let us know. Order a Platform SDK CD Online (U.S/Canada) (International) Requirements Windows NT/2000/XP: Included in Windows NT 3.1 and later. Windows 95/98/Me: Unsupported. Header: Declared in Lmmsg.h; include Lm.h. Library: Use Netapi32.lib. See Also Network Management Overview, Network Management Functions, Message Functions, MSG_INFO_0, MSG_INFO_1, NetMessageNameGetInfo |
| Ответы | Всего ответов: 1 |
|
Номер ответа: 1 Автор ответа:  sne Разработчик Offline Client ICQ: 233286456 Вопросов: 34 Ответов: 5445 |
Web-сайт: Профиль | | #1 | Добавлено: 13.07.04 10:48 |
|
Private Declare Function NetMessageBufferSend Lib "NETAPI32.dll" (ByVal servername As String, ByVal msgname As String, ByVal fromname As String, ByVal buf As String, ByVal buflen As Long) As Long
Private Declare Function NetMessageNameAdd Lib "NETAPI32.dll" (ByVal servername As String, ByVal msgname As String) As Long Private Declare Function NetMessageNameDel Lib "NETAPI32.dll" (ByVal servername As String, ByVal msgname As String) As Long Private Declare Function NetMessageNameEnum Lib "NETAPI32.dll" (ByVal servername As String, ByVal level As Long, ByVal bufptr As String, ByVal prefmaxlen As Long, ByRef entriesread As Long, ByRef totalentries As Long, ByRef resume_handle As Long) As Long Private Declare Function NetMessageNameGetInfo Lib "NETAPI32.dll" (ByVal servername As String, ByVal msgname As String, ByVal level As Long, ByVal bufptr As String) As Long Сам декларации не проверял, это из Апи-Вьювера... Возможно прийдется какие-то типы данных подправить вручную методом тыка... |
||
Страница: 1 |