Hi Andy, We have it fixed. The DNS server address was readily available in the router setup utility.
Thanks again for the help. Rod Lindgren -----Original Message----- From: Windows Home/SOHO [mailto:[EMAIL PROTECTED] Behalf Of Andy Medina Sent: Sunday, May 01, 2005 2:22 PM To: [email protected] Subject: Re: NETworking: On Sun, 1 May 2005, Rod Lindgren wrote: > Hi Wayne, > > No, I was not talking about changing the router's DNS. I was > talking about the DNS server field on the manual > configuration of one of the computers on the net. Up to now, > when manually configuring it, we used these settings: > > IP address - 192.168.0.100 > Subnet Mask - 255.255.255.0 > Default Gateway - 192.168.0.1 > Primary DNS Server - Blank > Secondary DNS Server - Blank > > Having found that the router listed a DNS Server address as > something similar to 24.205.192.75, I thought to put that > into the Computer's blank. Sandi says she uses 192.168.0.1. I > will try both in about an hour when I go to my friend's house > and have access to his computer. You have to enter at least one DNS server IP address if you are using a static (manual) configuration because the machine does not request the info from the router. But you only need one, any other DNS server IP address entries are optional And you are better off entering an IP address for the four items I mentioned before, even if you have to use the router's IP address for the DNS server, in case the DNS server IP address is unknown. Using the router's IP address as a DNS server with success however depends on the router. Not all routers support the DNS lookup relay service. So that's not a given. But most modern routers should support relaying a DNS lookup. If you enter the router's IP address as the *only* DNS server and it does not work, that may be one reason why. Another reason might be the router not having the correct DNS information. Incorrect DNS information in the router would also show up in DHCP configured computers though. One quick way to tell if DNS could be the culprit: use an *IP* address instead of a *web* address in your browser. For example use - 150.135.40.100 - instead of - cals.arizona.edu -. If you get there using the *number* instead of the *name*, then the DNS service is most likely where the problem resides. -- ---------------------------------------- The WIN-HOME list is hosted on a Windows 2000(TM) machine running L-Soft international's LISTSERV(R) software. To unsubscribe, write to [EMAIL PROTECTED] If you have questions about the list, write to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.0 - Release Date: 4/29/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.0 - Release Date: 4/29/2005 -- ---------------------------------------- The WIN-HOME list is hosted on a Windows 2000(TM) machine running L-Soft international's LISTSERV(R) software. To unsubscribe, write to [EMAIL PROTECTED] If you have questions about the list, write to [EMAIL PROTECTED]
