configure firewall along side local win2000 server.

[bashywash]

I?m attempting to run Smoothwall along side my win 2000 server. The server does NOT host any services (no web, email etc..) Its setup just as a local domain to connected about 6 systems, printer, share files. I have a shared T1 connection. The FW is setup without any problem outside the netword domain. I want my smoothwall to take control of DHCP roll of the local network, and DNS services. My main question would be what needs to be done (configuration) on the 2000 server to keep its purpose of authenticating, printing services, etc.. and have the changes be transparent to the client pc?s.

 

[err]

if it is a domain controller, I don't really see the point to place a firewall in front of your win2k server.

I would rather suggest placing the firewall closer to your Internet connection (if any).

At any rate, if you'd still like to have firewall in front of your win2k DC, you'll have to "poke" a lot of cheese holes in your firewall that includes NETBIOS port 135, 137, 139. I believe also DNS UDP 53 and a whole bunch of other ports. I would do a netstat -a on your DC to see what port it is listening to.

I believe microsoft has also published an article on enabling firewall holes for win2k DC.

 

[bashywash]

Originally posted by: err
if it is a domain controller, I don't really see the point to place a firewall in front of your win2k server.

I would rather suggest placing the firewall closer to your Internet connection (if any).

Ohh no of course my firewall will be placed behind my server, by the main t1 connection.
I just want my smoothwall to act as the dhcp server.

 

[netsysadmin]

If you have a domain setup you will want to keep DNS and DHCP on the domain controller. DNS is the backbone of active directory and will not function without it. Also you DHCP on your DC also does registration for DNS. What reason would you have to move it to the smoothwall box?

John