WinGate SOCKS server can't start, binding error for 1080port

[chuaneow]

Hello. Good day, everybody. Would like to get advices and solutions from you who is reading this topic.
Previously my SOCKS server service is working well. After one time I restarted my computer, the WinGate SOCKS service server cannot start due to the binding error for port 1080. If I change the port from 1080 to other, then it will run as normal... But if change back to port 1080, will get the exclaimation mark sign telling the SOCKS service server cannot start due to binding error. Please help me in solving this problem. Thanks.

Regards.

[neil]

This sounds like you have something else already running on port 1080 when the WinGate Socks proxy attempts to start. To check if this is so, stop the WinGate Engine (so that the icon turns red) and then from a command prompt type:

netstat -an |more

and look for port 1080. If it appears in this list then you have another application running on your PC that is using the socks port. You can use Port List to find out what this application is called. (Port List is a program that comes with the NetPatrol suite which can be downloaded from http://www.wingate.com/download.php).

If there is nothing using port 1080 when WinGate is stopped you could try deleting and then re-creating the Socks Proxy.

Regards

Neil

[chuaneow]

Hi Neil,

Thanks for your fast response. Will try out the suggestion ASAP. And will update the progress.

Thanks for once more.

Regards,
Chuaneow[/i]

[kgoodknecht]

Hello. Good day, everybody. Would like to get advices and solutions from you who is reading this topic.
Previously my SOCKS server service is working well. After one time I restarted my computer, the WinGate SOCKS service server cannot start due to the binding error for port 1080. If I change the port from 1080 to other, then it will run as normal... But if change back to port 1080, will get the exclaimation mark sign telling the SOCKS service server cannot start due to binding error. Please help me in solving this problem. Thanks.

Regards.

I had the same thing happen to me a couple of years ago, one of the Windows services decided it wanted to use port 1080 I move Socks to 3080 and that fixed it and it's been like that ever since.

[chuaneow]

I had the same thing happen to me a couple of years ago, one of the Windows services decided it wanted to use port 1080 I move Socks to 3080 and that fixed it and it's been like that ever since.[/quote]


Hi, kgoodknecht. Yeah, this is what I am using now. Change the SOCKS to use other port. But still I hope can use back the port 1080.

[kgoodknecht]

I had the same thing happen to me a couple of years ago, one of the Windows services decided it wanted to use port 1080 I move Socks to 3080 and that fixed it and it's been like that ever since.


Hi, kgoodknecht. Yeah, this is what I am using now. Change the SOCKS to use other port. But still I hope can use back the port 1080.

I don't remember what the service was but I know it was a service in which there was no way to set the listener port. So I just used 3080 because I know there are no Windows services that will want use that TCP port anyway. I'm still using 3080, it just requires me to configure the Apps that use Socks to look on port 3080.

[chuaneow]

I had the same thing happen to me a couple of years ago, one of the Windows services decided it wanted to use port 1080 I move Socks to 3080 and that fixed it and it's been like that ever since.


Hi, kgoodknecht. Yeah, this is what I am using now. Change the SOCKS to use other port. But still I hope can use back the port 1080.

I don't remember what the service was but I know it was a service in which there was no way to set the listener port. So I just used 3080 because I know there are no Windows services that will want use that TCP port anyway. I'm still using 3080, it just requires me to configure the Apps that use Socks to look on port 3080.

I see... I am not sure which application is using the port 1080 in my computer. But will check soon.

[adrien]

If you want to know which application uses which port, you can use our PortList tool which is part of NetPatrol.

Some trojans install a back-door SOCKS server, which could run on port 1080. You certainly don't want to be running an open SOCKS server you don't know about.

Adrien