[vpn-help] Shrew + Win 7 (64) - no incoming packets

[Service Lists]

Hi Kevin
(whoops, sent the previous mail directly to you by mistake, was meant
to go to the list, sorry)

Sorry for the long delay, customer was not responding. Here are the answers:
1) No, only the shrewsoft-client. First there was the cisco-vpn-client
installed too, but in the meantime we tried on a other notebook,
without any other vpn-client.
2) Yes, they're member of a windows domain
3) We can connect, but can't reach any resources
4) The list looks like this:
- Client for Microsoft Networks
- Shrew Soft Protocol Filter
- Deterministic Network Enhancer
- File an Printer Sharing for Microsoft Networks
- QoS Packet Scheduler
- Internet Protocol

On your list there is the shrew soft "lightweight filter", on mine the
"protocol filter". What's the meaning of this difference? I have a
different notebook, where the client is working, and there's also the
lightweight filter.

Regards
Mike

2013/12/17 Service Lists <lists at michael-bruenisholz.ch>:
> Hi Kevin
>
> Sorry for the long delay, customer was not responding. Here are the answers:
> 1) No, only the shrewsoft-client. First there was the cisco-vpn-client
> installed too, but in the meantime we tried on a other notebook,
> without any other vpn-client.
> 2) Yes, they're member of a windows domain
> 3) We can connect, but can't reach any resources
> 4) The list looks like this:
> - Client for Microsoft Networks
> - Shrew Soft Protocol Filter
> - Deterministic Network Enhancer
> - File an Printer Sharing for Microsoft Networks
> - QoS Packet Scheduler
> - Internet Protocol
>
> On your list there is the shrew soft "lightweight filter", on mine the
> "protocol filter". What's the meaning of this difference? I have a
> different notebook, where the client is working, and there's also the
> lightweight filter.
>
> Regards
> Mike
>
> 2013/11/27 Kevin VPN <kvpn at live.com>:
>> On 11/26/2013 10:08 AM, Service Lists wrote:
>>>
>>> Thanks for the hint, but sadly this didn't help in my case. Also tried
>>> not just starting as an admin, also installing the whole vpn-client as
>>> admin, but with the same result.
>>>
>>> Regards
>>> Mike
>>>
>>> 2013/11/13  <lst_hoe02 at kwsoft.de>:
>>>>
>>>>
>>>> Zitat von Service Lists <lists at michael-bruenisholz.ch>:
>>>>
>>>>
>>>>> Hello Jörn, Hello Kevin
>>>>>
>>>>> Altough this is a rather old thread, i'm really wondering if you found
>>>>> a solution for your problem. I ran into the same problem with some of
>>>>> our vpn-clients, on different windows-versions. It seems like the
>>>>> returning pakets reach the client-machine, at least i can see some
>>>>> returning pakets in wireshark.
>>>>> Strange is the fact, that some other vpn-clients, with the same
>>>>> configuration and client-version, run smoothly.
>>>>>
>>>>> I'd be very happy if you've found a solution to your problem, because
>>>>> i'm really stuck at this.
>>>>>
>>>>> Best regards
>>>>> Mike
>>>>
>>>>
>>>>
>>>> We sometimes get this repaired by starting the VPN Manager once as
>>>> Administrator. Not sure why it works afterwards and it wasn't a solution
>>>> in
>>>> any case :-(
>>>>
>>
>> Hi Mike,
>>
>> Some questions:
>>
>> 1. Do you have any other VPN software on the non-working machines?
>>
>> 2. Are the non-working machines on a Windows domain?
>>
>> 3. Does the Shrew client connect (you see "tunnel enabled" on the connect
>> dialog) but you can't reach network resources, or can you not connect at
>> all?
>>
>> 4. If you go into the network connection properties (e.g. Local Area Network
>> Connection) and look at the list of adapters, where is Shrew in the list?
>> For instance, one of mine reads:
>>
>> Client for Microsoft Networks
>> VMware Bridge Protocol
>> Shrew Soft Lightweight Filter
>> QoS Packet Scheduler
>> File and Printer Sharing for Microsoft Networks
>> Internet Protocol Version 6 (TCP/IPv6)
>> ...
>>
>>
>>
>> _______________________________________________
>> vpn-help mailing list
>> vpn-help at lists.shrew.net
>> https://lists.shrew.net/mailman/listinfo/vpn-help