Network issues to a specific site like Domebo, try a Tracert in command prompt. (Windows users)

[What Exit?]

tracert is the Trace Route command. It determines the routing from your computer to the server you are trying to hit.
--------------------------------------------------------------------------------------------------------------------------
In Windows XP go to Start- Run - Type CMD and hit enter.
In Windows Vista got to Start - Type CMD in the start here entry field.

In either hold down the Windows Key and hit R to get a Run dialog box then type CMD and hit enter.

--------------------------------------------------------------------------------------------------------------------------
In the Command prompt (looks like DOS for the older readers) type Tracert domebo.net and hit enter.
It will trace the route.
In the upper left corner, click on the c icon and choose Edit - Select All then click on the c icon and choose Edit - Copy.
Paste it into a PM or Email and send it off to the appropriate person, here it is probably McNutty and/or I.

Here is the example:
--------------------------------------------------------------------------------------------------------------------------
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C>tracert domebo.net

Tracing route to domebo.net [67.207.138.196]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms YourRouter [555.555.1.1]
2 29 ms 26 ms 25 ms IreplacedThisPart.verizon-gni.net [555.555.208.1]
3 28 ms 26 ms 25 ms so-0-1-1-0.NWRK-CORE-RTR1.verizon-gni.net [555.555.13.49]
4 30 ms 30 ms 30 ms so-7-2-0-0.NWRK-BB-RTR1.verizon-gni.net [555.555.20.160]
5 34 ms 35 ms 35 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [555.555.17.6]
6 31 ms 34 ms 34 ms so-6-0-0-0.NY111-PEER-RTR1-re1.verizon-gni.net [130.81.17.129]
7 34 ms 30 ms 31 ms po2-0.core01.jfk05.atlas.cogentco.com [154.54.11.45]
8 32 ms 31 ms 33 ms te4-1.ccr02.jfk05.atlas.cogentco.com [154.54.24.33]
9 31 ms 34 ms 34 ms te8-3.ccr04.jfk02.atlas.cogentco.com [154.54.26.65]
10 41 ms 38 ms 40 ms te8-8.ccr02.bos01.atlas.cogentco.com [154.54.27.173]
11 114 ms 59 ms 61 ms te8-8.ccr02.ord01.atlas.cogentco.com [154.54.24.58]
12 67 ms 69 ms 70 ms te4-2.ccr01.stl03.atlas.cogentco.com [154.54.27.30]
13 69 ms 69 ms 69 ms vl3802.na31.b016110-1.stl03.atlas.cogentco.com [66.28.5.246]
14 70 ms 70 ms 69 ms 38.104.162.58
15 71 ms 70 ms 71 ms 209-20-79-17.slicehost.net [209.20.79.17]
16 71 ms 69 ms 70 ms domebo.net [67.207.138.196]

Trace complete.

C>
--------------------------------------------------------------------------------------------------------------------------

[featherlou]

Are you going to do a Mac version too, or we just on our own?

[What Exit?]

Are you going to do a Mac version too, or we just on our own?

I can't but maybe a tech oriented Mac Poster could. I don't know Mac at all.

[featherlou]

Hmm. I used a ping a little while ago while my ISP was down - maybe I'll see if I can figure that out again.

[McNutty]

It's the same on the mac, except you use the "Terminal" program (I don't really know how to get that on a mac but I know it's a standard utility) and the command you type is the good-and-proper "traceroute" instead of "tracert". It's also "traceroute" on linux and most other unixy things.

[featherlou]

I went to Finder, typed in "Terminal," double-clicked on the Terminal application, then typed in traceroute at the C prompt. The returned data looks like this:
Version 1.4a12+Darwin
Usage: traceroute [-dFINnrSvx] [-g gateway] [-i iface] [-f first_ttl]
[-m max_ttl] [-p port] [-P proto] [-q nqueries] [-s src_addr]
[-t tos] [-w waittime] [-z pausemsecs] host [packetlen]

[Exy]

Okay so look if I ran traceroute and it ran unsuccessfully (i.e. as far as I can tell it did not find a route) what the porch am I supposed to do.

[What Exit?]

Okay so look if I ran traceroute and it ran unsuccessfully (i.e. as far as I can tell it did not find a route) what the porch am I supposed to do.

How far did it run?
Did you see any times at all?
Were you having connections issues with Domebo.net?
Did you try another site?

One thing you can do on a tracert is set the flags:

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

C>tracert domebo.net -d -w 2000

Tracing route to domebo.net [67.207.138.196]
over a maximum of 30 hops:
deleted 1st 7 hops
8 14 ms 14 ms 14 ms 154.54.11.45
9 15 ms 14 ms 14 ms 154.54.24.33
10 14 ms 15 ms 14 ms 130.117.0.53
11 18 ms 18 ms 19 ms 154.54.5.242
12 41 ms 42 ms 41 ms 154.54.6.22
13 47 ms 50 ms 48 ms 154.54.27.30
14 51 ms 50 ms 52 ms 66.28.5.58
15 50 ms 49 ms 50 ms 38.104.162.58
16 49 ms 49 ms 50 ms 209.20.79.17
17 50 ms 50 ms 49 ms 67.207.138.196

