WRP authentication problem

[avok]

Hi,

My setup is mentioned in this topic http://forums.qbik.com/viewtopic.php?t=935

I finally managed to run the vpn. Now I have my own PC with IP 192.168.10.2 attached to the server PC with IP 172.16.134.52
On the server PC
I have ordinary user named avok_user, which is assumed from IP 192.168.10.2
I have another user in administrators group named avok, which must be authenticated
Wingate uses his own user database.
All users can access services.
No one can be logged from more than one place at the same time.

On client pc (WinGate VPN and WRP clients installed)
I have user Administrator on the WinGate VPN client.
I have user avok in Win XP, which is currently logged on with administrative rights.
Wingate VPN uses his own user database.

I can freely access the web proxy for example on IP 172.16.134.52 and I see myself correctly as assumed. But I can't access WRP service at all. First the client does not automatically recognize WRP server despite the GDP is running. When I enter it manually and try to use IE to browse a web page it shows an error message that I don't have access to Wingate server. The web proxy and WRP service have exactly the same security settings. Any ideas?

[avok]

It turned out that stupid WRS client is trying to authenticate me with my windows user on the client machine. Once I renamed the user avok in the gateway the problem with access was solved. But now there is another problem. Seems like wingate have countless supply of them :) The WRS cannot connect any application to internet. Take a look at the debug log:

02/09/04 20:05:08 Configuration changed
02/09/04 20:05:17 Service started successfully
02/09/04 20:05:47 192.168.10.2 avok_user 0000001153 Created:
02/09/04 20:05:47 192.168.10.2 avok_user 0000001153 Debug: Request 14 WRP_COMMAND_CONNECT TCP socket 4294967295 192.168.10.2:1641 to 212.91.161.253:80
02/09/04 20:05:47 192.168.10.2 avok_user 0000001153 Debug: Request 14 Creating new socket 2236
02/09/04 20:05:47 192.168.10.2 avok_user 0000001153 Debug: Request 14 starting async connect
02/09/04 20:06:08 192.168.10.2 avok_user 0000001153 Debug: Request 14 connect error 10060
02/09/04 20:06:09 192.168.10.2 avok_user 0000001153 Terminated exit code 0
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Created:
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Request 15 WRP_COMMAND_BIND TCP 192.168.10.2:0 to 0.0.0.0:0
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Request 15 Created Socket 2236
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Setting new client socket port to 4452
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Request 15 bound to 0.0.0.0:4452
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Request 15 sending response packet
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Request 16 WRP_COMMAND_CONNECT TCP socket 2236 192.168.10.2:4452 to 207.36.6.208:80
02/09/04 20:08:06 192.168.10.2 avok_user 0000001155 Debug: Request 16 starting async connect
02/09/04 20:08:27 192.168.10.2 avok_user 0000001155 Debug: Request 16 connect error 10060
02/09/04 20:08:45 192.168.10.2 avok_user 0000001155 Debug: Request 17 WRP_COMMAND_CLOSESOCKET Socket 2236
02/09/04 20:08:45 192.168.10.2 avok_user 0000001155 Terminated exit code 0