P.S And Congratulations to Vera!
Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Hart Sent: 02 August 2007 11:52 To: ProFox Email List Subject: RE: [NF] Win 2K Networking Question Hi Dave If you would like to talk to my Nephew who is a Guru with Networks, I can give you his phone no. He has already agreed to talk to you. Ring me on my Mobile before 2.30. or after 6.00pm. (Vera becomes a British Citizen today) 07885 963 857 Cheers Peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Crozier Sent: 02 August 2007 10:46 To: 'ProFox Email List' Subject: RE: [NF] Win 2K Networking Question Peter, Thanks for your input. That is exactly my thinking on the problem but it doesn't seem to work consistently. Initially I thought it was because I hadn't rebooted the terminals when changing gateways etc., but this is so inconsistent I'm really confused. In my lay mans terms, what I'd really like to do is leave the clients so they automatically are set up without having to manually set gateways/DNS and then set up the Server to route all the Internet requests through itself to the router. However (1) how do I do this easily - or the "best way" and (2) how do I set the server to relay any DNS requests out to the router or an external DNS, whichever is the best option. I read somewhere that you can set up the "Active Directory" so that DNS values are loaded up onto the terminal from the Server i.e so you only need to set up the server once, but I can't find reference to it anywhere. Even though this is only a small network I'd like to sort out the "best practice" as I guess that I've fudged the issue in the past by always using the DHCP on the router, which I don't think is the correct way - even though it works. As the owner of the network said, if the Router dies then all his network would die as it couldn't allocate IP addresses to the workstations, whereas if the Server runs DHCP then they would still be up and running. Also maintenance would all be at one point in the network and I think he's got a valid point there. As for DNS settings I'd prefer not to hard code into the server or terminals but use the DNS settings as uploaded automatically to the router by the ISP to keep it simple for maintenance i.e let the DNS first point be the server, which then passes the request to the router, which in turn passes it onto the ISP's DNS servers - if I can of course. Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Cushing Sent: 02 August 2007 10:05 To: profox@leafe.com Subject: Re: [NF] Win 2K Networking Question Dave Crozier wrote: > To All, > I'm setting up a small network with an ADSL Modem/Router (IP address > 192.168.0.2), 1 x Win 2K Server (IP address 192.168.0.1) running active > Directory and a number of Win 2K clients, each client using DHCP from the > Server to get an IP address in the range 192.168.0.100 to 192.168.0.150. > > In any previous networks I've always used the ROUTER to assign dynamic IP > addresses to the clients with the server still having a fixed address with > no problems whatsoever but I can't seem to work out the best/easiest way to > configure the client machines with regards to Gateways/DNS Server etc when > using the Server as a DHCP source. > > Using my preferred method of DHCP on the router means that I can leave the > "obtain IP Address automatically" setting along with forgetting about the > Default Gateway and DNS Server settings on the clients but this situation is > different and I'm just a little stumped at present. > > What would your suggestions be for settings of Gateway, DNS > Primary/secondary on the server and workstations if I HAVE to use DHCP on > the server as opposed to on the router? > > I'm sure I'm being really stupid here in missing something out as the DHCP > from the server is fine in that I can see the whole network from the > workstations but cannot see the Internet unless I put in a DNS setting of > 192.168.0.2 and/or a gateway of 192.168.0.2 which then seems to screw up the > local networking. Even worse some workstations seem to work intermittently > with one of the previous Gateway/DNS settings. > > Hi Dave, I'm no expert in this area (arse covered!), but there should not be any problem getting the network addresses from the server. We do that now using W2K3 and used to use it with NT. You can also set the server to be the DNS source but I think you need another piece of software to then forward the requests to the router. We used to use a program called VSOCKS which is basically a proxy server. What you can also do for the DNS is to set them to the external setting recommeded by the ISP. This is what I do at home with 4 machines. They all have DNS or 194.168.4.100 etc. This works fine. As for the default gateway, AFAIK that should always be the router. That is the settings we use here and at home. HTH Peter [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
