private network and dsl

[m e macon]

private network consists of 1 w2k server that acts as dns and dhcp server.
configured with static address. also are 5 xp pro clients set to get ip
info automatically from server. have recently added a dsl connection and
purchased a Netgear Fr114p firewall. connection will be
dsl---firewall---switch/hub---clients

My question is this. The Firewall performs the nat/dhcp function and
assigns the computers private ip addresses. I am assuming that for all this
to work I will need to disable or unauthorize the current dhcp service on
the w2k server box for all this to work. Any good resources for this ?

What other issues have any of you run up against on this type of set up. My
only concern is how the clients will connect after all is set up. The
server has the static address that is the same as the firewall so the server
will have to have a new static address set up. I am unsure at this time as
to what new and exciting problems this will cause for the client/server
finnace application that is installed on the server. I think that the
clients connect to the server by name ?? but wonder if there will need to be
new installs of the finance app ws on the client machines to point them to
the new server/ip address.

 

[Steven L Umbach]

I would disable the dhcp on the Netgear device and configure your current
dhcp scope to point to the Netgear device as the default gateway which you
can configure to be on the same internal network as your current lan. If
your W2K server is a domain controller you need to take extra care to make
sure that the clients continue to get the right information from dhcp
including that they point ONLY to the domain controller as their preferred
dns server in tcp/ip properties. Your existing W2K dns server can resolve
internet names for the lan clients by using root hints in a default install
as long as the dns server does not have it's own root "." - dot zone OR by
configuring it to forward to your ISP dns servers. See the link below on W2K
dns FAQ. -- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

 

[Michael Johnston [MSFT]]

It would be best to disable the DHCP service on the firewall instead. Use DHCP on the WIndows 2000 server. You'll just need
to change the IP address of the server so that you don't get an IP conflict. The IP change shouldn't cause any problems for the
server. Also, no software re-install is needed.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Guest]

I agree with the last two folks!...Your DSL modem may have nat with dhcp config'd as well. Check with your provider tech support to see...if so, they can walk you through setting the modem in bridge mode & disabling the dhcp. Have fun...shouldn't be difficult.

 

[Lanwench [MVP - Exchange]]

AFAIK nothing will need to change on the DSL router - the Netgear can
happily get a DHCP configured address from it, and NAT to the appropriate
private range.