Socks Proxy problem

Jul 12 04 8:53 pm

Hi, i just installed wingate, and am trying to bind ip addresses to socks proxys.
It's only showing one ip though, and i can only bind to that one..

i've tried "ipconfig /all" and such, and it lists all ip addresses, i've tried rebooting, restarting wingate, and it still wont show the ip's in the binding part, and wont let me bind to any of them.

i'm running windows server 2003 on a dedicated server.

it's showing 127.0.0.1 and 67.x only. the 127 one is like a blue U looking icon, and the 67 one is like an adapter icon.
i have 196 to 259, and only the 196 is able to be binded. i am 99% sure the subnets, masks, and configuration is all correct.

if anybody knows why i'm not able to bind to my ip addresses please let me know.

thanks.

Jul 13 04 7:28 pm

could somebody please help me out here?

Jul 13 04 7:32 pm

What OS are you using?

Jul 14 04 7:03 am

like i said.. i'm running windows server 2003 on a dedicated server.

Jul 24 04 8:53 am

altgamer wrote:like i said.. i'm running windows server 2003 on a dedicated server.

best solution: create a new socks service on port 1081 and configure clients to work on 1081.

Jul 24 04 10:23 am

Hi

WinGate 5.x used a winsock call to enumerate IP addresses. This had a maximum limit of addresses it would return. Looks like you are over that limit so it is showing none.

There are 2 options. With WinGate 5.x you can manually define interfaces in the registry. You would need to add REG_DWORD entries under

HKEY_LOCAL_MACHINE\Software\Qbik Software\WinGate\Settings\Interfaces

just make the name of the entry the string value of the IP you want to insert, e.g. "192.168.0.1". It doesn't matter which value you give it, only the name is used.

The other option is to upgrade to version 6.0, which uses a different method to enumerate IP addresses.

Adrien