Trace complete.

[McNutty]

Note that if you post your traceroutes here you are giving up some information about your whereabouts. Probably best to PM them to What Exit and me.

[featherlou]

Well, we're moving next month anyway.

[McNutty]

Oh, featherlou, I just noticed your post. If you got that output from traceroute, it's because you didn't provide a hostname. You want to type "traceroute domebo.net". Sorry, I wasn't clear when I said the command was "traceroute." I just meant the name of the command, not the whole command line including args.

[featherlou]

Man, it's service like that that makes me want to ask for a refund. Oh, wait....

[Glazer]

Well ya gets what ya pays fer.

[Exy]

Okay, so, continuously, since Friday, I cannot connect from home unless I do it via Tor. It consistently fails between slicehost.net and domebo. Work it's (sort of mostly) been working.

15 71 ms 70 ms 71 ms 209-20-79-17.slicehost.net [209.20.79.17]
16 71 ms 69 ms 70 ms domebo.net [67.207.138.196]

[Winston Smith]

have you tried rebooting?

[Exy]

have you tried rebooting?

Is this a joke about standard tech-support-guy advice? Yes, I've definitely rebooted in that time, and why would that help anyway?

[Winston Smith]

have you tried rebooting?

Is this a joke about standard tech-support-guy advice? Yes, I've definitely rebooted in that time, and why would that help anyway?

Yeah, I was joking. You might try flushing all your cookies, temp files and what-have-you from IE (or whatever browser you use).

[Exy]

Yeah, I was joking. You might try flushing all your cookies, temp files and what-have-you from IE (or whatever browser you use).

That stuff would have no effect on the outcome of a traceroute.

[Winston Smith]

Suit youself, Exy. Good luck.

[Myrnalene]

It's not just Exy. Fenris, prr and binks were also having severe connection issues that I know of. So I don't think Exy flushing his cookies is gonna help all that much.

FWIW, my connection issues had seemed to have cleared up but I was booted off several times today at work. I can do a traceroute from there tomorrow.

[McNutty]

Okay, so, continuously, since Friday, I cannot connect from home unless I do it via Tor. It consistently fails between slicehost.net and domebo. Work it's (sort of mostly) been working.

15 71 ms 70 ms 71 ms 209-20-79-17.slicehost.net [209.20.79.17]
16 71 ms 69 ms 70 ms domebo.net [67.207.138.196]

Can you tell me more about the traceroute snippet above? You say it fails between slicehost.net and domebo, but that snippet shows success all the way through.

[Exy]

Huh, my problem with connecting from home seems to have resolved itself just now. I actually tried connecting via ssh tunneling from work before posting this afternoon just to confirm it was still happening, and I even tried rebooting my home computer from there and connecting again since I wasn't positive I had rebooted since I started having problems. It still wasn't working as of an hour and a half ago, but it is now, without using Tor.

Can you tell me more about the traceroute snippet above? You say it fails between slicehost.net and domebo, but that snippet shows success all the way through.

Yeah, sorry, I wasn't clear. That bit I copied and pasted from your traceroute above for illustration purposes since my SSH client was giving me troubles copying and pasting. It was that step that was failing for me, it connected to 209.20.79.17 and then tried that next hop to 67.207.138.196 about 18 times with no success. But obviously it's working for me now, so I'll just cross my fingers.

[McNutty]

It's not just Exy. Fenris, prr and binks were also having severe connection issues that I know of. So I don't think Exy flushing his cookies is gonna help all that much.

I haven't heard from binks*, but prr is not having connectivity issues -- he's having issues with staying logged in, which points to a problem with the board and/or his browser. Fenris' problem could be connectivity related, but he said logging out solved it, which makes me go 'hmm' (because being able to click the "logout" link and log back in implies that connectivity is fine).

*that I remember. Binks, if you asked me something about this in chat and I spaced, please send me a PM.

[McNutty]

Huh, my problem with connecting from home seems to have resolved itself just now.

Damn, I'm good. You see, the way it works is: if it breaks, it was network goblins (as opposed to, say, my server). When it starts working again, it's because I'm awesome. Glad we had this talk.

[terrifel]

I have been losing my connection tonight, several times. This is the first time I have had such a problem with Domebo.net. I mention this merely as a data point.

[pepperlandgirl]

Well, I just lost my connection to the board for several minutes (and I know at least one other poster had issues at the same time). It is not my work connection, and no other website I had open in the browser was affected. It just got hung up for several seconds in chat, and when I hit reload, it told me that the connection had timed out and domebo.net couldn't be reached.

