possible routing issue?

I've set up an new network with 20 XP client machines and one Windows
2003 server standard edition with AD. On the server I installed DNS,
and DHCP. I also have a 2wire DSL router for internet access.

On the client machines if I add a gateway pointing to the DSL router or

the server then any application access or network access takes around
30 seconds before
something happens. If I take out the gateway then everyhting run at
top speed, but the end users do not have internet access. Is this a
possible routing issue or something else?


Each machine is running CA antivirus scanner.


Some things I've tried..
1. Made the router the DHCP server and stopped it on the MS server.
Did not make a difference
2. Added the MS server and the router IP address as the primary and
secondary DNS servers.
3. Took out the gateway and added a static route on each machine.


These were all set back like they were as they on had the same result.


Thanks
tom

Not sure what a "2wire DSL router" is, but assuming all machines are
directly or through a switch connected to the router:

1. All machines including the DC should point only to the DC's IP for DNS.

2. All machines should use the router's LAN IP as a default gateway.

3. On the DC open the DNS management console; right click the server and
select Properties. Click the Forwarders tab; check the box to enable
forwarders; add the IP address of your ISP's DNS server.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"tawright915" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> I've set up an new network with 20 XP client machines and one Windows
> 2003 server standard edition with AD. On the server I installed DNS,
> and DHCP. I also have a 2wire DSL router for internet access.
>
> On the client machines if I add a gateway pointing to the DSL router or
>
> the server then any application access or network access takes around
> 30 seconds before
> something happens. If I take out the gateway then everyhting run at
> top speed, but the end users do not have internet access. Is this a
> possible routing issue or something else?
>
>
> Each machine is running CA antivirus scanner.
>
>
> Some things I've tried..
> 1. Made the router the DHCP server and stopped it on the MS server.
> Did not make a difference
> 2. Added the MS server and the router IP address as the primary and
> secondary DNS servers.
> 3. Took out the gateway and added a static route on each machine.
>
>
> These were all set back like they were as they on had the same result.
>
>
> Thanks
> tom
>

What is the IP configuration on the DSL Router?
Do you have a default gateway setup on it?
You must disable DNS and assign the DSL Router a static IP. Make sure that
the mask is the same as your network range.

Regards

"tawright915" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> I've set up an new network with 20 XP client machines and one Windows
> 2003 server standard edition with AD. On the server I installed DNS,
> and DHCP. I also have a 2wire DSL router for internet access.
>
> On the client machines if I add a gateway pointing to the DSL router or
>
> the server then any application access or network access takes around
> 30 seconds before
> something happens. If I take out the gateway then everyhting run at
> top speed, but the end users do not have internet access. Is this a
> possible routing issue or something else?
>
>
> Each machine is running CA antivirus scanner.
>
>
> Some things I've tried..
> 1. Made the router the DHCP server and stopped it on the MS server.
> Did not make a difference
> 2. Added the MS server and the router IP address as the primary and
> secondary DNS servers.
> 3. Took out the gateway and added a static route on each machine.
>
>
> These were all set back like they were as they on had the same result.
>
>
> Thanks
> tom
>

Thanks for replying back so quickly. Yes the 2Wire is a DSL
modem/router connected to a switch along with all other PC's and the
one DC. I currently have all the PC's and DC pointing to the DC for
DNS with the secodnary pointing to the router. Should I take out the
routers ip address from the secondary DNS slot?

I have not added the IP address of my ISP's DNS server to the DNS
server on my DC. I'll try that tonight and see what happens.

what do you mean. I've given it the ip address of 192.168.0.254 to the
router with a subnet mask of 255.255.255.0 There is no spot for me to
set a gateway on the router. The router has a statice IP address and
is not assigned one from DHCP.

Thanks
Tom

If you configure the router as secondary DNS, then you may be able to retain
Internet name resolution even if the server goes down. However, the risk is
that a machine may for various reasons be temporalily unable to reach the
server even though the server is functioning fine. If this happens the
client may switch to the secondary DNS and thereafter be unable to access
domain resources which it would be able to access if only the DC were
specified for DNS.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"tawright915" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Thanks for replying back so quickly. Yes the 2Wire is a DSL
> modem/router connected to a switch along with all other PC's and the
> one DC. I currently have all the PC's and DC pointing to the DC for
> DNS with the secodnary pointing to the router. Should I take out the
> routers ip address from the secondary DNS slot?
>
> I have not added the IP address of my ISP's DNS server to the DNS
> server on my DC. I'll try that tonight and see what happens.
>

If by only giving the DC's ip address for DNS it will do all the name
resolution right? Doesn't the order of the DNS server listing make a
difference. For instance I have the DC as the primary DNS and the
router as the secondary. shuldn't it go to the server first then to
the router for resolution.

Also how come this would effect, applications such as going to a DOS
prompt, or clicking on my computer? This doesn't have anything to do
with it checking for permission first does it. If so then I could see
the DNS issue if it cannot find the server in a timely fashion.

Also do I need to clear out the DNS cache on the client machines?

Thanks again
Tom

If by only giving the DC's ip address for DNS it will do all the name
resolution right?

Well, it will resolve names for all the zones it hosts. For all other zones
it will forward to your ISP's DNS server - this is why you configure
forwarders.

Doesn't the order of the DNS server listing make a
difference.

Yes, the DC's IP must be primary.

For instance I have the DC as the primary DNS and the
router as the secondary. shuldn't it go to the server first then to
the router for resolution.

No, this is not how DNS works. If the client gets no response from the
primary DNS server, it will query the secondary DNS server. If instead the
client gets a host not found response from the primary server that = 'a
response' and it will not query the secondary server.


Also how come this would effect, applications such as going to a DOS
prompt, or clicking on my computer? This doesn't have anything to do
with it checking for permission first does it. If so then I could see
the DNS issue if it cannot find the server in a timely fashion.

It may or may not be related to misconfigured DNS - eg. the machine may be
trying and failing to register in DNS, authenticate to the server, etc.

Also do I need to clear out the DNS cache on the client machines?

If you are changing DNS settings, this is a good idea - run ipconfig
/flushdns

Also, on the server check Event Viewer System and DNS for errors. If you
see Netlogon or failure to register records errors, try restarting the
Netlogon service:

net stop netlogon
net start netlogon

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"tawright915" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> If by only giving the DC's ip address for DNS it will do all the name
> resolution right? Doesn't the order of the DNS server listing make a
> difference. For instance I have the DC as the primary DNS and the
> router as the secondary. shuldn't it go to the server first then to
> the router for resolution.
>
> Also how come this would effect, applications such as going to a DOS
> prompt, or clicking on my computer? This doesn't have anything to do
> with it checking for permission first does it. If so then I could see
> the DNS issue if it cannot find the server in a timely fashion.
>
> Also do I need to clear out the DNS cache on the client machines?
>
> Thanks again
> Tom
>