in message
: > Yes, he told me there was a error in the article earlier this morning.
:
: So what is correct? I don't know what to do with my original problem.
: Is there an article that I could look at that is correct and how would
: I know if it was correct or not?
:
: Do I even need a default gateway?
You shouldn't need one on the internal network as that interface doesn't
need to route. The NIC for the internal network, on the server, if
192.168.x.x, does not need a gateway since the other workstations will also
be on that subnet. A gateway is a connection to another network. The DNS,
for this NIC, will point to the internal DNS, which is probably running on
that server, or should be.
The NIC, on the server, for the external network [ISP - Internet], needs to
use the DFG assigned by the ISP. It will also point it's DNS to the ISP's
DNS.
The article actually has at least 2 errors I found. You don't point the
internal NIC to the ISP's DNS and you don't point ANY NIC for WINS to the
ISP since they don't provide NetBIOS naming.
Ok, I found another possible error: Under the heading "Adding Private NAT
Interfaces", #7 appears to be incorrect (notice the subnet mask).
This:
If your LAN is using DHCP, click Automatically assign IP addresses by using
DHCP on the Address Assignment tab. If you are not using DHCP, NAT assigns
TCP/IP addresses in the 192.168.0.0 range with a 255.255.0.0 subnet mask by
default.
Should probably be:
If your LAN is using DHCP, click Automatically assign IP addresses by using
DHCP on the Address Assignment tab. If you are not using DHCP, NAT assigns
TCP/IP addresses in the 192.168.0.0 range with a 255.255.255.0 subnet mask
by default.
All workstations would point their DNS ONLY to the internal DNS. But if you
do not have an internal DNS then they will use the DNS proxy supplied by
NAT. The idea of this article is to allow the server to be a server and a
NAT router, use the one public IP for outbound communications for all
systems and route all other systems through the internal NIC-server-external
NIC.
An easier solution is to install a true NAT router and connect everything
there and ONLY use the internal DNS on the server for all systems, add a
forwarder to the ISP, eliminate the need for a second NIC in the server,
lessen the burden of having all outbound/inbound traffic route through it,
eliminate the need for RRAS and NAT on the server and have more hair when
you're done.
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382