# Why Can't I Get To Job.com?

**URL:** <https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218>\
**Category:** Factual Questions\
**Created:** [December 14, 2009, 3:37pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218 "2009-12-14T15:37:31Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 14, 2009, 10:05pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/21 "2009-12-14T22:05:01Z")

</div>

> [@teletype](#):
>
> Just as an aside, if you want to test from an external location to see if a web site’s up for other people, you can try: [http://downforeveryoneorjustme.com/](http://downforeveryoneorjustme.com/)

Interesting site - I like that.  
It’s “Just Me” for [Jobs.com](http://Jobs.com)

---

<div class="post-metadata">

**Author:** ![sco3tt](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@sco3tt](https://boards.straightdope.com/u/sco3tt)\
**Post date:** [December 15, 2009, 12:49am UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/22 "2009-12-15T00:49:36Z")

</div>

What do you see if you run “nslookup [job.com](http://job.com)” from a command prompt?

This will probably tell you the host can’t be resolved as well, but assuming your own router isn’t also your name server, it should tell you which one you’re using, which in turn can help identify the problem.

You can also try “nslookup [job.com](http://job.com) 8.8.8.8” (where 8.8.8.8 is Google’s public DNS) and see if that’s not blocked for you. If that resolves, try editing your network settings to make 8.8.8.8 your DNS server (assuming you trust Google to handle all your DNS lookups) and see if you’re able to access the website.

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 1:06am UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/23 "2009-12-15T01:06:07Z")

</div>

> [@sco3tt](#):
>
> What do you see if you run “nslookup [job.com](http://job.com)” from a command prompt?
> 
> This will probably tell you the host can’t be resolved as well, but assuming your own router isn’t also your name server, it should tell you which one you’re using, which in turn can help identify the problem.
> 
> You can also try “nslookup [job.com](http://job.com) 8.8.8.8” (where 8.8.8.8 is Google’s public DNS) and see if that’s not blocked for you. If that resolves, try editing your network settings to make 8.8.8.8 your DNS server (assuming you trust Google to handle all your DNS lookups) and see if you’re able to access the website.

Returns “DNS request timed out. Timeout was 2 seconds.\*\*\*Can’t find server name 192.168.1.1: Timed out.”

nslookup [job.com](http://job.com) 8.8.8.8 returns “DNS request timed out. Timeout was 2 seconds.\*\*\*Can’t find server name 8.8.8.8: Timed out.”

I also tried “nslookup [google.com](http://google.com)” and got the same as above, though I have no problem getting to Google or any other site via FF or IE8.

---

<div class="post-metadata">

**Author:** ![sco3tt](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@sco3tt](https://boards.straightdope.com/u/sco3tt)\
**Post date:** [December 15, 2009, 2:53am UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/24 "2009-12-15T02:53:14Z")

</div>

I am guessing that you have a router on your network (between your PC and the cable or DSL modem) and that your PC’s network connection is set to DHCP (i.e. the “Obtain an address automatically” option). Is this true?

The 192.168.1.1 address in your error message is a private IP address, and is used as the out-of-the-box local IP address for a lot of routers. The router also typically will handle DNS resolution locally (acting as a proxy to a real nameserver at your ISP) for all of the machines on your network (especially if you’re using DHCP).

If all this holds true for you, the implication of what you’ve posted is that the DNS resolution is failing at your router. This is what the error message above is telling you… you’re asking the router (at 192.168.1.1) to resolve the name, but the router is not responding. Windows will cache DNS lookups, so the fact that you’re still able to access other commonly-used sites is probably because the cached IPs (from some point in the past when DNS was still working) are being used for them.

Did you happen to change your router’s local IP address from 192.168.1.1 to something else recently? What do you see if you browse to [http://192.168.1.1](http://192.168.1.1)? This will typically show you the router’s status page (or possibly an admin login prompt). Regardless, as long as it shows something without timing out, this is a good sign, implying the router is still at that address. On the other hand, if this also times out with no response, it sounds like maybe the router’s IP address has changed.

In either case, rebooting the router (just unplug it for about 30 seconds) would be worth a shot. Try that and see if anything changes.

---

<div class="post-metadata">

**Author:** ![sco3tt](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@sco3tt](https://boards.straightdope.com/u/sco3tt)\
**Post date:** [December 15, 2009, 3:04am UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/25 "2009-12-15T03:04:43Z")

</div>

> [@Fritz](#):
>
> nslookup [job.com](http://job.com) 8.8.8.8 returns “DNS request timed out. Timeout was 2 seconds.\*\*\*Can’t find server name 8.8.8.8: Timed out.”

I overlooked this before I posted that last response. This is really curious, as it almost seems like something is blocking ns lookups from your machine altogether. What happens if you do a traceroute to this address (i.e. “tracert 8.8.8.8”)?

Also, do you have other PCs on your local network that you can try any of this from? So far, the problem sounds like it’s constrained to your network, not your ISP. Therefore, if it fails similarly from another machine, I would suspect the router, but if not it sounds like there’s something up with your PC.

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 11:45am UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/26 "2009-12-15T11:45:23Z")

</div>

> [@sco3tt](#):
>
> I am guessing that you have a router on your network (between your PC and the cable or DSL modem) and that your PC’s network connection is set to DHCP (i.e. the “Obtain an address automatically” option). Is this true?

Correct - a wireless router between computer and DSL modem. The computer in question is hardwired to this router. Set to DHCP.

> [@sco3tt](#):
>
> Did you happen to change your router’s local IP address from 192.168.1.1 to something else recently? What do you see if you browse to [http://192.168.1.1](http://192.168.1.1)? This will typically show you the router’s status page (or possibly an admin login prompt). Regardless, as long as it shows something without timing out, this is a good sign, implying the router is still at that address. On the other hand, if this also times out with no response, it sounds like maybe the router’s IP address has changed.

No change to configuration or IP address recently.

> [@sco3tt](#):
>
> What do you see if you browse to [http://192.168.1.1](http://192.168.1.1)?

Login page to my wireless router.

> [@sco3tt](#):
>
> In either case, rebooting the router (just unplug it for about 30 seconds) would be worth a shot. Try that and see if anything changes.

No change.

This is good information. It didn’t occur to me that the router might be causing this. Eliminating the router and connecting directly to the DSL modem should be telling, no?

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 11:50am UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/27 "2009-12-15T11:50:31Z")

</div>

> [@sco3tt](#):
>
> I overlooked this before I posted that last response. This is really curious, as it almost seems like something is blocking ns lookups from your machine altogether. What happens if you do a traceroute to this address (i.e. “tracert 8.8.8.8”)?

C:\DOCUME~1&gt;tracert 8.8.8.8

Tracing route to [google-public-dns-a.google.com](http://google-public-dns-a.google.com) [8.8.8.8]  
over a maximum of 30 hops:

1 \<1 ms \<1 ms \<1 ms 192.168.1.1  
2 1 ms 1 ms 1 ms 192.168.254.254  
3 25 ms 25 ms 25 ms [h1.136.18.98.dynamic.ip.windstream.net](http://h1.136.18.98.dynamic.ip.windstream.net) [98.18.13  
6.1]  
4 26 ms 26 ms 25 ms [h58.122.90.75.static.ip.windstream.net](http://h58.122.90.75.static.ip.windstream.net) [75.90.12  
2.58]  
5 28 ms 27 ms 28 ms [h84.122.90.75.static.ip.windstream.net](http://h84.122.90.75.static.ip.windstream.net) [75.90.12  
2.84]  
6 29 ms 29 ms 29 ms [h96.254.213.151.static.ip.windstream.net](http://h96.254.213.151.static.ip.windstream.net) [151.21  
3.254.96]  
7 29 ms 29 ms 30 ms [te-3-2.car2.Atlanta2.Level3.net](http://te-3-2.car2.Atlanta2.Level3.net) [4.71.254.13]  
8 36 ms 35 ms 35 ms [ae-72-52.ebr2.Atlanta2.Level3.net](http://ae-72-52.ebr2.Atlanta2.Level3.net) [4.68.103.61]

9 36 ms 34 ms \* [ae-63-60.ebr3.Atlanta2.Level3.net](http://ae-63-60.ebr3.Atlanta2.Level3.net) [4.69.138.4]  
10 53 ms 54 ms 53 ms [ae-2.ebr1.Washington1.Level3.net](http://ae-2.ebr1.Washington1.Level3.net) [4.69.132.86]  
11 48 ms 53 ms 54 ms [ae-81-81.csw3.Washington1.Level3.net](http://ae-81-81.csw3.Washington1.Level3.net) [4.69.134.1  
38]  
12 44 ms 43 ms 43 ms [ae-3-89.edge1.Washington1.Level3.net](http://ae-3-89.edge1.Washington1.Level3.net) [4.68.17.14  
4]  
13 45 ms 44 ms 44 ms [GOOGLE-INC.edge1.Washington1.Level3.net](http://GOOGLE-INC.edge1.Washington1.Level3.net) [4.79.23  
1.6]  
14 45 ms 44 ms 44 ms 209.85.241.50  
15 46 ms 45 ms 44 ms 64.233.175.219  
16 46 ms 53 ms 54 ms 216.239.49.149  
17 45 ms 44 ms 44 ms [google-public-dns-a.google.com](http://google-public-dns-a.google.com) [8.8.8.8]

Trace complete.

> [@sco3tt](#):
>
> Also, do you have other PCs on your local network that you can try any of this from? So far, the problem sounds like it’s constrained to your network, not your ISP. Therefore, if it fails similarly from another machine, I would suspect the router, but if not it sounds like there’s something up with your PC.

Yes, I have another computer that I can try, but it needs to be connected. I’ll do this later today, and also connect directly to the modem.

If it is the router, what parameters for the router might be implicated?

Thanks for your help - sounds like I’m getting somewhere with this annoying problem. I’ll report back later today.

---

<div class="post-metadata">

**Author:** ![Saint\_Cad](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/saint_cad/32/18907_2.png) [@Saint\_Cad](https://boards.straightdope.com/u/Saint_Cad)\
**Post date:** [December 15, 2009, 3:23pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/28 "2009-12-15T15:23:54Z")

</div>

> [@myskepticsight](#):
>
> I’ll tell you, at least in my experiences, [Job.com](http://Job.com) has a lot of bs listings. They’ve had the exact same HR job listing up (company confidential of course) for like this past year, and the job is one of those too-good to be true. 45k starting salary, requires no experience. Here most no experience type jobs start at 30 or lower even. I fell for one of their listings once and all I got was some company calling me asking me if I wanted to “get more education” even though it clearly said I was currently working on a masters degree.
> 
> So long story short, watch out for phony ass listings there.

Same with careerbuilder and monster. Too bad they don’t have a spam filter.

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 3:38pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/29 "2009-12-15T15:38:48Z")

</div>

I bypassed the router and connected directly to the DSL modem - still not able to connect to [Job.com](http://Job.com). That leaves either the computer or the modem. And maybe the ISP?

---

<div class="post-metadata">

**Author:** ![ZipperJJ](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/zipperjj/32/211_2.png) [@ZipperJJ](https://boards.straightdope.com/u/ZipperJJ)\
**Post date:** [December 15, 2009, 3:57pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/30 "2009-12-15T15:57:43Z")

</div>

Stay connected directly to the modem and now do an nslookup [jobs.com](http://jobs.com)

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 4:15pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/31 "2009-12-15T16:15:15Z")

</div>

> [@ZipperJJ](#):
>
> Stay connected directly to the modem and now do an nslookup [jobs.com](http://jobs.com)

Will do shortly.

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 4:21pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/32 "2009-12-15T16:21:07Z")

</div>

> [@ZipperJJ](#):
>
> Stay connected directly to the modem and now do an nslookup [jobs.com](http://jobs.com)

Returns:

C:\DOCUME~1&gt;nslookup [job.com](http://job.com)  
DNS request timed out.  
timeout was 2 seconds.  
\*\*\* Can’t find server name for address 192.168.254.254: Timed out  
\*\*\* Default servers are not available  
Server: UnKnown  
Address: 192.168.254.254

DNS request timed out.  
timeout was 2 seconds.  
Non-authoritative answer:  
Name: [job.com](http://job.com)  
Addresses: 208.17.204.150, 208.17.204.176, 208.17.204.152, 208.17.204.153  
208.17.204.177, 208.17.204.170, 208.17.204.179, 208.17.204.145, 208.17  
.204.146  
208.17.204.148, 208.17.204.155, 208.17.204.149, 208.17.204.171, 208.17  
.204.128  
208.17.204.129, 208.17.204.172, 208.17.204.173, 208.17.204.178, 208.17  
.204.140  
208.17.204.180, 208.17.204.182, 208.17.204.131, 208.17.204.189

---

<div class="post-metadata">

**Author:** ![goldmund](https://avatars.discourse-cdn.com/v4/letter/g/a4c791/32.png) [@goldmund](https://boards.straightdope.com/u/goldmund)\
**Post date:** [December 15, 2009, 5:10pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/33 "2009-12-15T17:10:30Z")

</div>

> [@Fritz](#):
>
> Returns:
> 
> C:\DOCUME~1&gt;nslookup [job.com](http://job.com)  
> DNS request timed out.  
> timeout was 2 seconds.  
> \*\*\* Can’t find server name for address 192.168.254.254: Timed out  
> \*\*\* Default servers are not available  
> Server: UnKnown  
> Address: 192.168.254.254
> 
> DNS request timed out.  
> timeout was 2 seconds.  
> Non-authoritative answer:  
> Name: [job.com](http://job.com)  
> Addresses: 208.17.204.150, 208.17.204.176, 208.17.204.152, 208.17.204.153  
> 208.17.204.177, 208.17.204.170, 208.17.204.179, 208.17.204.145, 208.17  
> .204.146  
> 208.17.204.148, 208.17.204.155, 208.17.204.149, 208.17.204.171, 208.17  
> .204.128  
> 208.17.204.129, 208.17.204.172, 208.17.204.173, 208.17.204.178, 208.17  
> .204.140  
> 208.17.204.180, 208.17.204.182, 208.17.204.131, 208.17.204.189

Well that means it is looking up the addresses properly. The error in the beginning is because it’s trying to do a reverse lookup, to resolve 192.168.254.254 to a hostname, so it can display it as such. Not really a concern though.

If you still can’t browse there, try running “ipconfig /flushdns” from your command prompt, restart your browser and try again. Also try to ping [job.com](http://job.com) from the command line as well.

---

<div class="post-metadata">

**Author:** ![BobArrgh](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bobarrgh/32/2881_2.png) [@BobArrgh](https://boards.straightdope.com/u/BobArrgh)\
**Post date:** [December 15, 2009, 5:33pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/34 "2009-12-15T17:33:56Z")

</div>

Some people keep referring to “[jobs.com](http://jobs.com)”. Please note that the OP is having trouble connecting to “[job.com](http://job.com)”.

Try the following commands: “tracert [job.com](http://job.com)” and “tracert 208.17.204.128”.

That IP address is the address given for “[job.com](http://job.com)”.

You might also try entering “[http://208.17.204.128/](http://208.17.204.128/)” into your browser’s Address/URL bar and see what happens.

---

<div class="post-metadata">

**Author:** ![Contrapuntal](https://avatars.discourse-cdn.com/v4/letter/c/e274bd/32.png) [@Contrapuntal](https://boards.straightdope.com/u/Contrapuntal)\
**Post date:** [December 15, 2009, 5:36pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/35 "2009-12-15T17:36:56Z")

</div>

> [@BobArrgh](#):
>
> Some people keep referring to “[jobs.com](http://jobs.com)”. Please note that the OP is having trouble connecting to “[job.com](http://job.com)”.

In the OP he said job. In post 21 he said jobs.

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 5:39pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/36 "2009-12-15T17:39:12Z")

</div>

> [@Contrapuntal](#):
>
> In the OP he said job. In post 21 he said jobs.

So I did. Sorry, I meant [Job.com](http://Job.com)

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 5:50pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/37 "2009-12-15T17:50:26Z")

</div>

> [@BobArrgh](#):
>
> Try the following commands: “tracert [job.com](http://job.com)” and “tracert 208.17.204.128”.

**“tracert [job.com](http://job.com)” returns:**

C:\DOCUME~1&gt;tracert [job.com](http://job.com)

Tracing route to [job.com](http://job.com) [208.17.204.145]  
over a maximum of 30 hops:

1 \<1 ms \<1 ms \<1 ms 192.168.1.1  
2 1 ms 1 ms 1 ms 192.168.254.254  
3 26 ms 26 ms 26 ms [h1.208.140.67.dynamic.ip.windstream.net](http://h1.208.140.67.dynamic.ip.windstream.net) [67.140.  
208.1]  
4 25 ms 26 ms 26 ms [h58.122.90.75.static.ip.windstream.net](http://h58.122.90.75.static.ip.windstream.net) [75.90.12  
2.58]  
5 28 ms 28 ms 28 ms [h84.122.90.75.static.ip.windstream.net](http://h84.122.90.75.static.ip.windstream.net) [75.90.12  
2.84]  
6 30 ms 33 ms 29 ms [h96.254.213.151.static.ip.windstream.net](http://h96.254.213.151.static.ip.windstream.net) [151.21  
3.254.96]  
7 29 ms 30 ms 29 ms [te-3-2.car2.Atlanta2.Level3.net](http://te-3-2.car2.Atlanta2.Level3.net) [4.71.254.13]  
8 30 ms 34 ms 36 ms [ae-62-51.ebr2.Atlanta2.Level3.net](http://ae-62-51.ebr2.Atlanta2.Level3.net) [4.68.103.29]

9 33 ms 35 ms 36 ms [ae-63-60.ebr3.Atlanta2.Level3.net](http://ae-63-60.ebr3.Atlanta2.Level3.net) [4.69.138.4]  
10 44 ms 51 ms 53 ms [ae-2.ebr1.Washington1.Level3.net](http://ae-2.ebr1.Washington1.Level3.net) [4.69.132.86]  
11 53 ms 53 ms 54 ms [ae-61-61.csw1.Washington1.Level3.net](http://ae-61-61.csw1.Washington1.Level3.net) [4.69.134.1  
30]  
12 45 ms 44 ms 43 ms [ae-1-69.edge2.Washington4.Level3.net](http://ae-1-69.edge2.Washington4.Level3.net) [4.68.17.19  
]  
13 46 ms 44 ms 45 ms [COX-COMMUNI.edge2.Washington4.Level3.net](http://COX-COMMUNI.edge2.Washington4.Level3.net) [4.53.1  
14.58]  
14 46 ms 46 ms 46 ms [mrfddsrj02-ge710.rd.dc.cox.net](http://mrfddsrj02-ge710.rd.dc.cox.net) [68.1.1.7]  
15 52 ms 49 ms 49 ms [wsip-98-172-152-158.dc.dc.cox.net](http://wsip-98-172-152-158.dc.dc.cox.net) [98.172.152.15  
8]  
16 \* \* \* Request timed out.  
17 \* \* \* Request timed out.  
18 \* \* \* Request timed out.  
19 \* \* \* Request timed out.  
20 \* \* \* Request timed out.  
21 \* \* \* Request timed out.  
22 \* \* \* Request timed out.  
23 \* \* \* Request timed out.  
24 \* \* \* Request timed out.  
25 \* \* \* Request timed out.  
26 \* \* \* Request timed out.  
27 \* \* \* Request timed out.  
28 \* \* \* Request timed out.  
29 \* \* \* Request timed out.  
30 \* \* \* Request timed out.

Trace complete.

* * *

**“tracert 208.17.204.128” returns:**

C:\DOCUME~1\SUEAND~1\>tracert 208.17.204.128

Tracing route to [www7b.job.com](http://www7b.job.com) [208.17.204.128]  
over a maximum of 30 hops:

1 \<1 ms \<1 ms \<1 ms 192.168.1.1  
2 1 ms 1 ms 1 ms 192.168.254.254  
3 26 ms 26 ms 26 ms [h1.208.140.67.dynamic.ip.windstream.net](http://h1.208.140.67.dynamic.ip.windstream.net) [67.140  
208.1]  
4 25 ms 26 ms 26 ms [h60.122.90.75.static.ip.windstream.net](http://h60.122.90.75.static.ip.windstream.net) [75.90.1  
2.60]  
5 28 ms 28 ms 28 ms [h17.248.213.151.static.ip.windstream.net](http://h17.248.213.151.static.ip.windstream.net) [151.2  
3.248.17]  
6 30 ms 29 ms 29 ms [h98.254.213.151.static.ip.windstream.net](http://h98.254.213.151.static.ip.windstream.net) [151.2  
3.254.98]  
7 30 ms 28 ms 29 ms [te-3-2.car2.Atlanta2.Level3.net](http://te-3-2.car2.Atlanta2.Level3.net) [4.71.254.13]  
8 30 ms 35 ms 36 ms [ae-72-52.ebr2.Atlanta2.Level3.net](http://ae-72-52.ebr2.Atlanta2.Level3.net) [4.68.103.61]

9 35 ms 35 ms 35 ms [ae-63-60.ebr3.Atlanta2.Level3.net](http://ae-63-60.ebr3.Atlanta2.Level3.net) [4.69.138.4]  
10 43 ms 51 ms 53 ms [ae-2.ebr1.Washington1.Level3.net](http://ae-2.ebr1.Washington1.Level3.net) [4.69.132.86]  
11 50 ms 53 ms 53 ms [ae-61-61.csw1.Washington1.Level3.net](http://ae-61-61.csw1.Washington1.Level3.net) [4.69.134.  
30]  
12 45 ms 45 ms 45 ms [ae-1-69.edge2.Washington4.Level3.net](http://ae-1-69.edge2.Washington4.Level3.net) [4.68.17.1  
]  
13 46 ms 46 ms 44 ms [COX-COMMUNI.edge2.Washington4.Level3.net](http://COX-COMMUNI.edge2.Washington4.Level3.net) [4.53.  
14.58]  
14 45 ms 46 ms 46 ms [mrfddsrj01-ge710.rd.dc.cox.net](http://mrfddsrj01-ge710.rd.dc.cox.net) [68.1.1.5]  
15 48 ms 49 ms 48 ms [wsip-98-172-152-158.dc.dc.cox.net](http://wsip-98-172-152-158.dc.dc.cox.net) [98.172.152.1  
8]  
16 \* \* \* Request timed out.  
17 \* \* \* Request timed out.  
18 \* \* \* Request timed out.  
19 \* \* \* Request timed out.  
20 \* \* \* Request timed out.  
21 \* \* \* Request timed out.  
22 \* \* \* Request timed out.  
23 \* \* \* Request timed out.  
24 \* \* \* Request timed out.  
25 \* \* \* Request timed out.  
26 \* \* \* Request timed out.  
27 \* \* \* Request timed out.  
28 \* \* \* Request timed out.  
29 \* \* \* Request timed out.  
30 \* \* \* Request timed out.

Trace complete.

> [@BobArrgh](#):
>
> You might also try entering “[http://208.17.204.128/](http://208.17.204.128/)” into your browser’s Address/URL bar and see what happens.

This does get me there, as noted to **Sunspace** above.

---

<div class="post-metadata">

**Author:** ![jjimm](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@jjimm](https://boards.straightdope.com/u/jjimm)\
**Post date:** [December 15, 2009, 5:55pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/38 "2009-12-15T17:55:14Z")

</div>

You’ve clearly got a problem with your cox.

ETA: it times out for me at my office, just after the internal gateway IP address. But at home it works fine.

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 5:55pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/39 "2009-12-15T17:55:45Z")

</div>

> [@teletype](#):
>
> If you still can’t browse there, try running “ipconfig /flushdns” from your command prompt, restart your browser and try again. Also try to ping [job.com](http://job.com) from the command line as well.

“ipconfig /flushdns”, restarted FF: No Good.

* * *

C:\DOCUME~1&gt;ping [job.com](http://job.com)

Pinging [job.com](http://job.com) [208.17.204.179] with 32 bytes of data:

Request timed out.  
Request timed out.  
Request timed out.  
Request timed out.

Ping statistics for 208.17.204.179:  
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

---

<div class="post-metadata">

**Author:** ![Fritz](https://avatars.discourse-cdn.com/v4/letter/f/c57346/32.png) [@Fritz](https://boards.straightdope.com/u/Fritz)\
**Post date:** [December 15, 2009, 5:58pm UTC](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218/40 "2009-12-15T17:58:28Z")

</div>

> [@jjimm](#):
>
> You’ve clearly got a problem with your cox.

cox?

[Previous page](https://boards.straightdope.com/t/why-cant-i-get-to-job-com/521218.md?page=1)