QUOTE(level42 @ Oct 3 2007, 12:37 AM) [snapback]170438[/snapback]
2. Some computers loose connection to the DNS I.E "The IpAddress cannot resolve the DNS server."
That message makes absolutely no sense

DNS servers resolve a domain name
to an IP address. Since an IP address is just a four-byte integer value, commonly represented as separate bytes for human readability, they can't really do any resolving by themselves...

QUOTE(level42 @ Oct 3 2007, 12:37 AM) [snapback]170438[/snapback]
3. Some computers pulling weird 169.xxx.xxx.xxx Ip's - They should be 192.168.1.xxx
That's the same as #1. 169.x.x.x IP addresses are what Windows uses when it doesn't have another IP address for whatever reason.
QUOTE(level42 @ Oct 3 2007, 12:37 AM) [snapback]170438[/snapback]
Reset ipconfig - I.E ipconfig /release, ipconfig /renew/, ipconfig /flushdns
Aka releasing your IP address lease, requesting a new IP address, and then emptying the DNS resolution cache. I mention this explicitly because of what I will say next:
It
sounds like the DHCP server in your router is playing silly buggers. That would explain the lack of IP addresses on client machines, and could also explain the lack of DNS resolution. You could also have a b0rked DNS server in the router which would be causing the DNS issues, but merely having a dead DHCP server would do the same occasionally. I suspect that this is why your reset router, modem & switch solution works:
QUOTE(level42 @ Oct 3 2007, 12:37 AM) [snapback]170438[/snapback]
Reset Router Modem and Switch. - Unplug all for 30 seconds, Plug in modem till 4 leds are on, Plug in Router till leds come on, then plug in switch.
By restarting the router you'll also be restarting its internal DHCP and DNS servers, which may kick them into doing something useful for a period of time.
How to fix it? Well, the best solution would be to sort out the DHCP/DNS servers in the router to stop them misbehaving. Upgrading the firmware of the router might solve that. As might using 3rd party firmware for the router, if any exists (though that option is generally excitingly warranty-voiding). Alternatively you could buy a new router, but that seems like overkill until you know for sure that something in the router is causing problems - I'm just guessing, here, really.
A less practical option, but one that should still work, is sodding the DHCP server entirely and assigning static IP addresses to every machine connected to the router. You'll have to assign (obviously different) IP addresses to every machine, plus the same subnet mask (
probably either 255.255.255.0 or 255.255.0.0, but you'll be able to find out by checking what the router's handing out now), and also saying that the router is the default gateway (probably - again, check what's being assigned by the DHCP server now and just copy that, but set it up statically so Windows doesn't even have to talk to the DHCP server). Then set your ISP's DNS servers to be the DNS servers used by Windows. In theory their website will tell you what DNS servers to use. Alternatively you could use
OpenDNS for your DNS resolution - the IP addresses of their servers are at the bottom of their website.
If none of that works, I really don't have a clue