Hi Hugh, Let me see if I can add some mud to this water. If you want to have a server with a static IP address i.e. 192.168.0.2, then set this address on the servers NIC and in the router configs "exclude" that address. This will prevent the router's DHCP from giving out that address, Your router must have a setting that you can manually start or end DHCP at some IP address. For example in my router, I can start DHCP addresses at 192.168.0.15. This means that addresses 192.168.0.1 to 192.168.0.14 are "reserved" for static addresses such as your server. Hope this doesn't cloud the water too much.
Vin -----Original Message----- From: Windows Home/SOHO [mailto:[EMAIL PROTECTED] On Behalf Of Hugh Gundersen Sent: Sunday, June 18, 2006 3:02 AM To: [email protected] Subject: Re: Help - router messing about again On Sat, 17 Jun 2006 22:16:39 -0700, you wrote: >> If you have the computer's NIC ip manually set to 192.168.0.2 then >> the router MUST have DNS turned OFF. > >Did you mean, the router must have DHCP off? >In that case you could never have some clients on a network >with a dynamic IP if even one has a fixed IP. I'm not so sure >that's true. > >Gary VanderMolen Hi Gary, Wayne, Good morning from the UK! I have told the computer to use 192.168.0.2 and have also reserved the address in the router setup - as it always has been! This seems to have cured the problem but I have also limited the use of address from 255 available to 4 so with the other machines connected to the router it can only have 0.2 to use. I am now wondering what will happen when I put the new machine into use as the server - will it accept 0.2 or will it insist on staying at 0.3? Sir Hugh of Bognor -- ---------------------------------------- The WIN-HOME mailing list is powered by L-Soft's renowned LISTSERV(R) list management software. For more information, go to: http://www.lsoft.com/LISTSERV-powered.html
