Here's the only other thing I can think of...
Windows Vista's TCP/IP stack has new auto-tuning algorithms that
automatically and dynamically adapt the TCP receive windows to the properties
of the network path between the endpoints. This allows the stack to fully
utilize the bandwidth between two endpoints (especially in high-delay
conditions) and dynamically adapt to changing bandwidth and delay
characteristics. But some network devices (older / without recent firmware)
may not support this and drop some / all of your packets on the floor!
You can disable auto-tuning via NETSH to see if it's affecting your ability
to connect across non-compliant network devices (and there are some!).
Stuart.
-----------
"Robert Fischer" wrote:
> Hello Stuart
>
> Thanks for your suggestion but k899148 doesn´t solve the problem:
> I´m working with static packet filters (netsh ipsec static) and I´ve opened
> all ports on the filesserver FS-WAN for the VPN-Server VPN-WAN.
> The local Server Srv-LAN has the same packet filter configuration ref. VPN.
> All Vista Workstations located as domain members in my workplace environment
> don´t have any problems and they find exactly the same opened ports!
>
> I´m looking forward to find a solution...
> Best regards
>
>
> Robert
>
> "Stuart [MVP]" <StuartMVP@discussions.microsoft.com> wrote in message
> news:89050F01-2DA3-42E9-A608-EFD48783CDA1@microsoft.com...
> > The article below may (or may not) be related to your problem. Take a look
> > and let us know:
> >
> > http://support.microsoft.com/default...b/899148/en-us
> >
> > Regards,
> >
> > Stuart.
> >>
>
>
>