There is a lot to be done before you get to DNS forwarding. Exactly what
device do you have at the end of your DSL line? If it is simply a modem, it
won't really do much for you. That is really only suitable to connect a
single PC to the Internet. As I said earlier, using a DC as your Internet
router is a pain. You really need a DSL NAT device (or DSL "router") with a
builtin DSL modem to act as your Internet connection device. These usually
include a number of switch ports
If what you have is a NAT device, you need to disable its DHCP function
and run DHCP from your server for the LAN machines and configure it as
described previously.
When everything is working in AD (ie your client can join the domain and
see shares on the server) you can worry about Internet access. DNS
forwarding is done from the DNS MMC. You use the default setting (all other
domains) and enter the address of a public DNS server (such as the one at
your ISP). When the client needs the IP address of a public URL (such as
www.microsoft.com) it sends the request to the local DNS server (your DC).
The DC forwards the request to the public DNS and forwards the reply to your
LAN client. You can test this from the client by doing an nslookup from a
command prompt. (ie nslookup
www.microsoft.com). If your forwarding is set
up correctly you will get a bunch of IP addresses and alias names.
"frustrated" <(E-Mail Removed)> wrote in message
news:598CAFCE-1EA5-4396-B1C7-(E-Mail Removed)...
> Sorry, I have been working with Server 2003 for 2 weeks now. I disabled
> DHCP
> on my dsl modem and assigned a static IP to my primary nic but I am not
> sure
> what or how to modify in DNS.
> --
> Thanks
> Frustrated
>
>
> "Bill Grant" wrote:
>
>> If the server is a domain controller, forget about using it as a
>> router. It is not worth the pain.
>>
>> Just use one NIC in the server an let the DSL device do the routing.
>> You
>> still have a few problems to overcome. You will need to turn off DHCP on
>> the
>> router so that only your server does DHCP for the clients. You will also
>> need to modify DNS. The client machines must use the local DNS for AD to
>> work, and that will kill access to Internet sites until you modify the
>> local
>> DNS to forward to a public DNS server which can resolve.
>>
>> You need to configure DHCP so that it hands out the DSL device as the
>> default gateway but your server as the DNS address. eg
>>
>> Internet
>> |
>> public IP
>> DSL
>> private IP (say 192.168.0.1)
>> |
>> server DC (static IP say 192.168.0.3 dg 192.168.0.1 DNS
>> 192.168.0.3)
>> |
>> clients (config from DHCP on server)
>> 192.168.0.x dg 192.168.0.1 DNS 192.168.0.3
>>
>> "frustrated" <(E-Mail Removed)> wrote in message
>> news:1835CCD7-DA31-43B2-9C3C-(E-Mail Removed)...
>> >I am using Active Directory and I have been through the scope wizard for
>> > DHCP. In routing and remote access I right clicked the server name and
>> > went
>> > to the IP tab in the properties window; under IP assignment I checked
>> > DHCP
>> > and selected the second adapter at the bottom of the window. Is that
>> > not
>> > right?
>> >
>> >
>> > --
>> > Thanks
>> > Frustrated
>> >
>> >
>> > "Bill Grant" wrote:
>> >
>> >> What exactly are you trying to do? Do you want to share the DSL
>> >> connection to machines plugged into the switch?
>> >>
>> >> Are you planning to run this with Active Directory? If not you can
>> >> setup
>> >> RRAS as a NAT router to give your client Internet access through the
>> >> server.
>> >> Without NAT, you will need to modify the routing on the DSL router
>> >> (and
>> >> configure DHCP on the server or configure the clients manually).
>> >>
>> >> DSL to Internet
>> >> |
>> >> public IP
>> >> RRAS
>> >> static IP (say 192.168.31.1)
>> >> |
>> >> client
>> >> 192.168.31.x dg 192.168.31.1
>> >>
>> >>
>> >> "frustrated" <(E-Mail Removed)> wrote in message
>> >> news:1FC4E57D-8D30-462F-83B4-(E-Mail Removed)...
>> >> >I have a server with 2 nics, dsl is in the first one and the second
>> >> >nic
>> >> >is
>> >> > plugged into an 8 port switch with a desktop computer plugged into
>> >> > the
>> >> > switch
>> >> > as well. DHCP will not issue an IP address to the client computer
>> >> > and
>> >> > the
>> >> > second nic on the server say limited or no connectivity. What to do?
>> >> > --
>> >> > Thanks
>> >> > Frustrated
>> >>
>> >>
>>
>>
Similar Threads
Linear Mode
