"Socket type not supported" error

kbbass · Post by **kbbass** » Mon Dec 08, 2008 9:45 pm

I am trying to get a proprietary app's windows service running in Wine. When I try to start the service, I get this:

err:eventlog:ReportEventW L"System error 10044: Socket type not supported."

I have copied all dependant DLLs from a Windows installation, but still the same error.

I know that this service is trying to set up a socket to listen on, but I'm not sure of the specifics, especially the type.

Anyone have any ideas? Getting this to work here would be great, since I won't need to set up a separate Windows box just for this service.

TIA

ken

James McKenzie · Post by **James McKenzie** » Mon Dec 08, 2008 10:36 pm

kbbass wrote:

I am trying to get a proprietary app's windows service running in Wine. When I try to start the service, I get this:

err:eventlog:ReportEventW L"System error 10044: Socket type not supported."

I have copied all dependant DLLs from a Windows installation, but still the same error.

I know that this service is trying to set up a socket to listen on, but I'm not sure of the specifics, especially the type.

Anyone have any ideas? Getting this to work here would be great, since I won't need to set up a separate Windows box just for this service.

Do you know what protocol and port this product listens on? That would
give us a start. It is possible that Linux does not know which port to use.

James McKenzie

jeffz · Post by **jeffz** » Tue Dec 09, 2008 7:59 am

kbbass wrote: Anyone have any ideas?

it's easier if you tell us the name of the program and if there is somewhere to get a demo/trial copy

kbbass · Post by **kbbass** » Tue Dec 09, 2008 10:17 am

jeffz wrote: it's easier if you tell us the name of the program and if there is somewhere to get a demo/trial copy

As I said, the program is part of a proprietary application, and, unfortunately, I have no source code for it, so I don't really know what port it is trying to open, nor can I 'legally' send it to anyone. That is a big part of the battle.

I have (re)verified that this app works on XP, and the DLLs I copied to Wine's system32 folder were from that installation.

I have the wineserver's verbose debug output that I could provide. But I am having a hard time deciphering much of it. It looks like a "select" call is returning TIMEOUT where it doesn't on XP.

Hope this helps some.

TIA

ken

kbbass · Post by **kbbass** » Tue Dec 09, 2008 10:27 am

James McKenzie wrote:
Do you know what protocol and port this product listens on? That would
give us a start. It is possible that Linux does not know which port to use.

James McKenzie

I just did a port scan of the working XP installation, and the app is listening on port 27345. As for the protocol, I should be able to get that from a capture trace.

TIA

ken

kbbass · Post by **kbbass** » Tue Dec 09, 2008 7:47 pm

OK, I think I got something.

In my past life as a software designer, this would be referred to not as a "bug", but as a "feature" (please, no flames, just a little luv...).

In the registry, under the key: HKLM/System/CurrentControlSet/Services/WinSock2,
there are several dummy keys (in the default Wine setup). I imported the WinSock2 tree from my XP installation, and that cured the Socket type not supported message. It looks like it must have been just a message, and not a failure.

But my service still won't start - it reports a service request timeout (that message may be from the app, not Wine).

More digging around debug messages....

ken

austin987 · Post by **austin987** » Tue Dec 09, 2008 7:56 pm

On Tue, Dec 9, 2008 at 6:47 PM, kbbass <[email protected]> wrote:

OK, I think I got something.

In my past life as a software designer, this would be referred to not as a "bug", but as a "feature" (please, no flames, just a little luv...).

In the registry, under the key: HKLM/System/CurrentControlSet/Services/WinSock2,
there are several dummy keys (in the default Wine setup). I imported the WinSock2 tree from my XP installation, and that cured the Socket type not supported message. It looks like it must have been just a message, and not a failure.

But my service still won't start - it reports a service request timeout (that message may be from the app, not Wine).

More digging around debug messages....

ken

So perhaps we need to propagate that key to support that app. What was
in that key?

--
-Austin

kbbass · Post by **kbbass** » Wed Dec 10, 2008 9:29 am

austin987 wrote: So perhaps we need to propagate that key to support that app. What was
in that key?

--
-Austin

I can send you the exported key file if needed, but it might be easier to just go to any windows installation and look for yourself.

It seems to be just an enumerated listing of supported protocols with descriptions.

ken

austin987 · Post by **austin987** » Wed Dec 10, 2008 12:24 pm

On Wed, Dec 10, 2008 at 8:29 AM, kbbass <[email protected]> wrote:

austin987 wrote:
So perhaps we need to propagate that key to support that app. What was
in that key?

--
-Austin
I can send you the exported key file if needed, but it might be easier to just go to any windows installation and look for yourself.

It seems to be just an enumerated listing of supported protocols with descriptions.

ken

I didn't have a windows box handy at the time. How much of that key
needs to be present? Does it just need the Winsock2 key? The version
key?

What app is this?

--
-Austin

kbbass · Post by **kbbass** » Thu Dec 11, 2008 9:40 am

austin987 wrote: I didn't have a windows box handy at the time. How much of that key
needs to be present? Does it just need the Winsock2 key? The version
key?

What app is this?

--
-Austin

The contents of the key seem to be a list of supported network types. Looking at the debug output, the app enumerates the entries in both branches (under the Parameters key). So the only entries you would need would be for whatever network types are available on the linux system.

Also, I believe (not 100%) that it is not my app that looks at this key, but maybe the WSock2 DLL itself, when it gets loaded. My app simply listens for incoming tcp connections on one port. Nothing too exotic.

BTW: this is a server that is a backend to a proprietary (ie, not available publicly) graphics application suite . The network part is simply the doorway for processing requests.

ken

austin987 · Post by **austin987** » Thu Dec 11, 2008 10:26 am

On Thu, Dec 11, 2008 at 8:40 AM, kbbass <[email protected]> wrote:

austin987 wrote:
I didn't have a windows box handy at the time. How much of that key
needs to be present? Does it just need the Winsock2 key? The version
key?

What app is this?

--
-Austin
The contents of the key seem to be a list of supported network types. Looking at the debug output, the app enumerates the entries in both branches (under the Parameters key). So the only entries you would need would be for whatever network types are available on the linux system.

Also, I believe (not 100%) that it is not my app that looks at this key, but maybe the WSock2 DLL itself, when it gets loaded. My app simply listens for incoming tcp connections on one port. Nothing too exotic.

BTW: this is a server that is a backend to a proprietary (ie, not available publicly) graphics application suite . The network part is simply the doorway for processing requests.

ken

A) Can you test and see how much of the key is needed? I.e., try
deleting a bit at a time to see when it stops working?

B) Is there some reason you can't name the application?

--
-Austin