cholla

mrproper;Even though the large download was slightly faster with the larger RWIN values the testmy test did best with these. DefaultReceiveWindow = 524288 TcpWindowSize = 513920 GlobalMaxTcpWindowSize= 513920 I think that would be a good place to leave those for now. I'm not sure where to go with the send window But I think smaller.I haave seen some use 65536 so lets try that & see how the upload does. DefaultSendWindow = 65536 There are 3 more settings that I would like you to try at different values.First I want you to use the Microsoft default settings. LargeBufferSize =8192 MediumBufferSize=1504 SmallBufferSize=128 Beleive it or not those are the default settings.

mrproper ;No I don't use any messenger program.Did you restart your PC after you changed the Cablenut settings again?You have to do this for them to go into your registry. These did the best on the test so use them for now. DefaultReceiveWindow = 524288 TcpWindowSize = 513920 GlobalMaxTcpWindowSize= 513920

mrproper ;Those may be too large it seems to have slowed down.So go back to the previous ones.I think they are close to best you are going to get.I could come up with a couple in between to fine tune it .Before you move these back down though try to time a large download with these & then the previous settings .Like you were doing in earlier posts.I think it was a 250MB download.I could go back & check but I think you get the idea. Just to make sure that you are not tweaking just to the test but also to a real function that you use.

It just shows us hard ass customers who know we're right can put someone out of business. Probably not a national business like Best Buy.Just don't let them tell you it's all between you & Westinghouse.They have more clout with Westinghouse than you do.& keep reminding them That THEY (Best Buy) bought the monitor from Westinghouse & you bought it from them.Even if it came with a warranty.And that makes it their responsibility to see that Westinghouse honors the warranty. It all comes down to any defect even 1 pixel makes it not the way it's supposed to be.I would also tell them that this is an indication something is wrong & probably more bad pixels will be showing up.So you want to get it fixed while it's still under warranty. One more thing once you get it warrantied make sure your warranty starts new again with the new monitor .Sometimes the try to slide on that.The new unit should have a full warrany of the same legnth as the first one.

mrproper ;Some faster so try these DefaultReceiveWindow = 786432 TcpWindowSize = 770880 GlobalMaxTcpWindowSize= 770480

just- ;Since I tweak I have thrown about every setting at my 56K.The recomended MTU of 576 for 56K is slower than when I use 1500.So I use 1500 for my MTU & adjust the MSS & Rwin to that as well.So for a 56 K if there is any slowdown I think it will be slight.& maybe faster because of less congestion.Also my ISP uses a MTU of 1500 for my dial-up connection.I think I still have a screen shot of the DUN box that shows this.I would do another one to post but this test is a little tricky to get it to work. IPv4IPv6ADSL2+FCCIEEE looks forboding all lumped together opps did I add one. I have been helping a new member named mrproper get his ADSL2+ speed up.It's on PPPoA Which could use an MTU of 9180 bytes max if the rest of the internet could handle it.

mrproper;First I wanted to further explain this DefaultReceiveWindow,TcpWindowSize &GlobalMaxTcpWindowSize are all RWIN.RWIN is just short for receive window.The difference is in Windows XP the DefaultReceiveWindow which is Windows XP's first chioce to use is based on AFD parameters.TcpWindowSize & GlobalMaxTcpWindowSize are based on TCPIP parameters.These are used if your connection is using TCPIP & it probably does for some of the Internet you connect to. The server time when you did the tests before the last settingwas 6:30 PM the server test time.The last ones at 6:00 AM server time.I really don't know why they were slower with the previous settings.I think you still need to try a couple of larger settings to see if this improves your speed.The send wimdow has about leveled so we will leave it for now & actually make it smaller after the best RWIN is determined. DefaultReceiveWindow = 524288 TcpWindowSize = 513920 GlobalMaxTcpWindowSize= 513920

