cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
7459
Views
0
Helpful
6
Replies

Invalid Window Scale option for session

lcaruso
Level 6
Level 6

Can anyone tell if it's a misconfigured host or router causing these log messages ?

*Nov  9 01:05:22.807: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.25.16:28230 (Initiator scale 0 Responder scale 7)
*Nov  9 01:07:05.811: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.24.40:28230 (Initiator scale 0 Responder scale 7)
*Nov  9 01:08:15.715: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 69.16.187.84:28230 (Initiator scale 0 Responder scale 7)
*Nov  9 01:29:39.731: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.24.41:28230 (Initiator scale 0 Responder scale 7)
*Nov  9 01:40:30.079: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.9.218:28230 (Initiator scale 0 Responder scale 7)
*Nov  9 01:50:16.651: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 69.16.187.64:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 01:17:57.669: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.24.16:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 01:25:18.253: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 69.16.187.73:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 01:50:29.381: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.24.16:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 02:05:13.185: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.25.22:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 02:50:53.853: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.27.147:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 02:51:27.641: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:443 to 209.197.27.146:28230 (Initiator scale 0 Responder scale 7)
*Nov 12 02:55:06.869: %FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE: Dropping packet - Invalid Window Scale option for session 172.29.6.99:1132 to 69.16.187.108:28230 (Initiator scale 0 Responder scale 7)

3 Accepted Solutions

Accepted Solutions

heres a suggestion.

Window scaling was added to allow for rapid transmission of data on long fat networks (LFN). These are typically connections with very high bandwidth, but also high latency. Networks with satellite connections are one example of an LFN, since satellite links always have high propagation delays but typically have high bandwidth. To enable window scaling to support LFNs, the TCP window size must be more than 65,535. This error message can be resolved by increasing the TCP window size to be more than 65,535.

View solution in original post

6 Replies 6

vmiller
Level 7
Level 7

Thanks for the link. Unfortunately, even though I have CCO access, I don't have partner acess.

heres a suggestion.

Window scaling was added to allow for rapid transmission of data on long fat networks (LFN). These are typically connections with very high bandwidth, but also high latency. Networks with satellite connections are one example of an LFN, since satellite links always have high propagation delays but typically have high bandwidth. To enable window scaling to support LFNs, the TCP window size must be more than 65,535. This error message can be resolved by increasing the TCP window size to be more than 65,535.

thanks for that (and reminding me I should have partner access )

Hi Icaruso,

Since you have a CCO , please check for this BugID=CSCsc37281 .

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsc37281

Manish

kind of you to post that--thank you. I can share that description with my client.