Just for reference, the way you do it without a wrapper dll is as follows:
First make a copy of the clusters that are intended just for calling the DLL and rewrite the arrays as scalars. LabView arrays have the number of array elements at the front, and C arrays don't. So instead of the 2-element array, you would have two scalar UINT32s, ident_number_0 and ident_number_1. Next call Flatten to String on the whole GF_SERVER_INFO cluster using platform-specific byte ordering, then convert the string to a byte array, then pass the byte array to the DLL.
As Andrey said, things can go wrong. For example GF_SW_VERSION_INFO has 112 bytes of data. The compiler is almost certainly going to pack this into 128 byte chunks in memory because it's faster. There is no way to know what size it really is without calling sizeof() using the compiler that built the DLL. Your structure must exactly duplicate the size that the DLL is expecting, e.g. by putting a UInt16 at the end of GF_SW_VERSION_INFO as padding. This is a pain, which is why people are recommending passing native LabView types to a DLL that you write and then letting your DLL call the external DLL.
Getting the data back out is the reverse of this process; byte array to string, unflatten string to cluster, convert special dll cluster to the "user" cluster.
Note the above only works with flat data types (no pointers).
