Re: wodVPN For 1 Server - N Client Scenario (General questions)

by wodDamir, Monday, October 13, 2008, 11:22 (5676 days ago) @ Tanmay Soni

Hi Soni,

You can't get instance of wodVPN there, however, in that case you should use Connected event to start new instance of wodVPN which will accept new connection.

In this case, clients will be names same. Also, you should lower the Timeout property in Mediator (determines how long it takes before mediator will ignore the last request), and set client instances to Retry (RetryWait and RetryCount properties) if no connection is established.

Hope this helps.

Regards,
Damba

locked

2481 views

Complete thread:

wodVPN For 1 Server - N Client Scenario - Tanmay, 2008-10-10, 17:54
- Re: wodVPN For 1 Server - N Client Scenario - wodDamir, 2008-10-10, 21:02
  - Re: wodVPN For 1 Server - N Client Scenario - tanmay, 2008-10-11, 15:48
    - Re: wodVPN For 1 Server - N Client Scenario - wodDamir, 2008-10-11, 17:53
      - Re: wodVPN For 1 Server - N Client Scenario - wodDamir, 2008-10-11, 17:58
        Re: wodVPN For 1 Server - N Client Scenario - Tanmay Soni, 2008-10-13, 08:50
        Re: wodVPN For 1 Server - N Client Scenario - wodDamir, 2008-10-13, 11:22

...with WOD's excellent support I was able to bypass Winsock and focus on the task at hand...

Sander Pool

Rhapsody Networks

Thank you for the great customer service ... I am really impressed with the wodSSH ActiveX control.

Andrew Ross

Kiwi Enterprises

It is very refreshing to find such helpful, knowledgeable and quick responding technical support.

Jason Sears

CompuSource Systems, Inc.

...with a minimum of effort as the DLL interface was written with such simplicity...

Zack Menendez

Mapframe Corporation

May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?

Michael Barnett

Full Spectrum Telecommunications