adrien,labull,stanwoods,tim,ChrisH..please HELP ME OUT!!!!!

Nov 24 03 8:57 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.....

Nov 24 03 11:09 am

Hi,

I don't know what that error message means - developers will know. I would suggest as an interim measure to create a UDP mapping from port 1080 to 1081 and see if that works. Disable SOCKS server on 1080 and create new one on 1081. Then create UDP map from 1080 to 1081 on server 127.0.0.1. Hopefully that will work until you can solve why 1080 fails.

Nov 24 03 12:34 pm

ChrisH wrote:Hi,

I don't know what that error message means - developers will know. I would suggest as an interim measure to create a UDP mapping from port 1080 to 1081 and see if that works. Disable SOCKS server on 1080 and create new one on 1081. Then create UDP map from 1080 to 1081 on server 127.0.0.1. Hopefully that will work until you can solve why 1080 fails.

Hi Chrish Thanks for ur Suggestion....it work for a while on port 1081..but then i restarted my PC again to check....same probelm
now the sock proxy fails on both 1080, and 1081
now i am running it on port 1090...i restarted to check if something bad happens again....but now it's working fine on port 1090....

now i am afraid when port 1090 is going to fail(Suspence.. :) HEHE)

well
I can't understand this probelm??????

i am having this problem sience ver 4.0.....
but then i was not bound with just wingate.....
but now i am totally depends on wingate..........
why don't they just still can't fix this issue....
-------------
if i am not wrong i always get this error when my cache folder size get higher then 1GB? i can't understand the link between cache and socks???

have u ever get this kind'a error....in ur exprience???
......................

Nov 24 03 2:05 pm

I haven't seen this issue before - I don't really need to use SOCKS server. Interesting theory on cache size and SOCKS problem - have you tried purging cache more frequently than once a day to see if that changes anything or making cache size smaller or not caching at all? I would think though, that if WG can't bind to a service something else is using that port. If you run netstat -an you should be able to see if something else is using 1080. Any AV or Gatefilter running on this machine as well? Sorry, I'm out of ideas at this point.

Nov 24 03 9:53 pm

I tried to use netstat but i can't see anyting useing port 1080.......
but today when i restart my server...it allworks fine.....now i have 2 socks proxy servers with port 1080 and 1090....
I am NUMB now........i don't know what to say....
and as far as the cache....i am using wingate as a cache server.....
i do really need cache.....
is there any solution for the best and realiable cache server running at the background for the wingate...
request from the clients passes thought the wingate, to the cache server....?????
---------------------------------
just can anyone tell me what was the probelm...
because i am still wating for the socks proxy to GO Down...