v5.2.2 SOCKS error 10013

[daveg]

I have just upgraded our WinGate software to v5.2.2 (was v5.0.5) to try to correct a strange problem with the SOCKS service. However the problem still occurs even after the upgrade.

The SOCKS service (set to use the default port 1080) fails to start and the System Messages tab shows the error "Service startup complete or partial failure - Check your bindings".
The SOCKS service log file shows "Error: Service failed startup on interface 127.0.0.1:1080 error 10013" (along with a similar message stating the service failed to start on the systems local IP address).

If I run "netstat -an" as recommended in a previous similar posting (to which I could see no resolution), I can only see one line with a port 1080 as follows:

TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING

I presume that this is an indication that this port is available for use.
There is no mention of anything else using this port.

If I create a new SOCKS server on port 1081, it starts fine (the previous poster also did this, but said that this only worked for a short while, then started to fail in the same way).

Can you suggest what might be wrong here?

[Pascal]

If I run "netstat -an" as recommended in a previous similar posting (to which I could see no resolution), I can only see one line with a port 1080 as follows:

TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING

I presume that this is an indication that this port is available for use.
There is no mention of anything else using this port.

Did you run that netstat -a with WinGate running or with WinGate stopped ? If it gives you that output with WinGate stopped, something is already using that port (Hence the failure to bind to it)

What you can try is to download NetPatrol (And only install the PortList application included with it) to see which application is then using that port.

[daveg]

I re-ran netstat -an with WinGate stopped and closed and got the same result, i.e.:

TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING

I then downloaded NetPatrol and installed just the QBik PortList utility as suggested. When I run this, the only entry for port 1080 was:

TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING 8
PID 8 corresponds to the 'System' process.
Presumably this means that for some reason the system has port 1080 open?

Where do I go from here?

Thanks in advance
Dave

[Pascal]

Presumably this means that for some reason the system has port 1080 open? Where do I go from here?

I'm not 100% sure what other services could potentially have port 1080 open. At this point, I'd recommend you go through the list of running applications and stopping them one at a time to see which one releases that port number. (Might be a chat client ?)

What OS are you running, btw ? XP ?

[daveg]

If it's the 'System' process that is using the port, I assume that means it could be an application (running as a service via svchost.exe) or a genuine service?

I'll try as you suggest as soon as poss. and let you know what that reveals.

Thanks
Dave

[daveg]

Well, I tried as you suggested, i.e. closing all applications and even stopping as many services as I thought were non-standard and non-essential, after which Port 1080 was still listed as TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING. I tried closing the port via QBiks PortList utility, but it remains in the list and no port close failure was reported.

I took a snapshot of the system status (via the System Information MMC) with the apps. and services stopped. I also have a process list for the system whilst it was in this state. If these are helpful in diagnosing the problem, I can send them to you (outside the forum - I'll need an e-mail address).

I'm puzzled as to why it appears to be the 'System' process which is LISTENING on port 1080. If it was a service or an application running as a service, wouldn't you expect to see that service/application listed as the process which has the port open?

Any more ideas? I'm stumped.

Dave

[Pascal]

I took a snapshot of the system status (via the System Information MMC) with the apps. and services stopped. I also have a process list for the system whilst it was in this state. If these are helpful in diagnosing the problem, I can send them to you (outside the forum - I'll need an e-mail address).

That would help, yes. You can email to the address listed in my profile (pascalv at qbik dot com )