Refer to the above. Not sure if there's surefire answer ultimately but putting a firewall
in front of the server is not an option currently.
I tried the PowerShell command given in the url above using administrator but got syntax
error below, so what's the exact syntax:
PS C:\Windows\system32> Set-netTCPsetting -SettingName InternetCustom -Timestamps disabled
term 'Set-netTCPsetting' is not recognized as the name of a cmdlet, function, script file, or operable program. Che
the spelling of the name, or if a path was included, verify that the path is correct and try again.
et-netTCPsetting <<<< -SettingName InternetCustom -Timestamps disabled
+ CategoryInfo : ObjectNotFound: (Set-netTCPsetting:String)
+ FullyQualifiedErrorId : CommandNotFoundException
Can we set Windows Firewall rules instead & what's the exact Windows Firewall rules?
Saw somewhere the following so is it sufficient or there's more rules
needed? What's the equivalent rules in Windows Firewall, Juniper &
Fortigate & Cisco ACLs if any & if they help to get the scanner report
the Tcp timestamp is fixed?
"Create RHEL iptables firewall rules as additional enhancement:
iptables -A INPUT -p icmp --icmp-type timestamp-request -j DROP
iptables -A OUTPUT -p icmp --icmp-type timestamp-reply -j DROP
While not official Microsoft documentation, this Symantec page seems to indicate that Tcp1323Opts is deprecated in Windows Server 2008 and Windows Server 2008 R2. So I guess the question is - what has it been replaced by?
Is above true?
Anyone know of any other ways to fix this in Win 2008 (R2) & Win2012?
Anyone tried the following & it helps:
set the Tcp1323Opts=0 in CurrentControlSet001, 002, etc as well