Revision history [back]

RST and Data flags = 1. SYN, SYN-ACK or FIN flags all = 0

I had observed a number of t-ring packets in packet traces from the previous week that appeared to be faulty or suspect of some type of server problem.

I emailed them about these t-ring 'errors'. I received no reply, (which is pretty typical in my experience) as to the nature or source of the problem. But interestingly the t-ring errors disappeared from my subsequent traces since reporting this.

Now, I have this Incomplete (40) packet from what is a Microsoft server. Anyone ever seen a (40) ?

RST and Data flags = 1. SYN, SYN-ACK or FIN flags all = 0

I had observed a number of t-ring packets in packet traces from the previous week that appeared to be faulty or suspect of some type of server problem.

I emailed them about these t-ring 'errors'. I received no reply, (which is pretty typical in my experience) as to the nature or source of the problem. But interestingly the t-ring errors disappeared from my subsequent traces since reporting this.

Now, I have this Incomplete (40) packet from what is a Microsoft server. Anyone ever seen a (40) ?

RST and Data flags = 1. SYN, SYN-ACK or FIN flags all = 0

I had observed a number of t-ring [t-ring-fdv2.msedge.net] packets in packet traces from the previous week that appeared to be faulty or suspect of some type of server problem.

I emailed them about these t-ring [t-ring-fdv2.msedge.net] 'errors'. I received no reply, (which is pretty typical in my experience) as to the nature or source of the problem. But interestingly the t-ring errors disappeared from my subsequent traces since reporting this.

Now, I have this Incomplete (40) packet from what is a Microsoft server. Anyone ever seen a (40) ?