Re: Internet Issues

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: david lazarus (dlazarus_at_volante.com.au)
Date: 09/17/04 

Date: Fri, 17 Sep 2004 14:52:43 +0800

Obviously the server has a static address - otherwise DHCP would have
complained when you set it up. It also goes to suggest that you have
configured the server with PDNS and possibly SDNS - If so what are these
IP's.

If you are running AD on the servers then DNS should already be configured
as AD requires DNS. Thus you can do 2 things. if the clients are not a
member of your Servers domain. Set the DNS address for the DHCP clients to
the same as your server DNS. This should then allow your clients to Browse
the internet.
On the otherhand if your clients are members of the domain you should set
the DNS for the clients to point to the servers IP (as it should already
have the DNS server service started) If this is the case then you may need
to configure forward lookups on your DNS server to point to the ip address
that your server has. As it must be resolving DNS names somehow.

Also one more thing - A lot of ISP's provide DNS resolution for their
customers. If you set your clients to use the IP address of the ISP's server
(assuming there is no firewall that is going to block the requests) You
should find that your clients are accessing the internet.

"D. Young" <DYoung@discussions.microsoft.com> wrote in message
news:E0976306-06FA-4D90-9A91-A21152461317@microsoft.com...
> I've just completed a training Lab for Windows 2000 networking purposes.
> Here's the config...
>
> (1) Windows 2000 Server (SP4) w/ Active Directory
> (3) Windows 2000 Pro (SP4) Clients
> (1) 4-port Linksys router & a 5-port Linksys workgroup switch
> (1) DSL Modem
>
> The problem is, I'm not able to access the internet on the client pcs.
I've
> disable DHCP on the router and set DHCP on the Server. I can access the
> internet on the Server however. My router's local LAN IP is 192.168.1.1.
My
> Server's IP config is IP Addr:192.168.1.10, Subnet:255.255.255.0,
> Gateway:192.168.1.1, Preferred DNS:192.168.1.1. My IP scope starts at
> 192.168.1.15.
>
> I have scope options set on the Server to Router:192.168.1.1, DNS
> Server:192.168.1.10, Host Name:XXX.com. When I 'ipconfig /all' on my
client
> pcs, I'm returned, Client IP: 192.168.1.xx, Subnet:255.255.255.0,
> Gateway:192.168.1.1, DHCP Server:192.168.1.10, DNS Server:192.168.1.10.
>
> Any ideas anyone? Should I configure DNS & how?
>
> Thanks!

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: DNS Problem??
    ... In the DHCP field at the router, ... DNS but it adds the 'public' side DNS automatically. ... >> I am assisting someone install a new 2003 server (I am working remotely ... Clients will not receive an address from the server's DHCP. ...
    (microsoft.public.windows.server.dns)
  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Strange Issues moving from SBS 2000 to Server 2003 R2
    ... one new 2003 server,installed as DC DNS DHCP, all clients moved to new ... We are trying to get away from ISA, but if i unplug the server now it ...
    (microsoft.public.windows.server.networking)
  • Re: Host (A) Records do not appear
    ... I have a Windows Server 2003 Server installed, AD, DNS, and DHCP ... The clients are logging in perfect, ... DHCP has Wins 44/46 and 06/DNS set. ... If you want the clients registered in DNS, you need to configure the clients ...
    (microsoft.public.windows.server.dns)