Clients log on to domain but can't connect to internet

30 Oct 2006 6:48 AM

DGolds

I set up a DC, DNS, DHCP Server with a lone Windows Server 2003 machine. My
2 client computers (both Windows XP Pro) join and log on to the domain with
no problems, but cannot connect to the internet. The server machine connects
to the internet with no problems. The server machine is a dual boot with the
other partition booting Windows XP Pro. When I boot Windows XP Pro on the
server machine and reconfigure my router accordingly, all 3 machines connect
to the internet.

With the server machine booting Windows Server, I have tried pointing the
clients to the static IP address of the server by going into the properties
of the connection and changing the TCP/IP properties to "Use the following
DNS server address". I still get no internet connection on the clients. Any
suggestions on what else I could try to resolve this would be greatly
appreciated.

Thanks,
-Dave

30 Oct 2006 8:16 AM

Ian

Try http://207.46.250.119 - If you get a well-known website, but can't
reach the same site by its domain-name then you have a DNS problem.

The domain controller will be acting as the DNS server for the clients, so
it's likely the problem is here. Is there a firewall on the server that might
be blocking port 53?

30 Oct 2006 1:28 PM

Malke

DGolds wrote:

Show quoteHide quote

> I set up a DC, DNS, DHCP Server with a lone Windows Server 2003
> machine. My 2 client computers (both Windows XP Pro) join and log on
> to the domain with
> no problems, but cannot connect to the internet. The server machine
> connects
> to the internet with no problems. The server machine is a dual boot
> with the
> other partition booting Windows XP Pro. When I boot Windows XP Pro on
> the server machine and reconfigure my router accordingly, all 3
> machines connect to the internet.
>
> With the server machine booting Windows Server, I have tried pointing
> the clients to the static IP address of the server by going into the
> properties
> of the connection and changing the TCP/IP properties to "Use the
> following
> DNS server address". I still get no internet connection on the
> clients. Any suggestions on what else I could try to resolve this
> would be greatly appreciated.

You've set up DNS incorrectly. The server should only look to itself for
DNS with forward/reverse lookups set for Internet access. The
workstations should only look to the server for DNS.

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

HOW TO: Configure DNS for Internet Access in Windows 2000 -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

DNS and AD FAQs - http://support.microsoft.com/?id=291382

Malke

--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

30 Oct 2006 8:05 PM

DGolds

Thanks,

When I set my router as the DHCP server everything seems to work, whether I
point my clients to the DNS server or not (of course if I turn my server off
or run the other OS, the clients only connect if I don't point to the DNS
server). I'm not sure exactly this is, but it seems to solve the problem.
I'll have to experiment more.

-Dave

Show quoteHide quote

"Malke" wrote:

> DGolds wrote:
>
> > I set up a DC, DNS, DHCP Server with a lone Windows Server 2003
> > machine. My 2 client computers (both Windows XP Pro) join and log on
> > to the domain with
> > no problems, but cannot connect to the internet. The server machine
> > connects
> > to the internet with no problems. The server machine is a dual boot
> > with the
> > other partition booting Windows XP Pro. When I boot Windows XP Pro on
> > the server machine and reconfigure my router accordingly, all 3
> > machines connect to the internet.
> >
> > With the server machine booting Windows Server, I have tried pointing
> > the clients to the static IP address of the server by going into the
> > properties
> > of the connection and changing the TCP/IP properties to "Use the
> > following
> > DNS server address". I still get no internet connection on the
> > clients. Any suggestions on what else I could try to resolve this
> > would be greatly appreciated.
>
> You've set up DNS incorrectly. The server should only look to itself for
> DNS with forward/reverse lookups set for Internet access. The
> workstations should only look to the server for DNS.
>
> How Domain Controllers Are Located in Windows XP -
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
>
> HOW TO: Configure DNS for Internet Access in Windows 2000 -
> http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
>
> DNS and AD FAQs - http://support.microsoft.com/?id=291382
>
> Malke
> --
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"
> MS-MVP Windows - Shell/User
>