Any chance you guys (Ruskin and Grant) are on the same ISP? You both seem to be from Florida with the same problem. As pointed out before, it's probably a DNS issue (and given the recent flurry of activity around DNS exploits, it's possible that your ISP hasn't patched yet, or created problems when patching). It could also be a bad route, or a misbehaving proxy at your ISP.
Try this, (in windows):
Start->Run->cmd
at the command prompt, type:
nslookup
www.jkowners.com
Compare that to the same command run from work.
If they are the same, then it's likely a routing issue or a proxy issue. To determine, get back to your command prompt (from home), and type:
tracert
www.jkowners.com
Now, the above command may or may not be useful depending on your ISP's handling of ICMP packets (i.e. they may block packets of this type). However, what you want to look for here are timeout's (it'll be obvious in the output). If there's a timeout at a particular hop, that means either the route's bad somewhere (or a flaky intermediate node), or the packets are being blocked.
If you get all the way to the site using tracert, then it's likely a proxy or traffic filtering issue. To test this, find a free proxy server on the internet (use google), configure that as your proxy (again, use google for instructions), and try again. If you access it just fine, then you know it's a proxy or filtering issue at your ISP.
!c
