TCP Optimizer 4 (Windows 7 / 8 / 10 / 2012/2019 Server are all supported)

**Djfe** · 06-26-18, 02:21 AM

Might be, though I've selected only one of them, after all (in the dialogue above)

The output:

**Philip** · 07-11-18, 02:50 AM

We found a typo with applying the LargeSendOffload, it's been corrected in the latest TCP Optimizer version.

**Djfe** · 07-11-18, 05:15 AM

Thx, I can confirm that it's working now

Have you looked at RSS as well?
I'm ready to provide any info you need for fixing the bug, that prevents your tool from reading out RSS values.
Get-NetAdapterRss shows "enabled true" after all ^^

Setting rss to false in the tool -> Get-NetAdapterRss still shows "enabled true" (after reboot)

EDIT:
Setting ecn to enabled/disabled works

"Default" just keeps the value as it is. (true or false)
Is that intended?

**Philip** · 07-11-18, 12:05 PM

"Default" applies the command as described in the MS documentation, some settings have "enabled/disabled/default" option. Will check RSS. Glad Lso is working as intended now.

**Philip** · 07-11-18, 05:53 PM

RSS at program start is read from:

netsh int tcp show global
Receive-Side Scaling State: enabled

**ukue** · 07-11-18, 10:28 PM

Still getting blank space in RSS and RSC current values

**Philip** · 07-12-18, 12:43 AM

Can you post a screenshot of command prompt: netsh int tcp show global

If it doesn't have lines for "Receive-Side Scaling State", or "Receive Segment Coalescing State" they will not show at program start. This is likely OS-version, or NIC dependent.

The program should still apply the settings, if available.

**Ashdaw** · 07-12-18, 02:49 AM

I just downloaded the latest 4.08 and I am wondering if I should be changing the CTCP to Cubic?
One other thing, would it be advantageous to change the connection speed to 100Mbps? Name: Net.108.jpg
Views: 308
Size: 49.4 KB

Name: Net.108.jpg
Views: 308
Size: 49.4 KB

**ukue** · 07-12-18, 10:49 AM

Originally Posted by Philip

Can you post a screenshot of command prompt: netsh int tcp show global

If it doesn't have lines for "Receive-Side Scaling State", or "Receive Segment Coalescing State" they will not show at program start. This is likely OS-version, or NIC dependent.

The program should still apply the settings, if available.

**Djfe** · 07-12-18, 11:53 AM

For me those settings are the first two entries (I think)

I'm not sure whether your programm gets them in english or german though (when relying on powershell)

**Philip** · 07-12-18, 12:15 PM

Originally Posted by Ashdaw

I just downloaded the latest 4.08 and I am wondering if I should be changing the CTCP to Cubic?
One other thing, would it be advantageous to change the connection speed to 100Mbps?

Ashdaw, I would put your advertised connection speed in the TCP Optimizer. With Windows 10, it won't make much difference. As to "Cubic" vs "CTCP" they are the two best choices currently, both are good, you can use either.

**Philip** · 07-12-18, 12:25 PM

Originally Posted by Djfe

For me those settings are the first two entries (I think)

I'm not sure whether your programm gets them in english or german though (when relying on powershell)

The program reads them in your native Windows language, it shows empty if it does not recognize the setting. It will still apply the settings correctly, it just wont read the RSS/RSC on program start because of the language difference. We may add those translations in the next version, thanks for the screenshots.

**Ashdaw** · 07-13-18, 09:18 AM

Thanks Philip, I will do that.

**Philip** · 07-14-18, 01:17 AM

ukue and Djfe, can you please try the following command in command prompt (not PowerShell):

chcp 437 && netsh int tcp show global

Does it show the results in English?

Thanks.

**ukue** · 07-16-18, 02:52 PM

Nope, It doesn't. It is in the OS language ( spanish in my case)

**Djfe** · 07-17-18, 01:07 AM

I can confirm that.
It still displays the message in German for me

**Philip** · 07-18-18, 11:58 PM

What about when executed as two separate commands, i.e.

