I have a GPO applying policy-based QoS to mark DFSR.exe (replication traffic).
The policy shows up in GPRESULT output but netmon shows the packets being marked DSCP 0 in the IP header. The server has been rebooted. I don't see any errors in the log. I use the same technique to mark Lync voice traffic and it works.
I wondered if the difference could be that DFSR.exe is a system process, not a user process. To test, I tried marking ping.exe - no difference. The packet scheduler is enabled in the NIC. We have manually (not GPO-enabled)
the same on our Lync VMs.
Where else should I look?
This the policy:
QoS Policies Policy Name DSCP DFS Replication (server-to-server) 10
Protocol: TCP Application: DFSR.exe Source IP: Any Destination IP: Any Source Port: Any Destination Port: Any DO-CC-QosSettings-v0.2
The Netmon trace shows this:
Ipv4: Src = xxxxx, Dest = yyyy, Next Protocol = TCP, Packet ID = 25497, Total IP Length = 176+ Versions: IPv4, Internet Protocol; Header Length = 20
- DifferentiatedServicesField: DSCP: 0, ECN: 0
DSCP: (000000..) Differentiated services codepoint 0
ECT: (......0.) ECN-Capable Transport not set
CE: (.......0) ECN-CE not set
TotalLength: 176 (0xB0)
Identification: 25497 (0x6399)+ FragmentFlags: 16384 (0x4000)
TimeToLive: 128 (0x80)
NextProtocol: TCP, 6(0x6)
Checksum: 0 (0x0)
SourceAddress: 10.240.0.184
DestinationAddress: 10.126.11.55+ Tcp: Flags=...AP..., SrcPort=49241, DstPort=57336, PayloadLen=124, Seq=184338446 - 184338570, Ack=1214281947, Win=511