Hello, Often after I connect to my server with kppp, kmail and Netscape can't find the server. I can't ping out when this happens either. 70% of the time after booting, Netscape and kmail are just fine. If I just leave my computer on for a while when having problems, it does not clear up. Which indicates to me that my internet provider is not the problem. Because, rebooting helps about 80% of the time. My modem is set to /dev/ttyS1, so no lock problems. Has anyone had anything similar to this? It's weird. Lowering the baud rate does not help. I operate off of a Winbook XL laptop with SuSE 6.2 installed. I am using a Linksys 10/100 + 56k combo card. /var/log/messages doesn't really offer any clues. Thanks George -- My personal website http://www.firstnethou.com/gz/welcome.htm -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
George Zeigler wrote:
Hello, Often after I connect to my server with kppp, kmail and Netscape can't find the server. I can't ping out when this happens either. 70% of the time after booting, Netscape and kmail are just fine. If I just leave my computer on for a while when having problems, it does not clear up. Which indicates to me that my internet provider is not the problem. Because, rebooting helps about 80% of the time. My modem is set to /dev/ttyS1, so no lock problems.
Has anyone had anything similar to this? It's weird. Lowering the baud rate does not help. I operate off of a Winbook XL laptop with SuSE 6.2 installed. I am using a Linksys 10/100 + 56k combo card. /var/log/messages doesn't really offer any clues.
nscd was introduced in 6.2, it caches things so that access to network databases is faster. One of those databases is dns and that means that if netscape or kmail access a site before you are connected the fact that they don't have an address is cached and it continues to report that the address doesn't for the negative-time-to-live in /etc/nscd.conf. Your problem sounds like a problem with nscd. You can turn off nscd or use "nscd -i hosts" to flush that cache N.B. that will work with SuSE 6.3 I am not sure that it is available in 6.2. See also: http://sdb.suse.de/cgi-bin/sdbsearch_en.cgi?stichwort=nscd /Michael -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (2)
-
genz1968@mtu-net.ru
-
Michael.Salmon@uab.ericsson.se