If you are suddenly having major issues with zoning and logging in (out of date spells, weird errors, crashing)
AND your setup hasn't changed at all
then you are dealing with packet loss.
It has nothing to do with the last patch. The best thing that you guys can do is
provide a copy of your traceroute to 66.55.145.2 and we can hopefully see a common network node that you guys all have in common. That node is probably damaged or had its configuration changed in the last day.
I had this issue for a solid week recently, and spent a lot of time figuring out who/what/where/when/why of it all. It took a while, but the issue was repaired.
It will look something like...
Quote:
C:\Users\YourNameHere>tracert 66.55.145.2
Tracing route to 66.55.145.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms lolwat [192.168.1.1]
2 31 ms 28 ms 26 ms cpe-65-31-128-1.wi.res.rr.com [65.31.128.1]
3 11 ms 12 ms 12 ms tge7-1.brfdwifb02h.midwest.rr.com [24.164.233.69]
4 14 ms 15 ms 19 ms tge1-6-0-9.gnfdwibb01r.midwest.rr.com [65.29.44.54]
5 19 ms 19 ms 19 ms bu-ether16.chcgildt87w-bcr00.tbone.rr.com [66.109.6.204]
6 16 ms 16 ms 17 ms 0.ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
(snipped short for brevity)
|