OSQA is unmaintained. Help us figure out where to go from here.

if large send offload (ipv4) setting is enabled on the server (default nic setting) and disabled on the client (default nic setting) what problems can arise from a mismatched LSO setting if any? is there any indication in WS trace that large send offload (ipv4) is enabled/disabled on the NIC?

Thanks

asked 27 Oct '10, 10:25

net_tech's gravatar image

net_tech
116303337
accept rate: 13%

retagged 07 Jan '11, 02:51

martyvis's gravatar image

martyvis
8911525


LSO is an internal process - when the packets go out on the wire, they are not larger than a normal packet. Just like TCP Segmentation Offload and Large Receive Offload, this feature is designed to improve performance by using the brains of the adapter for certain tasks.

See http://www.chappellseminars.com/10blog0907.html (and the image of a LSO capture) for the effect of LSO on Wireshark. In essence, if Wireshark is running on the sending machine that supports LSO, Wireshark will see unusually high frame length values when LSO is in use.

I don't image mismatched LSO settings should cause a problem because again, on the wire the packets are normal size.

permanent link

answered 27 Oct '10, 12:12

lchappell's gravatar image

lchappell ♦
1.2k2730
accept rate: 8%

I am troubleshooting an RDP issue ("Because of an error in data encryption, this session will end. Please try connecting to the remote computer again) and came across a long thread on MS forum, where the problem seem to be related to LSO setting of the NIC. I thought miss-matched LSO setting (server – client) had something to do with it, but apparently not.

MS Forum Link

permanent link

answered 27 Oct '10, 12:39

net_tech's gravatar image

net_tech
116303337
accept rate: 13%

edited 27 Oct '10, 12:41

1

As Laura said, "LSO is an internal process - when the packets go out on the wire, they are not larger than a normal packet." LSO, like TSO and LRO, just hands some of the job of processing packets from the host's TCP/IP stack to the adapter's TCP/IP stack; it doesn't affect what's on the wire, unlike, for example, Ethernet full and half duplex, so there's no need for the settings on the machines to match.

(27 Oct '10, 16:01) Guy Harris ♦♦

This is almost identical to my problem, the only difference is my Windows 2008 is on VMWare server.

http://www.petri.co.il/network-issues-with-windows-server-2008-rdp-on-dell-servers.htm

What I am getting out of this is that everything that makes logical sense and works on the physical network DOES NOT, when virtualization is involved.

(28 Oct '10, 08:49) net_tech
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×14
×7
×3
×3

question asked: 27 Oct '10, 10:25

question was seen: 13,221 times

last updated: 07 Jan '11, 02:51

p​o​w​e​r​e​d by O​S​Q​A