Need Help Configuring Win 2K Server

[trilks]

Help out a Windows Server n00b...

I have set up Small Business Server 2000, which includes Win 2k Server, but I am having trouble getting the workstations connected. They cannot seem to use the server for DNS, and thus can't find any webpages. How do I configure the clients? I have tried using all dynamic IP and DNS settings, tried static settings, tried to make the server the default gateway, all to no avail. When I use the network disk created by Win 2K, I get an error saying that the workstation can't find the server. Get the same message when trying to enable the ISA firewall clients.

I am thinking that this is just a DNS configuration problem. But the DNS service is running, and I'm pretty sure I have the lookup zones and forwarding DNS servers set up correctly. Any thoughts/comments/suggestions?

Cheers in advance.

 

[owensdj]

Make sure that every computer has the IP address of the Windows 2000 Server as its DNS server. This includes the server itself. Give the server a static IP address. The workstations can get their IP address from the DHCP service on the server, or they can also have static IP addresses. Either way will work.

You didn't say anything about how Internet access works for your network. Do you have a DSL/cable modem and a NAT router box or are using your Win2K Server as a router(2 NICs)?

 

[trilks]

I have a DSL connection, and the previous P2P network setup had a hardware firewall that provided DHCP and NAT service. Now I am attempting to use the server for routing, and taking the firewall out of the network completely (ISA Server will do the packet filtering).

Thanks for your help

:beer:

 

[owensdj]

trilks, I wouldn't take out the hardware router. I would let it continue to be the Internet gateway for your LAN and provide NAT. Turn off its DHCP server and use the DHCP service provided on Windows 2000 Server. Set the DNS Forwarding in the DNS service on the Win2K Server to forward unknown DNS requests to the IP address of the hardware router. Let the Default Gateway on all machines be the IP address of the router.

This setup has many advantages. The firewall feature in the hardware router will protect the Win2K Server from the security risk you'd be taking if you choose to use the server as your router. Using the hardware router also makes the configuration much easier. Is there a reason why you want to use ISA Server?

 

[Abzstrak]

agreed, ISA isn't a bad firewall, but I'd run it on its own box, we are talking about windows here, and security is historically not its strong suit.

 

[trilks]

That's a good point about the router. I will try your suggestion tomorrow.

I guess I don't really have any reason to run ISA server if I already have a firewall. In fact, it would be easier not to, since its already set up, and has an easier interface than ISA.

Thanks again for your help.

 

[MulLa]

Have you deleted the "." without the quotes in the forward lookup in your DNS?

Shadow07 Taught me this a long while back with I was trying to configure a w2k server.

Good luck.

 

[NogginBoink]

If your server is running DNS, have all your clients point to your server as the DNS server.

Have your DNS server use your ISP's DNS server as a forwarder. It's in the server's settings in the DNS snap-in, I think.

You need a forwarder is all.

 

[stash]

A forwarder is not needed for the clients to be able to browse the net. A properly setup DNS server will have root hints and be able to resolve queries on its own.

You can add forwarders later if you want, but it would be easier to troubleshoot without.

 

[trilks]

Well, all of your advice worked. I am up and running and getting everyone set up on the domain. Thanks for all your help. I'm starting to actually feel like an admin now...

Next stop: Exchange Server setup... :beer:

 

[Saltin]

It's worthwhile noting, that when you enable the ISA firewall client on a machine, you do not need to define a default gateway or any DNS server's in the machines TCP/IP properties.

The gateway is the ISA server, and ISA handles all DNS lookups on behalf of the clients.

 

[MulLa]

Saltin, does that mean provided I have ISA client installed/working, I could stop DHCP giving out DNS server info and still have clients find their way around?

 

[Saltin]

Mula,

Yes it does, assuming the ISA server the clients are cofigured for is capable of resolving the requests.

It also means you don't have to hand out a Default Gateway to them in the lease as well.

To be honest, I do it anyhow (it's an added layer of redundancy). I posted that more to show how desktops with the Firewall client installed behave.

 

[MulLa]

Saltin, Thanks for the info and clearing things up for me.

Sorry to have hijacked your thread trilks.

 

[trilks]

Originally posted by: MulLa
Saltin, Thanks for the info and clearing things up for me.

Sorry to have hijacked your thread trilks.

no worries, MulLa, i'll take all the info i can get.