jackdashack

We got the above settled as it is impossible to peruse usernames before registering it was purely happenstance, there's no way I could have known there was a "jackinthehouse". That was settled between us all and all is well. As CA3LE said, it's kinda kool that there are so many members that names are starting to resemble each. In a private message to CA3LE I sincerely offered to change my username so no one was offended but he said, Nyet ... so we both keep the names and it's up to you folks who read to keep us separate! haha!

Well according to my friend Art Vandelay, an architect and his recent flame Nurse Paloma ... (LOL)
 
The Westell is connected as shown in the diagram above by direct shielded Ethernet wire. I guess that's what you are asking? The only things I use now wireless are the tablet from time to time and the Roku in either room. I always put the Roku's in inactive when done. Both TV's have a Chromecast connected. I'm not sure but they do show up in the Verizon Console I mentioned above as "connected."  Of course I've removed the IP's from the images below.
 
MYPAVILION is the Windows 10 pc at the primary Veriozon modem/router
NP ~ are the Roku's

 
android-494~ is the Xoom Tablet
Wii and the android's disconnected are the neighbors that I have blocked access. Next question from you is why? We have not been able to find a way back into the Westell to security lock it. Even when we know the IP and log on with this XP which it is connected to is won't log in or we don't know the credentials. So I found I could use Access Control to stop them from logging on, which I believe was their devices searching not them logging on purposely. The LWP devices are brothers. Since he just left yesterday they have not gone away.
 
And my friend my neck and shoulders about had it and I don't think it's much longer for me tonight. But I will stay current if you are onto something. Many many thanks to you and CA3LE.  Jack ":-Dx


 
 

Pedantic? lol, you must have watched Seinfeld. One of George's dates used that word and he had no clue, but he repeated it just to feign knowledge. Me too ... I guess it means redundant or repetitive.
 
As stated above, "" Oh, the reason for the slave and the Ethernet not directly to the HP Compaq is the wireless is being used by a Roku about 10 feet away. ""

The Westell was just a left over from earlier days. Rather than throw it we used it to get the signal via the slave nearer the Roku in the FL Room. I call it the porch,   , it started out as a porch before remodeled years ago. Now I should say this, the use of the slave is nothing new. It's served this purpose for a year or more. OK, the slave deifned ...

There's no doubt this is the one. Here is a link. I am lazy at the moment and the router is pinned up ceiling high, at 65 I do not feel like climbing up to look. However most the week with brother putting in dedicated lines in the basement I felt like I'd performed this 40 times a day. I'm resting. But this is a pretty certain thing.

http://www.dslreports.com/faq/13772

Why thank you kind sir. I thought of it kinda crude! hahah! No CGI to enhance it!

I hope this is what you mean. Crude but gets the job done ... again I hope!!! Oh, the reason for the slave and the Ethernet not directly to the HP Compaq is the wireless is being used by a Roku about 10 feet away. No, they are all off during all tests. In fact I try to have everything using bandwidth off during tests.

I'll be gone about an hour. But I'm not quite sure what you mean yet. As I mentioned to CA3LE I have an slightly above the average pc user understanding. You mean turn one pc off,  I'd probably eliminate the XP on the slave router?  That would mean disconnect or pull he Ethernet line from the D-Link Verizon Router which is/was to the XP? As far as nodes or switches I'm clueless. And then when one is completely out of the picture what then? Run the tracert test or .....  Back in an hour. Thanks so much for your time ............
 

Actually, I mentioned I duplicated the images and confused you. The XP is the one reporting the ms in the 16ms area after the Timed Out's. The 10 box is the one with over 100ms after the Timed outs. I did remove the slave from the 10 box once and ran the same test without the slave being attached. Same results so my laymen mind said the slave has little to do with it. So knowing the 10 is reporting much higher ms after the timed outs what is it that concerns you. I really have no clue, it's a "no clue" question from me. lol

Sorry, I duplicated the images. 4 images, 2 of the same each. ":-\\

The one with the lower ms after the Timed out is the XP on the Slave and the one with the way high ms after the timed out is the Windows 10.  Are those "timed outs" the issues. Does that signify the problem. If so I can get the neighbors to run this tracert too and see if it's a commonality in this little cul de sac.


 
 

I only use the others as a reference. Most times actually Testmy and they are not that far apart. But the one I always watch and trust is Testmy and it's results. Now I don't know what to do. I guess I'm done. Verizon is all we have. No FIOS will ever be here and I will never go Comcast again. 3 other neighbors in my immediate vicinity have the same service. Would love for him to see if they've got these fluctuations. What simple test could I ask them to do to check for just fluctuation? Is satellite internet a bad proposition. It's more expensive and I have to consider that. But these fluctuations ... I can't say I really notice them. My service seems to be steady. ???

 
Room for improvement? Gee .. how. I just spent a whole week installing shielded DSL line, dedicated no other phones on it. I wonder what else I could do to "improve" the stats. I never doubted your tests or your manners of doing things. I was just wondering about the differences being shown. I'm still not sure I understand all the input. If brother was here he'd be able to break it down. Alas, he just left a few hours ago. We thought we'd really done something all the work we did this week. We cut new ends on the telephone lines on the block inside. Brightened the posts, shielded dedicated DSL line. Ethernet line from the primary to the slave. Gosh .. there's more? Not to bother, you've take enough time here with me. Thanks much!  jack  ":-Dx
 

