missing source

[galenwbritt]

Well.....sorry nothings working. I was just trying to offer advice from a backseat idiots standpoint. Maybe somebody else will come along and get you the hook-up you need to get you back online.

G

[shaky]

Actually, it works again. Dunno why. Started yesterday.

[jeffreyr]

Originally Posted by shaky

Galen, I've done that, run ad-aware scans, run virus scans, and anything else I could think of.
I may have to reset the entire system, but even that may not help.
I'm stuck.

did you every get the problem fixed? I've had that type of problem lots of times. sometimes I get it to work by unpluging the modem and let it reset for a few minutes and then plug it in and let it run thru its startup cycle again. also on IE, I make sure the box is checked on the connections tab on the internet options under the tools menu and select auto detect on the LAN.

[FunkyRes]

Site not found probably indicates a DNS error.

I don't know what the windows equivalent is - but in linux/osx you should be able to run a command called nslookup from the command line:

[mpeters@athens ~]$ nslookup www.cornsnakesource.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
www.cornsnakesource.com canonical name = cornsnakesource.com.
Name: cornsnakesource.com
Address: 65.99.253.59

-=-
I'm sure there is a windows equivalent to nslookup you can run from the DOS prompt - I've used it before when troubleshooting why a friends PC could not find my network printer - but I don't remember what it is.

Anyway - if your nameserver can't find it, that's why you can't get to it. If there is an alternate nameserver you can use, try that - otherwise, you may need to submit a support request to your ISP telling them their nameserver needs to rebuild it's cache, as that's probably the problem. If they use bind as their nameserver, they may just need to restart it - I've seen that happen before, bind gets stuck and stops updating its cache. But anyway, I suspect the problem is on their end.

What sometimes happens is a website sets a short life for the name resolution and the nameservers are suppose to check that often, but some ISPs ignore the life and only check for new IP address once a month, resulting in issues if the IP address of the website changed.

I got so fed up with my ISPs nameservers either going down or having bad info that I just run my own now - but that's probably not what you want to do.

[FunkyRes]

Another thing - some broadband routers (IE a wireless router) will cache DNS requests and act as a DNS server for your lan, sometimes you need to log onto your router and turn off the cache feature, or power cycle the router.