[featherlou]

Yup, that was my experience, too, at around 9:30 AM (mountain time).

[featherlou]

Crapped out again at 10:30 AM.

[McNutty]

Well, Slicehost responded to me and said they know of no connectivity issues. They also very helpfully looked at a traceroute I sent them and tried running it in the other direction, concluding that since they couldn't hit the last hop, there was obviously a firewall involved at the user end, so the user should check their firewall. If you understood all that, you know it's a total cop-out.

Unfortunately, not having seen the problem myself, I don't have anything concrete to complain at them about. I'm not sure what the next step is.

[featherlou]

I don't recall installing any firewalls in my home computer.

[McNutty]

I don't recall installing any firewalls in my home computer.

Well, first of all, the suggestion is bogus, so pay it no mind. But you wouldn't have to have a firewall installed on your computer to get the type of behavior he's describing... many routers act as a firewall, for example.

[McNutty]

Could everyone that's having problems give me some kind of idea of how often the problems are happening? I just got yelled at in chat by Excalibur for not fixing the problem which he's apparently having all day every day, when I thought his problem had cleared up. So far everyone else I've talked to has indicated that this is not an ongoing problem, but rather a few isolated incidents where they couldn't connect. If this is actually a bigger problem, I need to know about it.

[Myglaren]

Not altogether sure why we are doing this. I never have any problems with this site an any of the machines here.

Using a BT Home Hub (Thomson-Alcatel) on a BT line.

steve@Innamoramento:~$ traceroute domebo.net
traceroute to domebo.net (67.207.138.196), 30 hops max, 60 byte packets
1 api.home (192.168.1.254) 95.652 ms 95.033 ms 94.420 ms
2 esr6.edinburgh5.broadband.bt.net (217.32.78.145) 40.413 ms 42.390 ms 44.298 ms
3 217.32.78.30 (217.32.78.30) 46.345 ms 48.543 ms 50.477 ms
4 217.47.187.10 (217.47.187.10) 52.476 ms 54.416 ms 56.339 ms
5 217.41.218.21 (217.41.218.21) 58.414 ms 60.290 ms 62.132 ms
6 217.41.174.65 (217.41.174.65) 64.118 ms 35.812 ms 35.907 ms
7 217.41.218.146 (217.41.218.146) 36.093 ms 38.070 ms 36.482 ms
8 217.41.174.50 (217.41.174.50) 36.376 ms 36.143 ms 35.960 ms
9 217.32.97.49 (217.32.97.49) 36.782 ms 40.115 ms 38.869 ms
10 core2-pos5-0.edinburgh.ukcore.bt.net (194.72.17.185) 37.698 ms 36.448 ms 37.840 ms
11 core2-pos8-1.manchester.ukcore.bt.net (62.6.201.25) 102.046 ms 100.632 ms 97.212 ms
12 core2-pos0-9-5-0.ealing.ukcore.bt.net (62.172.103.70) 53.337 ms 53.315 ms 53.487 ms
13 transit2-gig9-0-0.ealing.ukcore.bt.net (194.72.17.82) 53.707 ms 56.751 ms 58.100 ms
14 t2c2-ge8-0-0.uk-eal.eu.bt.net (166.49.168.49) 59.503 ms 53.611 ms 56.895 ms
15 195.50.91.169 (195.50.91.169) 58.921 ms 61.043 ms 64.737 ms
16 ae-32-54.ebr2.London2.Level3.net (4.68.117.126) 65.593 ms ae-32-52.ebr2.London2.Level3.net (4.68.117.62) 84.618 ms 85.262 ms
17 ae-41-41.ebr1.London1.Level3.net (4.69.141.189) 75.365 ms ae-42-42.ebr1.London1.Level3.net (4.69.141.193) 72.574 ms ae-43-43.ebr1.London1.Level3.net (4.69.141.197) 74.661 ms
18 ae-100-100.ebr2.London1.Level3.net (4.69.141.166) 76.578 ms 78.652 ms 80.480 ms
19 ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66) 152.474 ms ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) 154.437 ms 156.394 ms
20 ae-4-4.ebr1.NewYork2.Level3.net (4.69.141.18) 121.749 ms 121.137 ms 132.733 ms
21 ae-1-100.ebr2.NewYork2.Level3.net (4.69.135.254) 134.842 ms 138.799 ms 139.488 ms
22 ae-2-2.ebr1.Chicago1.Level3.net (4.69.132.65) 168.490 ms 169.148 ms 170.630 ms
23 ae-1-100.ebr2.Chicago1.Level3.net (4.69.132.42) 171.286 ms 171.877 ms 172.567 ms
24 ae-4-4.car2.StLouis1.Level3.net (4.69.132.189) 178.447 ms 180.432 ms 182.346 ms
25 ae-11-11.car1.StLouis1.Level3.net (4.69.132.185) 184.251 ms 186.429 ms 188.317 ms
26 RACKSPACE-M.car1.StLouis1.Level3.net (4.53.160.190) 163.769 ms 162.062 ms 170.543 ms
27 209-20-79-3.slicehost.net (209.20.79.3) 164.620 ms 165.321 ms 166.569 ms
28 domebo.net (67.207.138.196) 180.651 ms 182.577 ms 184.439 ms
steve@Innamoramento:~$

