One other curious thing, on a virtual machine the source port for the first packet is a random 62xxxx. On the real machine the source port is always 500. Could this be the reason ?
Thanks On Wed, Dec 16, 2015 at 6:02 AM, Bogdan Ciulei <[email protected]> wrote: > I think I've found a problem by taking a wireshark cap. > > The reply arrives from the gateway, but the delay is huge , ~20 seconds. > All this must be caused by the stream tracking crap in the Killer drivers. > It's either that or the reply doesn't get forwarded to the Shrew Soft > filter driver at all, which would be consistent with being able to connect > from within a virtual machine. > > I wonder , Can set the timeout for connection anywhere ?. Its worth a shot > I'd say. > > Thanks > Bogdan > > On Wed, Dec 16, 2015 at 5:21 AM, Bogdan Ciulei <[email protected]> > wrote: > >> Hello, >> >> I have recently upgraded my home system to a new one ( and expensive ) >> Unfortunately, while everything else is great , it had the Killer LAN e2400 >> on board NIC . >> To my disappointment and horror Shrew Soft refused to connect on the new >> system, the OS being the same as before, Windows 10x64. >> >> I need this connection urgently as it is required for my work place , I >> do not have an option to it and not having it means not being able to work. >> I've managed to solve it somehow, Shrew Soft still runs in a Virtual Box >> machine, but you can imagine is is inconvenient. >> >> I am available to provide a Wireshark capture, Shrew Soft logs ( from >> what I 've seen it never gets a reply to the hello packets ) or even a >> Team Viewer connection to my machine. >> I can not provide the physical adapter though, but it is fairly common >> with the latest z170a boards. >> >> >> Many thanks >> >> Bogdan Ciulei >> > >
_______________________________________________ vpn-help mailing list [email protected] https://lists.shrew.net/mailman/listinfo/vpn-help
