i saw an issue similar to this when working on a Disaster Recovery site. We had touble building devices when they tried to contact active directory, as well as when the users logged in. When runninga trace to the AD server we received similar results. However, reseting one of the switches along the route fixed the issue.…
Im guessing its still not sorted... Trace results as follows (not that it matters too much at this stage though, right?): Tracing route to patchserver.crypticstudios.com [208.95.185.41] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms . [192.168.2.1] 2 7 ms 6 ms 6 ms 10.98.216.1 3 9 ms 13 ms 9 ms…