were the results a couple of minutes ago.

ETA: had to install traceroute, haven't used it in yonks

[Myrnalene]

Could everyone that's having problems give me some kind of idea of how often the problems are happening? I just got yelled at in chat by Excalibur for not fixing the problem which he's apparently having all day every day, when I thought his problem had cleared up. So far everyone else I've talked to has indicated that this is not an ongoing problem, but rather a few isolated incidents where they couldn't connect. If this is actually a bigger problem, I need to know about it.

I am now, at work and at home, spending about half my domebo time disconnected. Every three, four, five minutes it freezes, then takes about five minutes to reconnect. It is very, very, very frustrating. Excalibur and I are getting kicked off at the same times.

It did clear up for a few days but started again in earnest about mid-week.

[featherlou]

I don't recall installing any firewalls in my home computer.

Well, first of all, the suggestion is bogus, so pay it no mind. But you wouldn't have to have a firewall installed on your computer to get the type of behavior he's describing... many routers act as a firewall, for example.

I knew I should have put a smiley face after that.

[CRSP]

Could everyone that's having problems give me some kind of idea of how often the problems are happening? I just got yelled at in chat by Excalibur for not fixing the problem which he's apparently having all day every day, when I thought his problem had cleared up. So far everyone else I've talked to has indicated that this is not an ongoing problem, but rather a few isolated incidents where they couldn't connect. If this is actually a bigger problem, I need to know about it.

I am now, at work and at home, spending about half my domebo time disconnected. Every three, four, five minutes it freezes, then takes about five minutes to reconnect. It is very, very, very frustrating. Excalibur and I are getting kicked off at the same times.

It did clear up for a few days but started again in earnest about mid-week.

When you say the board freezes, what exactly do you mean? A 404/500 error, or the links on the board just don't seem to respond? Does this always happen from a specific page (i.e. the forum index), or is it happening all over the board?

Also, everybody who has the problem seems to be in North America. Is everybody on the same ISP?

[Myrnalene]

Could everyone that's having problems give me some kind of idea of how often the problems are happening? I just got yelled at in chat by Excalibur for not fixing the problem which he's apparently having all day every day, when I thought his problem had cleared up. So far everyone else I've talked to has indicated that this is not an ongoing problem, but rather a few isolated incidents where they couldn't connect. If this is actually a bigger problem, I need to know about it.

I am now, at work and at home, spending about half my domebo time disconnected. Every three, four, five minutes it freezes, then takes about five minutes to reconnect. It is very, very, very frustrating. Excalibur and I are getting kicked off at the same times.

It did clear up for a few days but started again in earnest about mid-week.

When you say the board freezes, what exactly do you mean? A 404/500 error, or the links on the board just don't seem to respond? Does this always happen from a specific page (i.e. the forum index), or is it happening all over the board?

Also, everybody who has the problem seems to be in North America. Is everybody on the same ISP?

I personally have not had this issue since McNutty rebooted his server Saturday night, but I do not know about anyone else. Also, it has happened before where the issue has gone away for a few days and then reoccurred so it's probably to early to say it is fixed.

Anyway, what happens is this - usually I will have the index page or the chat window open and the window will not refresh. The little circle at the bottom of the window will go around and around and around with no new messages appearing. If I leave the page up for say, 7 or 8 or 9 minutes it will eventually resolve itself and unfreeze. If I try to reload the page I will get an error that says "the connection to the server was reset while the page was loading" or something to that effect. It also does not just happen on the index page or chat, sometimes when I am trying to go from page to page or post a message I will get the same error.

[Exy]

Yeah, I think rebooting it did something. It wasn't a connectivity issue; traceroutes showed no problems. It just wouldn't do anything -- chat froze up, and if I closed that and tried clicking on links, they would just eventually time out.

[featherlou]

What Myrna describes is what happened to me occasionally, too, but I'm pretty sure we have different ISPs and routes.

[McNutty]

What Myrna describes is what happened to me occasionally, too, but I'm pretty sure we have different ISPs and routes.

featherlou, when I spoke to you via PM, you said that the problem had only happened once that morning, and once about a week prior. Are you saying that you later experienced this happening every few minutes for a long period of time?

[featherlou]

Oh, no, just that the odd time it happened, it was like Myrna described - the little clock just turning around and around and around.