netmasta;First thanks for replying I had wanted this to generate more discussion from the testmy think tank.I did read the second link & I had already read the Wikipedia link. So here is why Wikipedia used a 14.Kb modem as an example.14.Kb is the minimum the FCC requires a phone company to have over a POTS voice line.This is the line dial-up of all speeds uses. Next I doubt there are many 14K modems being used today & most are 56K which is limited to 53 K. So I'm not sure how much a 1500 byte packet slows a 56K modem if it falls in line with the 14k one then 1/3 of a second.So do you want your 1500 byte packet smaller so my 56K modem will be faster?I'm saying a 1536 packet (some more binary based) would be about the same to the slower modems. On dial-up you get used to slow anyway.I should know. But really the next step would probably produce the best results for broadband with minimum increase in delay for dial-up modems. That would be a MTU of 2048. This falls in line with binary & the AFD parameters XP uses. Here's my theory on where this would actually help slower connections.Since this should have less retransmits on packets for broadband & the broadband would be faster less congestion would result making the dial-up work better. I think the real resistence to this is the higher lever hardware that can't handle faster than 1500 byte packets.

I was just wanting to know if anyone knew why 1500 bytes was decided on to be the MTU or general size of a packet or datagram.At least for most broadband.To me 1024 bytes seems a more logical size given it fits KB.MB ,etc. Heres the chart & an explanation for why these are 1024. 1 bit = a single digit, either 1 or 0 8 bits = 1 byte, a combination of 1's and 0's 1024 Bytes = 1 KB (kilobyte) 1024 Kilobytes = 1 MB (megabyte) 1024 Megabytes = 1 GB (gigabyte) Now to explain how they get that magic number 1024. Because the binary code system has only 2 numbers, powers of 2 plays an important role. Numbers always have to be 2 to the power of ? They take 2 to the 10th power to get the number 1024. 2 is the 1st power 2 X 2 = 4 (the 2nd power) 2 X 4 = 8 (the 3rd power) 2 X 8 = 16 (the 4th power) 2 X 16 = 32 (the 5th power) 2 X 32 = 64 (the 6th power) 2 X 64 = 128 (the 7th power) 2 X 128 = 256 (the 8th power) 2 X 256 = 512 (the 9th power) 2 X 512 = 1024 (the 10th power) And that's how you get 1 KB. So 1500 -1024 = 476 I could understand if they had used 1536 becaus that would have a packet of 1 & a half KB. So any explanations?

tstillery ; We will be with you in spirit.I really hope you don't have to go to Iraq.I would like to see the war over but that's probably not going to happen.I guess it's hard to duck in a tank so shoot first & ask questions later.Or kill them all & let God sort them out.

