VAX VMS TCP/IP bug? w/ Telnet

Is there some known bug with the TCP/IP implementation of telnet in the DEC version of TCP/IP ? I installed a fairly recent version of TCP/IP on my 10 year old VAX and when I telnet to it the VAX is driven to its knees and the hub goes wild. Doing a trace on the packets reveals zillions of 10:56:25.213012 unix.1714 > vax.telnet: P 36303:36314(11) ack 20085 win 17520 (DF) [tos 0x10] 10:56:25.216076 vax.telnet > unix.1714: P 20085:20091(6) ack 36314 win 4369 10:56:25.216856 unix.1714 > vax.telnet: P 36314:36325(11) ack 20091 win 17520 (DF) [tos 0x10] 10:56:25.219984 vax.telnet > unix.1714: P 20091:20097(6) ack 36325 win 4369 10:56:25.220726 unix.1714 > vax.telnet: P 36325:36336(11) ack 20097 win 17520 (DF) [tos 0x10] As you can see from the trace a couple of things are strange. Why are the windows screwed up? Why are the TOS bits set? Very confusing. --Chuck