On 12-01-01 11:55 AM, ed stuckems wrote: > Folks: > > This may be slightly off-topic, so I hope you'll consider this request > for help appropriate for this list. > > My home network is suddenly misbehaving and after poking around a bit > I'm at a loss to explain why things aren't working and I can't seem to > fix the problem. Any help/advice would be greatly appreciated. > > Here's the problem ... My kids' computers recently stopped serving web > pages. After poking around a bit, it appears that dns requests from > their machines aren't being resolved. Poking around more, I've > discovered that the game consoles and the android based phone aren't > working either and I suspect it's for the same reasons. The phone > worked on the wifi network as recently as last week. However, there > are machines on the network that are working! My linux box, mac book > pro (running Mac OSX), iPad, and Windows Vista computers are all > working. > > All the machines are able to access internal machines/servers/services > via ip address (I'm not using dns for internal servers) and everything > internal can be pinged and is able to ping (most) everything else. On > those machines that aren't working, nslookup is not able to resolve > host names and nslookup returns stating that the dns server(s) timed > out. > > There are 2 dns servers provided to clients on the network: the > caching server on the router, and the dns server provided by my > service provider. nslookup reports time outs for both servers. > > I'm at a loss to explain what's happening and any advice or guidance > for correcting the issue would be greatly appreciated. > > regards > eds. > _______________________________________________ > Linux mailing list > [email protected] > http://oclug.on.ca/mailman/listinfo/linux Doesn't seem off-topic at all.
Some more info would help: 1) Can you get DHCP info from each machine? Network, Netmask, IP Address, DNS Servers, Gateway, Routing. Compare. 2) Is there any difference between working versus non-resolving machines? I.E. working are statically assigned versus non-resolving are assigned by DHCP? Working are wired versus wireless? Do you have documentation on what you "THINK" the network looks like versus what it actually is? Have you scanned the network with nmap to see what's there? (-O to find out what nmap thinks is present). 3) Is there a DHCP server conflict on the network? Often there may be competing DHCP servers providing different setups to clients. Have your kids added a router unknown to you? 4) Are you blocking port 53 at the firewall? Or on the internal DNS server? These are just a few questions, but the situation is pretty easy to diagnose by watching traffic on the network with Wireshark or whatever. -- Bill Strosberg _______________________________________________ Linux mailing list [email protected] http://oclug.on.ca/mailman/listinfo/linux