WatchMeNow ;Your ISP blocks ping.so does mine.One result you can get is the test below. This will show a MTU of larger than 1500 will not work without fragmenting. C:WINDOWS>ping -f -l 1473 testmy.net Pinging testmy.net [67.18.179.85] with 1473 bytes of data Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Packet needs to be fragmented but DF set. Ping statistics for 67.18.179.85: Packets: Sent = 4, Received = 0, Lost = 4 (100% Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms If it gives you the timed out message with this below then your MTU is 1500 ping -f -l 1472 testmy.net If you have most DSL the amount to ping with would be 1464 this would show the MTU was 1492. BTW the l is a small L.

Sorry we got off topic on this but the general opinion is what MUff!N said in a few words.

I built my waterbed as an off the floor one in 1979.Back when most were on a short pedestal at best & a lot were on the floor with a frame.I designed my own support frame.It is still solid & in use.So if you needed some massage after a hard day the vibrator really relaxed the muscles.I never saw anyone this wouldn't put to sleep regardless of the fact it was noisy. The cheap POS only lasted about a year.The one I replaced it with is much quieter it cane out of a vibrating recliner & is 2 units that look like small motors.These have worked for many years now. The first one was for lack of a better description a buzz solenoid.This one did have a timer & variable speed. On the recliner one if I had gotten another rheostat I could have controlled the speed on each vibrator separately.

mrproper;I don't mind explaining my method.First there is no site that has a real how to on doing this.So I think this is the best method based on what I know. These 3 are RWIN settings: DefaultReceiveWindow TcpWindowSize GlobalMaxTcpWindowSize These affect the download you are able to recieve.The first one is calculated with AFD parameters & the next 2 are calculated based on MSS which is MTU minus 40. The minus 40 comes from bytes in the datagram header that basically tell the Internet how to handle the data contained in the datagram.The amount left is the data you recieve which is the MSS.In your case 1460 bytes. The reason I change these every time is I believe they should be as close as the calculations will let them be to the same size.Otherwise if for whatever reason your computer OS routed the datagrams to a lot smaller RWIN because 2 of them were left a lot smaller then it would slow the download. This setting is actually the send window it effects upload. DefaultSendWindow When it hits is best speed we will quite changing it with the others.We may even try it smaller after the RWIN values reach their fastest. I hope that explains it well enough.

tommie & me have used pretty much the same technic.& agree either you need to be a hard ass or take someone with you that will. Let me tell you of a couple of stories of making Walmart honor a warranty.Theey are not as good as when Sam Walton was alive,I have returned two different water faucets that had life time warranties.These were in the Popular mechanics line that Walmart more or less owned at one time.These warranties say "Return to the Walmart store."But at Walmart the first thing they tell you is faucets have a factory warranty & you have to return them to the factory.They didn't much like it when I showed them the fine print that said return to the store. I had to get an upper level manager to warranty it.The middle one even accused me of printing a fake Walmart receipt.because it was 8 years old & he hadn't seen one like that.Needless to say it was the real original.I got the faucet warranteed. The second faucet was for my mother.Same type warranty.They wanted me to pay the difference between the receipt price & the new faucet.I said the warranty says replacement.They would not do it& it was at night so no upper management was in the store. I did what tommie said & told them this was not acceptable because I needed it that night.So I went to Builders Square & bought a new comparable one.The next day I went to Walmart with the old faucet & the receipt for the new one I bought at Builders Square.When I left Walmart I had the money I spent on the new one from Walmart. One of the few things I wasn't sucessful on was a waterbed with a defective vibrator unit.The couldn't get me a replacement in less than a month.I said I haven't even unpacked most of it yet .I was just checking out the electrical stuff before I got started.The store manager had already dialed the police before I left. That was back in my younger days & I did threaten to kick his ass if he didn't refund my money. I carried it as far as picketing the store for two weekends after but no refund that time. btw the store was out of business by the end of the year so I guess I wasn't the only dissatisfied customer.

mrproper;That's fine.I would be tired too.It's only 9:00 PM in Texas right now. It looks like the Download is steadily coming up & more consistent.The upload has about leveled.I'm going to put the next settings in .You don't have to use them until your ready Get some sleep. DefaultReceiveWindow = 393216 DefaultSendWindow = 393216 TcpWindowSize = 385440 GlobalMaxTcpWindowSize= 385440

Heres you one.The lights are ok but the horns are a little strange.

mrproper;I'm just going up in size with the RWIN using the correct calculations for them.VanBuren knows a lot more about some of this than me but it's hard to get him to devote the time.So I'm having you take it up till we see a speed drop.Then we will go back down a little.After this I need to find more about adjusting the 3 buffer sizes in CableNut to help with those. I think we should begin to see a slow down in the upload first.Since there is so much difference in your upload & download. So try these. DefaultReceiveWindow = 262144 DefaultSendWindow = 262144 TcpWindowSize = 256960 GlobalMaxTcpWindowSize= 256960

mrproper;I read the messages in the screen shot.The TCPIP Analyzer makes the wrong recomendation for RWIN in Windows XP.Because the base all of them on MSS. They would be correct about the scaling if I wasn't going to have you go larger now. You can see the speed took a step uo from the first settings.I think this is what you will continue to see until it gets too large.So lets go another step up. DefaultReceiveWindow = 131072 DefaultSendWindow = 131072 TcpWindowSize = 128480 GlobalMaxTcpWindowSize= 128480

amc11890 ;We must have been working on figuring out what the car was at about the same time.The starnge lights kind of threw me.

I believe it is a 1985 or 1986 Ford RS200.The headlights or whatever they are is some strange modification to this particular car.

mrproper ;I wanted to see how you did with all the RWIN settings small.I think we need to step it to quite a bit larger now.You can try a test a a mirror ot one of the sites you do a large download from .I suspect those will be slow also. But I needed to start some where because too large an RWIN is bad also. So now try these.65536 DefaultReceiveWindow = 65536 DefaultSendWindow = 65536 TcpWindowSize = 64240 GlobalMaxTcpWindowSize= 64240 See if the speed goes up also try an upload test.

Westinghouse only says 6 or 8 is what the call a high amount.What do you want to bet if a store like Best Buy had a westinghouse on displat with 4 dead pixels .Westinghouse would consider that a high amount. If the President of Westinghouse wanted a one of this model to use & it devoloped one bad pixel .Then he said it has a bad pixel I want another unit .Do you think he would be told 1 pixel was not enough for him to get another unit?I bet not. Of course there is always small claims court as a last resort. But before that try to talk to higher & higher supervisor at Westinghouse.This takes High salaried employees time.& sooner or later they get the idea that you are costing them more than replacing your defective unit will.

mrproper;Those settings are a starting point.I want you to try these in CableNut.I think you have a couple the way you want them but I'm putting them in to make sure.Give these a try .remember to restart after "save to the registry "in Cablenut. DefaultReceiveWindow = 16384 DefaultSendWindow = 16384 TcpWindowSize = 17520 GlobalMaxTcpWindowSize= 17520 TcpRecvSegmentSize = 1460 TcpSendSegmentSize = 1460 DefaultTOSValue = 0 DefaultTTL = 128 EnablePMTUDiscovery = 0 Then check with the TCPIP Analyzer to mak sure its reading the new RWIN & That it detactes the MTU as 1500. Then come to testmy .Clear your cache & test.

dlewis23 ;Here are acouple of articles I found on ADSL using MTU 1500.I didn't find the one I had gotten the information from earlier.I will look some for more if you want me too, Use your edit/find for MTU http://www.usr.com/support/9108/9108-ug/wui_internet.htm#option1 Authentication method is default to Automatic. It is recommended that you leave the Authentication method in Automatic, however, you may select PAP or CHAP if necessary. The default value for MTU (Maximum Transmission Unit) is 1500 for PPPoA and 1492 for PPPoE. Do not change these values unless your ISP asks you to. http://forums.whirlpool.net.au/index.cfm?a=wiki&tag=ADSL_Theory_PPP Point to Point Protocol (PPP) is, as it's name suggests, a protocol for establishing a link between two points. In the case of ADSL it's between your modem or PC to our BRAS (Broadband Remote Access Server - the PPP server). PPP isn't technically required for an ADSL connection, the internet could run straight over the ADSL's ATM network. PPP is used on most of ADSL connection because of the legacy of dialup; an authorisation/accounting system is needed and PPP is the defacto standard. PPP can be run in two different ways and the preferred style is dependant on your ISPs set up. PPPoE is best if they run an ethernet link between the DSLAM and BRAS, PPPoA is better if they are running an ATM network between the DSLAM and BRAS. Why the difference? Maximum Transmissable Unit (MTU) is the largest individual data packet that can be sent over a network, in the case of Ethernet it's 1500, in the case of ATM it's not limited. What this means is that as the packet passes from ADSL to Ethernet is can exceed Ethernet's MTU and be dropped. By forcing PPPoE your modem forces the packets to stay with in Ethernet's 1500 MTU limit. That said PPPoA is marginally more effiecient with overheads and processing by both ends. ADSL - Asyncronous Digital Subscriber Line - what this is all about ATM - Asyncronous Transfer Mode - a network protocol used by ADSL PPPOA - Point-to-Point Protocol Over ATM PPPOE - Point-to-Point Protocol Over Ethernet