HI Doug
Thanks for your responses.
The subnet mask is manually set to 255.255.254.0, on the DC. However when I
perform the IPconfig command on any of the clients it shows as
255.255.255.0.
The default gateway is set to the trusted side of the firewall - that device
can be reached without a problem
I can also ping the trusted side of the ADSL modem.
This is a trace I performed to google.com, the results are as follows.
C:\>tracert 216.239.37.99
Tracing route to 216.239.37.99 over a maximum of 30 hops
1 <1 ms 1 ms 1 ms *.*.*.10
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * ^C
C:\>
Clients are being allocated IP address within the *.*.*.101 - 199 range.
Am I missing anything.
Thanks
"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On the domain controllers:
>
> 1. Check subnet mask - easy to make a mistake when manually setting this.
>
> 2. Check default gateway - make sure this is set to the LAN IP of the
> Netscreen device.
>
> 3. Ping the default gateway IP.
>
> 4. If #3 works then the problem is most likely with the Netscreen
settings.
> You can confirm this by running tracert to an external IP - probably the
> result will show that packets stop at the router. Possibly, Netscreen
DHCP
> is leasing *.*.*.7 or 8 to a client machine; however, Netscreen devices
have
> multiple features that could account for this behavior if not properly
> configured.
>
> Doug Sherman
> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "Test" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Could you advise on what I should check or what commands I should run to
> > test my routing.
> >
> > Thanks
> >
> > "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> > news:#7#(E-Mail Removed)...
> > > If you cannot external IP addresses, the problem is with routing not
> DNS.
> > >
> > > Doug Sherman
> > > MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> > >
> > > "test" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > > > Hi All
> > > >
> > > > I have two Windows 2003 servers operating within my LAN, each with
> > static
> > > > IPs (*.*.*.7 -a domain controller and *.*.*.8 -the PDC). The PDC is
> > where
> > > > we have configured the DNS zone, a copy is being replicated onto the
> DC
> > > >
> > > > For the PDC, I have the DNS server set to *.*.*.8 (its own address),
> > while
> > > > for the other DC, I have the PDC's IP. My DHCP service is provided
by
> > my
> > > > Netscreen firewall, and there we have identified the DC's IP as the
> DNS
> > > > server.
> > > >
> > > > My problem is that over the last six months we have had a recurring
> > > > situation where one or both of the machines loses its ability to
surf
> > the
> > > > internet. Investigations show that they are not able to ping
> externally
> > > by
> > > > IP or by name. We have found that the situation is resolved simply
by
> > > > changing the static IP to some other number within the range.
> > > >
> > > > Why should this be happening? We are not making any changes to the
> DNS
> > > > configuration and cannot identify anything which might trigger the
> loss
> > of
> > > > this service.
> > > >
> > > > Thanks
> > > >
> > > >
> > >
> > >
> > > ---
> > > Outgoing mail is certified Virus Free.
> > > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > Version: 6.0.789 / Virus Database: 534 - Release Date: 11-7-2004
> > >
> > >
> >
> >
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.789 / Virus Database: 534 - Release Date: 11-7-2004
>
>
Similar Threads
Linear Mode
