|
|
On 11/10/05, Robert Kuszinger <kuszinger@xxxxxxxxx> wrote: > > > Hi all! > > > // !!Derrick, thanks for the idea with Ethereal monitoring. // > > So, it seems that all request from the client are coming in correctly: > > > (client is ....99.6, server is 99.1) > > > (Some samples, remote desktop and http requests. I was monitoring the TAP > interface... what else to do?) > > No. Time Source Destination Protocol > Info > 1 0.000000 172.16.99.1 172.16.99.3 NBNS > Name query NB SZFVAR<1b> > 2 0.750961 172.16.99.1 172.16.99.3 NBNS > Name query NB SZFVAR<1b> > 3 1.503354 172.16.99.1 172.16.99.3 NBNS > Name query NB SZFVAR<1b> > 4 6.390920 172.16.99.6 172.16.99.1 TCP > 3087 > 3389 [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1366 > 5 9.388672 172.16.99.6 172.16.99.1 TCP > 3087 > 3389 [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1366 > 6 14.367642 172.16.99.6 172.16.99.1 TCP > 3088 > http [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1366 > 7 15.379773 172.16.99.6 172.16.99.1 TCP > 3087 > 3389 [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1366 > 8 17.287473 172.16.99.6 172.16.99.1 TCP > 3088 > http [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1366 > 9 23.338659 172.16.99.6 172.16.99.1 TCP > 3088 > http [SYN] Seq=0 Ack=0 Win=16384 Len=0 MSS=1366 > > > Well, no answer is sent back to the client. > Here is the routing table of the server - what could be the problem? I still > don't understand. I assume this is on the client side. What packets do you see on the server side? No inbound packets on the TAP interface could indicate that there is a firewall on the server blocking the packets. -- Leonard Isham, CISSP Ostendo non ostento. ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |