been working ok for me :)
OK. I'll try to remember to record the time/s when it happens and email you.
"The ultimate judge of your swing is the flight of the ball." - Ben Hogan
been working ok for me :)
live, love and laugh!!
Thanks cause I need to fix this problem
Twitter updates we will follow you back
http://twitter.com/Hardcoreweather
Now on Facebook We will like you back
http://www.facebook.com/pages/Hardco...0344466?v=wall
....
Twitter updates we will follow you back
http://twitter.com/Hardcoreweather
Now on Facebook We will like you back
http://www.facebook.com/pages/Hardco...0344466?v=wall
My thinking is there are tools which should be able to tell you your avg response time out to your portal then other things including all of us users seeing the elapsed portal to EU + system to portal elapsed time.
the handydan command line lookup is nslookup
what should be there is an nslookup for the IP Name should match an nslookup for the IP Address
at the moment I'm getting about 170 ms through 11 nodes but the biggest block of time are the last 3 nodes [ie at the "Host" end]
Kobayashi aka Frediii is from a different mental dimension than the rest of us.
You see, all of that makes perfect sense to him and he probably thinks it is rather elementary. He sees it in his head like Einstein probably saw theories.
Whereas the rest of us do, in fact, say "WTF???"
Ability is what you're capable of doing. Motivation determines what you do. Attitude determines how well you do it.Lou Holtz
This is a traceroute from my PC:
Tracing route to go4.dr-mann.com [66.197.156.69]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home [192.168.1.254]
2 22 ms 21 ms 20 ms 99-55-68-3.lightspeed.nworla.sbcglobal.net [99.5
5.68.3]
3 23 ms 21 ms 24 ms 99.179.204.10
4 22 ms 22 ms 23 ms 99.179.205.16
5 23 ms 21 ms 22 ms 99.179.205.10
6 22 ms 21 ms 21 ms 70.159.224.236
7 23 ms 22 ms 22 ms 12.81.24.110
8 22 ms 22 ms 23 ms 12.81.24.105
9 44 ms 44 ms 43 ms 74.175.192.50
10 46 ms 52 ms 46 ms cr1.nwrla.ip.att.net [12.123.153.18]
11 46 ms 45 ms 45 ms cr1.hs1tx.ip.att.net [12.122.1.141]
12 47 ms 45 ms 45 ms cr2.hs1tx.ip.att.net [12.122.5.190]
13 45 ms 47 ms 46 ms cr1.dlstx.ip.att.net [12.122.28.157]
14 45 ms 45 ms 45 ms ggr4.dlstx.ip.att.net [12.122.139.65]
15 47 ms 46 ms 46 ms 192.205.35.186
16 76 ms 75 ms 76 ms vl0019.gwy02.sctn01.hostnoc.net [63.218.31.42]
17 75 ms 75 ms 74 ms ec1-13.agg02.sctn01.hostnoc.net [64.191.108.46]
18 74 ms 74 ms 74 ms go4.dr-mann.com [66.197.156.69]
Trace complete.
I'm getting serious delays on the last three hops. How does that compare to yours?
Last edited by dkmac; 09-08-2010 at 07:00 PM.
"The ultimate judge of your swing is the flight of the ball." - Ben Hogan
go4.dr-mann.com
What in the wide world of sports is that
Twitter updates we will follow you back
http://twitter.com/Hardcoreweather
Now on Facebook We will like you back
http://www.facebook.com/pages/Hardco...0344466?v=wall
And the same time results from a ping:
C:\Users\XXXXXXX>ping hardcoreweather.com
Pinging hardcoreweather.com [66.197.156.69] with 32 bytes of data:
Reply from 66.197.156.69: bytes=32 time=75ms TTL=45
Reply from 66.197.156.69: bytes=32 time=75ms TTL=45
Reply from 66.197.156.69: bytes=32 time=74ms TTL=45
Reply from 66.197.156.69: bytes=32 time=74ms TTL=45
Ping statistics for 66.197.156.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 75ms, Average = 74ms
"The ultimate judge of your swing is the flight of the ball." - Ben Hogan
Nope I have never heard for them before
Twitter updates we will follow you back
http://twitter.com/Hardcoreweather
Now on Facebook We will like you back
http://www.facebook.com/pages/Hardco...0344466?v=wall
Pshhh...surprisingly, this IS elementary for me! ;)
Decipher this....
wi8j00=7=+8IOIEJjooloooeuu99390-mja;
ioa joijew c9i09ewiuissic i8302[a s09dlaa2
sieuaFJDIA;skdaoilovetebowakjaiIOEAOIie
YIOER9023jidsodajiiu90katisaperv323996
sis89eaFJDSIjsioreaskajsiaujfak;graruaou
What the hell did I just type???
http://www.facebook.com/home.php?#!/...00000499419036
"Personal foul - #69 - Offense - He was giving him the business" ~ Ron Cherry (referee ) Maryland vs. N. Carolina State ~
From the last line of the trace route to Hardcoreweather.com:
From the first line of the ping to Hardcoreweather.com:18 74 ms 74 ms 74 ms go4.dr-mann.com [66.197.156.69]
It's the same IP address: 66.197.156.69Pinging hardcoreweather.com [66.197.156.69] with 32 bytes of data:
So, the "go4.dr-mann.com" has to be the WWW network name for your internet hosting company.
But, at this point I'll defer to Kobayashi on WWW networking. I can give good advice on building/repairing/upgrading PC's, installing MS operating systems, installing most software, troubleshooting PC hardware problems, but networking (especially WWW networking) is not my strong suit.
"The ultimate judge of your swing is the flight of the ball." - Ben Hogan
Ohhhhhhhh I'm in so much stress on this thread - I had "multi-quotes" for all the questions I needed to answer.
......but they totaled 3 pages.....
Wind, Kat, Mooreweather - my 'day work' is the ERP Systems planning, installation and troubleshooting for "Fortune 50" companies that includes "Network Troubleshooting"
..which means geek
.....more precisely "Hyper Geek"
my post on the main 'response' topic not the "What should we get for an avatar for Katfive'
...was two universally available 'computer commands' for troubleshooting "Network Response Issues"
Dkmac, yes......your trace route and the one I pm'd to rolltide - they both had 3/4 of their total time at the "Hosting Company"
Roll -
Think of it in these terms: If you have 2 different websites, say www.hardcoreweather.com and separately www.rolltide.com where you want people to be able access them independently. example some get hardcoreweather, some get rolltide.com, and some get both
Those being the two primary IP Names you ask your "Network People" for a single static IP Address [the numbers thing] and the DNS entries to go with
Your 'did they get it?' check:
nslookup for www.hardcoreweather.com returns the IP address assigned [the xxx1.2.3.4 thing]
nslookup for the xxx1.2.3.4 coming back as go.kalamazoo.whatever means the network assignment was crossed up with addresses........
Dkmac and I both saw the same thing....
on the go.doc.man last time I looked that was a German website hosted over here
When you talk to your 'systems people'
I'm guessing they've got a misplaced DNS record for either you or go.mann
most likely is an un-flushed old DNS second is a server crossup on a secondary device IP
Okay, back to Wind, Katfive, and mooreweather ....its safe to turn your ears back on and let the kids and the dawgs out.
.......end-fred-geek rant!
Last edited by kobayashi; 09-08-2010 at 10:03 PM. Reason: 3 pages of multi-quotes
...ACCORDING TO http://www.alexa.com/siteinfo/dr-mann.com#Dr-mann.com's three-month global Alexa traffic rank is 15,729,561. The site has been online for more than thirteen years. The site is based in Germany.
http://www.facebook.com/home.php?#!/...00000499419036
"Personal foul - #69 - Offense - He was giving him the business" ~ Ron Cherry (referee ) Maryland vs. N. Carolina State ~
http://www.facebook.com/home.php?#!/...00000499419036
"Personal foul - #69 - Offense - He was giving him the business" ~ Ron Cherry (referee ) Maryland vs. N. Carolina State ~
LOL is right
the software I deal with is German,
the simple "Geek" stuff is a call from a UK accountant at 4:30 in the morning [what noon their time] that they can't get the system
The "Hyper Geek" is when it comes out "Der weinershnitzel ist gebroken!" [a long paragraph message that says that actually] and the UK user is waiting on a 15 million production run that we have to take to the Level III support in Germany as 'an escalation'. Ask Mandy.
Last edited by kobayashi; 09-08-2010 at 10:55 PM.
Bookmarks