-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Does the management front end on the SMC have an option to release and renew the dynamic IP that Shaw assigns? If this does not populate the DNS servers on the SMC router, then the problem is likely an error in the SMC firmware. Unless there is an updated firmware, you may be better served by buying a new router (I have a couple of linksys wireless routers and a couple of linux boxes with different distros that all work fine with Shaw, so you have a lot of choice here).
Trouble shooting this is not really worth the time, since you can't fix the problem (The SMC is a closed appliance that you do not have access to). If buying a new $80 router fixes the problem, then it is not even worth 1 hour of my time to troubleshoot. Of course if you are curious then it is worth the time. It would be interesting to see the differences between the linux box and the SMC, but from a curiosity/educational point of view, not really a technical troubleshooting point of view. Ethereal is a neat tool, especially if have/are reading/learning about TCP/IP (Shawn, my review of that giant TCP/IP book should be ready this week). An old fashioned hub is great in this case, since it repeats packets to all ports, making it easy for Ethereal to capture them (ie cable modem to hub, then both the linux box and SMC router to the hub). Cheers __ Carl wrote: > My home network has decided to stop resolving names today. Eg. If I ping > google.com I get unknown host yet if I ping 64.233.167.99 I get > responses. If I enter host google.com I get: > ;; connection timed out; no servers could be reached > > I have several computers connected to an SMC router which is connected > to a Shaw cable modem. The computer I have using now is running Fedora > core 3. > > While connected through the SMC Barricade router my /etc/resolv.conf is: > > ; generated by NetworkManager, do not edit! > search cg.shawcable.net > nameserver 192.168.2.1 > > If I browse to 192.168.2.1 on the status page, among other things I see: > > Primary DNS: 0.0.0.0 > Secondary DNS: 0.0.0.0 > > > If I connect my computer directly to the cable modem things are good, > name resolution works and and my /etc/resolv.conf looks like: > > ; generated by NetworkManager, do not edit! > search cg.shawcable.net > nameserver 64.59.135.133 > nameserver 64.59.135.135 > > > To me it seems like the SMC router is not getting the DNS information > correctly from the Shaw DHCP server. I phoned Shaw and they said it is a > problem with my SMC router. I talked to SMC tech support and they got me > to manually enter the DNS servers and then it works. I don't want to > have to manually setup the DNS config but they offer no other solution. > > Does anyone know why the SMC router might have trouble receiving the DNS > info? How can I trouble shoot this? Would using Ethereal to see what is > happening be worthwhile? > > Thanks, > > Carl > > > > > > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEMXXFwRXgH3rKGfMRAtvyAJ4g7GTKxmPSGB5HOVOsl7KLgPhccQCbBdha wAhexeqjprJYNPXfo8t+hso= =PJol -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
