Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
More info... I think that Norton Firewall was giving me grief. I turned it off. The two DNS servers reported by my attbi connection are: 204.127.202.19 216.148.227.79 I can ping them and get a response! Which leads me to believe that I now have outside connectivity (perhaps killing the firewall did it?) But if I execute nslookup I get: DNS request timed out. timeout was 2 seconds. *** Can't find server name for address 204.127.202.19: Timed out DNS request timed out. timeout was 2 seconds. *** Can't find server name for address 216.148.227.79: Timed out *** Default servers are not available Default Server: UnKnown Address: 204.127.202.19 > So, I don't fully understand what's going on. I didn't think that DNS servers needed to lookup their own names. Duane At 03:26 PM 2/12/2003 -0500, Jerry Feldman wrote: >Duane, >Sounds like either your router is not working or your ISP's DHCP server >is broken. >Is your staticly connected box connected directly to the cable modem (or >DSL) or is it connected directly to the router? > >Assuming your cable or DSL connection and equipment is working >correctly: >I would take the following steps: >1. Bypass ther router and connect your DHCP client machine directly to >the DSL or cable modem. If everything works, we can assume the problem >is at the router end. If not, the problem is with your cable/DSL >equipment or your ISP. >2. reboot the router, reconnect it and check all the settings. You >should be able to find the assigned IP address and the appropriate DNS >server. >3. If the router seems to be the problem, reset the router to factory >settings and re-input the various settings. Possibly even reflash the >firmware. >4. If things still don't work and you are sure it is the router, if you >live in a high rise, take it up to the roof and tell it to make like a >bird. If you don't have easy access to a high rise, just drop it out of >your car on 128. > > >On Wed, 12 Feb 2003 14:38:29 -0500 >Duane Morin <dmorin at morinfamily.com> wrote: > > > This morning one of my machines, which is connected via DHCP to my > > router, apparently stopped doing DNS properly. I am guessing this > > because all of the operations from that machine that connect directly > > to an IP, i.e. my mail program, work fine, but attempt to go to a web > > site by name fails. > > > > My statically configured box which has /etc/resolv.conf with 3 > > nameservers in it continues to work fine (although I have not rebooted > > it lately). Anybody got suggestions on what might be going wrong with > > this machine, and where I can start looking? I tried telling it the > > DNS servers (while keeping it on DHCP) but that failed. > > > > Ok, wait, tried a few things and it's weirder than I thought. Any > > attempt to ping addresses by number outside of my own domain fail as > > well, which suggests I don't have a connection to the outside. I do > > have a connection to the inside of my network, though, so I know that > > I have wireless at least. So I guess what's happening is that my > > router has decided to stop allowing this machine to connect to the > > outside world? Why would that be? I have confirmed that my other > > machine can connect to outside machines both by name and number, and > > look things up in dns. > > > > This is an XP machine, in case that matters. The static box that's > > working is Linux (of course). > > > > Duane > > > > _______________________________________________ > > Discuss mailing list > > Discuss at blu.org > > http://www.blu.org/mailman/listinfo/discuss > >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |