Sock Proxy error..Check ur Bidings...

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Sock Proxy error..Check ur Bidings...

Postby max3do » Nov 24 03 12:16 am

Hi
it was all working fine...but science the i last restart my server from a 4 day long session...socks proxy is not working now any more....

when i try to stop and start again the system messages show this error
Object: SOCKS Proxy server
Time: 23-Nov-2003 16:03:31
Message ID: 0506
Description: Service startup complete or partial failure - Check your bindings
---------------------------------------------
in a Log file the error was this

11/23/03 15:58:11 Service stopped
11/23/03 15:58:11 Error: Service failed startup on interface 192.168.0.1:1080 error 10013
11/23/03 15:58:11 Error: Service failed startup on interface 127.0.0.1:1080 error 10013
11/23/03 15:58:11 Error: Service startup complete or partial failure
11/23/03 15:58:11 Service restarted
11/23/03 15:58:11 Configuration changed
--------------------------------------------

what is this error 10013????
---------------------
well any when i change the port to 1081 or something else execpt 1080..
it works fine...

te probelm is this i can't change all of my client socks ports request to 1081 or something else
........cuz this will take a huge amount of time....
-------------------------------------------

i got win2000 server
i gb ram
2.4 GB with HT Processor
and for about 55 clients....
server has just wingate installed on it...
nothing else
no Terminal services etc....
------------------
Please help me out.....
i will add this later
max3do
 
Posts: 45
Joined: Oct 17 03 9:33 pm
Location: Lahore, pakistan

Postby MattP » Nov 25 03 4:27 pm

According to the Winsock error codes that I found this error is a permission denied error. Are you running any other firewall software? Do you have anything else running on this port? What do you see when you do a netstat?
MattP
Qbik Staff
 
Posts: 991
Joined: Sep 08 03 4:30 pm

Postby daynight » Nov 27 03 2:22 pm

the port must be in use , try another ...
daynight
 
Posts: 4
Joined: Nov 10 03 7:36 pm

I had this failure 3 times.. and again today.

Postby sazunike » Aug 31 05 6:19 am

I had the same problem, im using w2k server and latest update in wingate.
I changed the port on socks 3 times.. im kinda tired of configuring all the clients every 3 or 4 month..
It seems like the port stay blocked for ever.. i cant configure it in port 1080 like i have it the first time i installed the proxy, because all the port that were failing are all blocked, i must use a new one.

Nicolas
sazunike
 
Posts: 1
Joined: Aug 31 05 6:11 am

Postby max3do » Sep 01 05 9:41 am

hey sazunike..
I had found a way to Get away this error ..
it's always Hit on Socks Proxy i don't know why ..
no other Service is Using this Port = 1080..
cuz when u creat another service like TCP map serive on Port 1080. it will work fine .. But at the same time if u change the port of socks service it will Fail..
SO here is a Sloution..
Create another serive "TCP map" ON port 1080
and Map it Local binds like if u have configured the socks on 1090 then
map it to 127.0.0.1 and port 1090.
so that u don't have to Change all the clinets Settings.
it's Expreimental cuz it's always work on my side .. don't know about other people.
just give it a try..
but beware this will eat up ur Ram and CPU .. all little bit more then before.
Take care.
i will add this later
max3do
 
Posts: 45
Joined: Oct 17 03 9:33 pm
Location: Lahore, pakistan


Return to WinGate

Who is online

Users browsing this forum: No registered users and 56 guests