XP Clients on Windows Server 2008 cannot access Internet

[allanc]

I am configuring (right now) a Windows Server 2008 R2 installation.
The server can access the Internet but the XP PRO sp3 clients cannot.
The clients have joined the domain and I am logged in as a user in the Administrator group.
There are no other operating systems installed on the clients.
DHCP and DNS server roles are running and appear to be error free.

As a result of a lot of research I have connected the router and server directly to the switch.
The server has 2 NICS and one is disabled.
The IPV6 on the NIC has been disabled.
The DHCP and DNS on the router have been disabled.
The IP of the router is 192.168.1.1

Here is the information from Servers NIC:
IP 192.168.1.10
Subnet 255.255.255.0
Gateway 192.168.1.1
DNS Primary 216.254.136.227 (ISPs DNS server)
DNS Secondary 216.254.141.13 (ISPs DNS server)

All clients are using wired connection:
Here is the clients info
using automatic DHCP
the ipconfig is:
IP 192.168.1.106
Subnet 255.255.255.0
Gateway 192.168.1.10
DHCP Server 192.168.1.10
DNS Server 192.168.1.10

If I try a ping on client for www.google.com for example:
I may get something like pinging google (xxx.xxx.xxx.xxx) then 4 timeouts
If I try pinging xxx.xxx.xxx.xxx I get 4 timeouts.
No data is ever returned.
Some sites don't even display the xxx.xxx.xxx.xxx and I only get the 4 timeouts.
All assistance is greatly appreciated.

 

[ljtechservices]

gateway is wrong in dhcp

 

[allanc]

gateway is wrong in dhcp

What should it be?
You mean on the server, correct?

 

[ljtechservices]

What should it be?
You mean on the server, correct?

Your DHCP settings are pointing the clients gateway to the IP address of the server.
Is the server doing any routing?

 

[allanc]

Your DHCP settings are pointing the clients gateway to the IP address of the server.
Is the server doing any routing?

Well, the DHCP and DNS have been disabled because of other reading that I have done.
These roles are installed on the server.
Does that answer your question? Otherwise I am not sure.

 

[ljtechservices]

think about it.
Your DHCP clients are pointing to the server (192.168.1.10) for the default gateway.

why would you do that?

Is the server routing external traffic or is something else?

While your server can act as an internet gateway, you haven't indicated you set it up as such.

so something else must be ROUTING the traffic outside of your 192.168.1.0 subnet. Some kind of default gateway.

You need to figure out how to get the DHCP clients to get that information from the DHCP Server.

i'm not trying to be difficult but it's basic network stuff. Normally all nodes on a subnet use the same gateway. there are some exceptions but it doesn't apply here.

 

[ljtechservices]

BTW you did right by disabling DHCP on the router.

 

[allanc]

think about it.
Your DHCP clients are pointing to the server (192.168.1.10) for the default gateway.

why would you do that?

Is the server routing external traffic or is something else?

While your server can act as an internet gateway, you haven't indicated you set it up as such.

so something else must be ROUTING the traffic outside of your 192.168.1.0 subnet. Some kind of default gateway.

You need to figure out how to get the DHCP clients to get that information from the DHCP Server.

i'm not trying to be difficult but it's basic network stuff. Normally all nodes on a subnet use the same gateway. there are some exceptions but it doesn't apply here.

I know you are not trying to be difficult.
And .... you pointed me in the right direction - I appreciate that.
I had to change the clients to use the router as the gateway.
Then, the client's browsing was unbearably slow.
Some sights worked (slow) and some pages just timed out.
I then changed the DNS on the client to the router and the Internet is moving along nicely.

I must admit that I got confused.
Long day and I had to cobble pieces of information from all over the Internet today that wore me out and confused me.

Thanks so much!

 

[ljtechservices]

I know you are not trying to be difficult.
And .... you pointed me in the right direction - I appreciate that.
I had to change the clients to use the router as the gateway.
Then, the client's browsing was unbearably slow.
Some sights worked (slow) and some pages just timed out.
I then changed the DNS on the client to the router and the Internet is moving along nicely.

I must admit that I got confused.
Long day and I had to cobble pieces of information from all over the Internet today that wore me out and confused me.

Thanks so much!

I knew you would figure it out.

If you are configuring a domain on your Win2k8 server you might want to point the clients back to the server for DNS and then enable DNS forwarding on the Server.
This will allow domain communication to work properly.

This is an option in the DNS settings on the server.
without it the clients may have intermittent times when they cannot find the server.

 

[pceinc]

Something else you should change is if you have DNS running on the server, your primary DNS on the server and workstations should point to the IP address of the server. You can then setup DNS forwarding of alternate DNS servers in the server DNS management console.

Edit: I should have read the post above.