Re: Concurrent clients to a single VPN server

On Mon, 28 Jun 2004, [windows-1252] Fabio Antonio Esquivel Chacón wrote:

> > > I had setup an OpenVPN server in Windows Server 2003 successfully. The 
> > > server has a public IP address and is listening on its default port.
> > >
> > > My client (on WinXP) works flawlessly as well.
> > >
> > > I then added a second TAP adapter on the Server in order to add a 
> > > second VPN interface, as to allow another client to connect 
> > > concurrently to the same LAN.
> > >
> > > The LAN I'm accessing is 10.3.1.0/24, so I defined its first VPN 
> > > interface as 10.3.2.1/24 and the client as 10.3.2.2. No problem there.
> > >
> > > The second interface is defined as 10.3.3.1/24 and another client as
> > > 10.3.3.2, but it seems not to be able to reach the LAN as 10.3.2.2 does!
> > >
> > > I can ping from 10.3.2.2 to 10.3.2.1 and into the LAN (10.3.1.x), but 
> > > I cannot ping from 10.3.3.2 to 10.3.3.1 and, obviously, not to the LAN 
> > > from that second interface either...
> >
> > Could you let us see your configs and the output from openvpn?
> I'm attaching a ZIP with the server OVPNs, the client's OVPNs and the 
> respective logs for each connection at the client computer.
>
> Note that I'm trying both connections to ports 5000 (default) and 5001 from 
> the same client but NOT concurrently (I try one first, then close it and try 
> the other one), but I get the same results when trying both connections 
> concurrently from two different client computers.

I can't see anything wrong with your configs.

Have you checked that there is no firewall in the way blocking port 5001 
but allows port 5000?

Check with a packet sniffer, like Windump that the packets really arrive 
on your server on port 5001.


--
_____________________________________________________________
Mathias Sundman                  (^)   ASCII Ribbon Campaign
NILINGS AB                        X    NO HTML/RTF in e-mail
Tel: +46-(0)8-666 32 28          / \   NO Word docs in e-mail