Or, you could use PInvoke to call Winsock's WSAStartup() function directly.
Create a TCP ( SocketType.Stream and ProtocolType.TCP) or UDP ( SocketType.DGram and ProtocolType.UDP) socket instead, which are not restricted, and most likely what OOo is actually going to use internally anyway. On the other hand, if your intention is just to initialize Winsock in general, then you do not need to create a RAW socket to do that. There is no way to get around that restriction. In earlier versions of Windows, access for raw sockets is enforced during other socket operations. Ensure the NODE or HOST name can be resolved. These message numbers and codes are in the TCPERRNO.H include file supplied with TCP/IP Services. The system cannot find the device specified. This section provides the system-wide message numbers and codes set by the system calls. On Windows Vista and later, access for raw sockets is enforced at socket creation. Remote Access Connection Manager failed to start because the Protocol engine C:WINDOWSsystem32vpnike.dll failed to initialize. x: Windows Sockets initialization failed: 5.
Users running Winsock applications that use raw sockets must be a member of the Administrators group on the local computer, otherwise raw socket calls will fail with an error code of WSAEACCES. x: Windows Sockets initialization failed: 5. Note To use a socket of type SOCK_RAW requires administrative privileges. Therefore, only members of the Administrators group can create sockets of type SOCK_RAW on Windows 2000 and later. Raw sockets offer the capability to manipulate the underlying transport, so they can be used for malicious purposes that pose a security threat. Access to RAW sockets requires admin rights on Windows 2000 and later, and that is described on MSDN:
0 kommentar(er)
