Not logging into the vpn before logging into a machine would mean that they are logging in with cached credentials. So, anything to their profile should generally stay as it was, but their machine did not actually actively log on to the domain, so it might have some weird issues.
Is anything about using the web tied into the domain - any proxies they have to authenticate with?
Is IM internal or external? Are we talking AOL IM or an in house IM?
The users don't use proxies to reach the web. We do have Bluecoat and we use WCCP to help stem the flow of traffic and keep surfers honest. However, these outages are not tied to reaching website. It is tied to getting name resolution.
They are not using an in-house IM. It is either YAHOO or AOL.
FYI, I learned later that many of these users are logging into their own corporate domain or home domain before launching VPN to us and then receiving our DDNS servers to do name resolution.
I'm thinking that this might be a part of the problem, also.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...