Here is the XP on the slave ... the same test on the Windows 10 just next to it. I see a difference but not sure what it all means. You are right, it is not giving the same stats as the 4 other speed tests using flash. I have no idea what this might tell but I suppose to a trained eye some good. About 30ms average difference of the two.
 

This is the same test run on the Windows 10 connected by Ethernet to the primary D-Link router. An frankly Ca3le I should fess and tell you I'm not real savvy on all the technical issues you are speaking of. Somewhat but not all. 

 

This is a ping test from the kitchen XP on the slave router that is connected by direct shielded Ethernet. A short Ethernet cable to the XP. I'll go do the same on the windows 10 at the primary D-Link Router supplied by Verizon

Do you think something might be going bad on Verizon end. I remember this sort of thing happened once when a module or node or something was beginning to go bad downtown. At this point it's not happening enough to really notice it. Yes, this last comment of mine, test, was on the Windows 10. Sorry, I am doing business on the win10 and just ran a test. AND, I never ignore the results from testmy.net. But I don't know what it might be saying like you would .... ??

I just ran 2 tests here and got below 1mg download. Quickly did Megapath and got 2.7mg download  and 17ms latency. So not sure what's going on but no worries. It seems fine. BTW brother was just up from FL and we ran a dedicated DSL shielded line from box to primary Verizon router. We also ran a dedicated shielded Ethernet line to the slave router in the kitchen. And yes, this kitchen one is an XP but the one at the primary is a Windows 10. Just FYI

Yes, DC is my default and never Dallas. lol  And I think I follow your reasoning which I know is correct. So ... I'll read it several times until it sinks. Thanks again so very much! 

 
Understood, good info. However when I run these test it's usually back to back, in sequence, same issues involved. And I've done this running of sequence of tests often and get the low PING say on SpeedTest.net (Yeah, I know your stomach just turned .. )  But I run about 5 like that and TestMy always gives a 2x or more higher ping or whatever the "ms" stat means. Should I cut that in half? Still cut in half not nearly as good as the other multiple stats. When techs come from Verizon or Comcast they all say they don't worry so much about the speed ... it's the ping they look at. ??? No worry, Just curious ... no need to get hung up on this long.   Others have hard problems here in the I suspect in the forum. It's been a long long time since I've visited. Nice to see CA3LE you are still in there and doing well. You've helped me well in the past.  Jack  ":-Dx
 

Every test I do .. about 6 others consistently rate me in the 16-18ms ping. Why is my ping here always so high? 59 to 65. I know this is a non-flash with better results but Mytest has never been that much at odds. One is as high as 500+. I consistently get the low above across other speed test. Of course I am very interested in ping and then speed. Thanks so much! jack ":-Dx

Ookla has never shown that good for me. However I've come to rely on CA3LE's suggestions. I use from the command prompt ping and tracert to the "east.testmy.net" less the quotes. This is more reliable and with them I am always in the 15-17ms range.

Based on my past experience with Ookla's Speedtest, it often gives me ping times well below what I can get to any host. 
 
The following is an example where I ran a speed test:
 

I have yet to see a host (outside my network) give a 1ms ping time, let alone under 10ms. 

Is it possible to get the topology of your network, in other words:
 
Modem---> switch --> windows machine
 
Or Modem --> switch --> switch --> XP windows machine
                           |
                       windows 10 machine
 
It all good, we should have the above before at least myself, has a better understanding of the layout.
 
Also, when referring to the 'node', this could mean any number of network 'devices' in the path, a switch, a router, to keep it simple, it's a 'hop' that must be traveled to reach the destination. Which is what the tracrt shows, each 'hop' from 'node to node' is showing the 'latency' or speed / time to reach there and back divided by 2.

ok no problem, lets simplify this.
Take one machine out of the discussion momentary.
 
Is there one of th[e] two machines which can be connected to either or internal 'nodes' or switches as you are referring to?
If so lets use that one to test each 'switch or node'
 

The nodes that timed out are not always abnormal, it's simply the 'security' setup to not respond.
 
What is more concerning appears to be the XP box, where the 10 box has not this issue.
Yet you are getting the same test results from both machines, correct me?

May I suggest running a traceroute to east.testmy.net, and post the results here please.
 
tracert east.testmy.net