chcp 437 [ENTER]

netsh int tcp show global

If that doesn't work, I am afraid we'd have to parse the output for different languages to get it to display properly on program start :/

**Djfe** · 07-19-18, 01:57 AM

Doesn't make any difference sadly
seems like MS kinda screwed up there for netsh
And you definitely aren't the only one puzzled by that

Even this doesn't work:
https://itworldjd.wordpress.com/2013...hell-language/

(I found lots of stackoverflow threads and stuff like that

Even the go language had to work around it haha
https://github.com/golang/go/issues/14859
https://go-review.googlesource.com/c/go/+/20865
https://go-review.googlesource.com/c/go/+/21195)

But they don't seem to be willing to change it's functionality anymore.
https://docs.microsoft.com/en-us/win...es/netsh/netsh

It is recommended that you use Windows PowerShell to manage networking technologies in Windows Server 2016 and Windows 10 rather than Network Shell. Network Shell is included for compatibility with your scripts, however, and its use is supported.

Are there infos you can't get with powershell/WMI right now?

There are lots of available APIs

Code:

Get-NetAdapter
Get-NetAdapterRsc
Get-NetAdapterRss
Get-NetOffloadGlobalSetting
Get-NetTCPSetting
Get-NetIPInterface

Especially
Get-NetOffloadGlobalSetting
seems to be ideal for getting global rss and rsc

**Philip** · 07-19-18, 02:12 AM

Do the Powershell variants display their results in English?

Get-NetOffloadGlobalSetting
Get-NetAdapterRsc
Get-NetAdapterRss

The reason we were using netsh for some of the commands is backwards compatibility with Windows 7/8, there are different Powershell cmdlet implementation levels/bugs for each OS.

**Djfe** · 07-19-18, 03:03 AM

I think I found the "solution" urgh (for netsh anyways)

Microsoft saves all those strings in the corresponding ressource files, the dlls

in this case probably "netshell.dll"

How did I find this out?
First things I found out
https://u-tools.com/help/RemoteMgmtServer.asp
https://social.technet.microsoft.com...winserversetup
https://docs.microsoft.com/de-de/pre...e-get_grouping
https://docs.microsoft.com/de-de/pre...g-group-string
https://stackoverflow.com/questions/...ndirect-string
https://books.google.de/books?id=2u-...trings&f=false

All interesting but not about netsh, yet.
But it's likely that it will work this way with netsh as well.

The relevant links (to solving this problem) tl;dr
https://blogs.msdn.microsoft.com/old...223-00/?p=8243
https://blogs.msdn.microsoft.com/old...0-00/?p=40813/
https://docs.microsoft.com/de-de/win...ng-redirection
https://docs.microsoft.com/de-de/win...rected-strings

searching with regedit for "netshell.dll,-" also reveals what some of the localized strings are (String and id); but also some ids for icons
(the relevant strings don't seem to be duplicated in the registry, but you could use the code described in above scripts to find the ids you need)

maybe relevant(?)
http://www.jasinskionline.com/window...akelangid.html
https://xpdll.nirsoft.net/netshell_dll.html (maybe xp didn't include the relevant strings, yet? apart from that important table!)

YESSSS! SUCCESSS!!! Found the sneaky bastard.
https://www.win7dll.info/netiohlp_dll.html
Or the newer dll (Win10): http://windows10dll.nirsoft.net/netiohlp_dll.html
ID:4478

Code:

---------------------------------------------- Receive-Side Scaling State : %1!s! Chimney Offload State : %2!s! NetDMA State : %7!s! Direct Cache Acess (DCA) : %8!s! Receive Window Auto-Tuning Level : %3!s! Add-On Congestion Control Provider : %4!s! ECN Capability : %5!s! RFC 1323 Timestamps : %6!s!

If you need backwards compatibility to older OSes, then you should use the commands from above to get the localized string from netiohlp.dll (to be able to parse, in which line which result is printed)

I just saw, that you answered already, here's what it looks like:

seems like my network adapters don't support rsc (it's enabled globally in the OS though)