Re: AD, DHCP or maybe DNS problem?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

In my expirience:

- ISA 2004 works perfectly with Windows 2003
- RRAS also works perfectly.

I thing you're missing some config step, I found this Article check if it
helps you check it:

NAT in Windows 2003: Setup and Configuration
http://www.windowsnetworking.com/articles_tutorials/NAT_Windows_2003_Setup_Configuration.html

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:246DE6D5-6FA3-4646-A587-D232A81BA978@xxxxxxxxxxxxxxxx
I'm sorry I mis-typed there, if I use the firewall it doens't work. If I
uncheck the box when configuring my RRAS then it works correctly?!? This
option is only available on the public interface.

I just tried to report the issue and was told to send a snail mail letter
to
Redmond. Thats a little discouraging as I'm sure you would know.
Sooooo...
I guess I'll write a letter to them. I can easily replicate on this
system,
although I don't know what is causing it. I'm guessing this product has
gone
through a ton of testing and this issue would have already been resolved?
I
don't know what to do.

Considering I need to lower my firewalls on my clients for file sharing
(which seems weird) the only option I can see is to work with ISA server
which I've heard is a big headache in 2003 server but left with no other
options I don't think I have a choice. I can't leave my network wide
open,
that is for sure.

"Jorge Silva" wrote:

Very strange....

DON'T REMOVE THE FIREWAL.

I already setup several RRAS servers and they work fine, were did you
enable
the Basic Firewal (In the internal Interface or in the Public Interface)?

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:6E45E005-53B4-4674-9196-0198A6449A17@xxxxxxxxxxxxxxxx
Jorge,

It works!! and this has to be a bug!!! When configuring RRAS if I have
the
RRAS firewall enabled I have the problem, If i remove the basic
firewall
when
configuring RRAS it doesn't work.

Why this only effect the two other computers and not my laptop makes no
sense to me, although there has to be a reason. But this has to be a
bug,
if
the firewall doesn't allow certain clients to receive the reply from
the
web
site, dont' you think?

Thanks,

"Jorge Silva" wrote:

Check if you have nay filters enabled on the RRAS server.

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:11E781ED-0DBA-41F7-86C7-63DDD5A9CB17@xxxxxxxxxxxxxxxx
FYI I did ping my Gateway (the external nic on my server) and was
sucessful.
I realized you might need to know that.

"Greg P" wrote:

Yes I am using Remote Access to access the internet. All of your
suggustions
worked (got a responce) and my trace gets out to MSN, but internet
still
doesn't work. 192..168.10.1 is my server 192.168.10.3 is my
desktop
(the
one
I ran the trace on, but can't use the internet on) below are my
pings
and
trace.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\gperrego>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\gperrego>ping 192.168.10.1

Pinging 192.168.10.1 with 32 bytes of data:

Reply from 192.168.10.1: bytes=32 time=101ms TTL=128
Reply from 192.168.10.1: bytes=32 time=174ms TTL=128
Reply from 192.168.10.1: bytes=32 time=1ms TTL=128
Reply from 192.168.10.1: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 174ms, Average = 69ms

C:\Documents and Settings\gperrego>ping 192.168.10.3

Pinging 192.168.10.3 with 32 bytes of data:

Reply from 192.168.10.3: bytes=32 time<1ms TTL=128
Reply from 192.168.10.3: bytes=32 time<1ms TTL=128
Reply from 192.168.10.3: bytes=32 time<1ms TTL=128
Reply from 192.168.10.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.10.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\gperrego>ping 192.168.10.2

Pinging 192.168.10.2 with 32 bytes of data:

Reply from 192.168.10.2: bytes=32 time<1ms TTL=128
Reply from 192.168.10.2: bytes=32 time<1ms TTL=128
Reply from 192.168.10.2: bytes=32 time<1ms TTL=128
Reply from 192.168.10.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.10.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\gperrego>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [207.46.199.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms nugget.sbs.net [192.168.10.1]
2 7 ms 8 ms 8 ms 10.37.160.1
3 8 ms 8 ms 8 ms gig0-2.austtxa-ubr7.austin.rr.com
[24.27.12.81]

4 9 ms 9 ms 7 ms gig2-3.austtxa-rtr1.austin.rr.com
[24.27.12.85]

5 18 ms 10 ms 9 ms srp0-0.austtxrdc-rtr2.austin.rr.com
[24.27.12.34
]
6 9 ms 8 ms 9 ms pos1-0.austtxrdc-rtr4.texas.rr.com
[66.68.1.110]

7 17 ms 18 ms 16 ms son0-0-0.hstqtxl3-rtr1.texas.rr.com
[24.93.33.15
3]
8 18 ms 17 ms 16 ms 4.79.88.21
9 16 ms 16 ms 18 ms ge-2-0-0.mp1.Houston1.Level3.net
[4.68.97.241]
10 172 ms 110 ms 60 ms as-1-0.mp2.Seattle1.Level3.net
[209.247.10.133]

11 61 ms 61 ms 59 ms
ge-2-0-0-52.gar1.Seattle1.Level3.net
[4.68.105.4
1]
12 60 ms 61 ms 62 ms 65.59.235.6
13 94 ms 62 ms 62 ms 207.46.37.225
14 62 ms 61 ms 63 ms pos1-0.tuk-12ix-1b.ntwk.msn.net
[207.46.36.146]

15 60 ms 62 ms 62 ms pos1-0.tke-12ix-1b.ntwk.msn.net
[207.46.155.5]
16 60 ms 60 ms 60 ms po10.tuk-65ns-mcs-1a.ntwk.msn.net
[207.46.224.15
1]
17 * ^C
C:\Documents and Settings\gperrego>

"Jorge Silva" wrote:

The request TimesOut -> normal, the servers in the internet won't
reply
to
ping requets because they are protected by firewalls.

Basic Steps to troubleshoot are:

1. Ping the loopback address to verify that TCP/IP is installed
and
configured correctly on the local computer. To perform this step,
enter
ping
127.0.0.1 at a command prompt.

If the loopback step fails, the IP stack is not responding. This
problem
might be occurring because the TCP drivers are corrupted, the
network
adapter might not be working, or another service might be
interfering
with
IP.



2. Ping the IP address of the local computer to verify that an
address
has
been added correctly. To perform this step, enter ping <IP
address
of
local
host> at a command prompt.



3. Ping the IP address of the default gateway. This step verifies
that
the
default gateway is reachable and that the local host can
communicate
with
another host on the network. To perform this step, enter ping <IP
address of
default gateway> at a command prompt.



Then you can use Tracert which is a route-tracing utility that
allows
you to
track the path of a forwarded packet from router to router for up
to
30
hops. Tracert works by sending ICMP echo requests to an IP
address,
while
incrementing the Time to Live (TTL) field in the IP header,
starting
at
1,
and analyzing the ICMP errors that are returned. Tracert prints
out
an
ordered list of the routers in the path that returned these error
messages.


Type on command prompt:
<tracert www.microsoft.com> press enter


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:01B390CF-90D6-4305-9008-8E34BE2E69E6@xxxxxxxxxxxxxxxx
Jorge,

I reset internet options to no avail. One thing i'm not sure
about
is
when
I ping the internet from any computer on the network the
request
times
out.
Even the server and the laptop that the internet works on.
Otherwise
I'm
totally stumped.

Thanks,
Greg

"Jorge Silva" wrote:

I uninstalled Norton totally from the desktop. If it can't
connect to
the
internet I can't get a virus :)

It looks that your Dns resolution is working well. So the only
explanation
that I can remember at this moment is that there is something
or
some
filter
that prevents you from going to the internet. Check Internet
options
or
any
type of configuration internet related that you migh have in
your
pc.
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:3BDBCBA0-CDBF-4A47-8B91-B77978A81F49@xxxxxxxxxxxxxxxx
Jorge,

Unfortunately I'm in the same spot that I started in, except
we
solved
the
file sharing issue on Laptop 2 by lowering the Norton
firewall.
I
still
can't access the internet on the desktop or laptop 2, even
though


.

Relevant Pages

  • Re: AD, DHCP or maybe DNS problem?
    ... if I use the firewall it doens't work. ... I already setup several RRAS servers and they work fine, ... but can't use the internet on) below are my pings ... Ping statistics for 127.0.0.1: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Help with Window 2003 server routing
    ... Internet ... Ray H wrote: ... > I had already enabled RRAS with the LAN routing radio button ... I can ping both Nic1 and Nic2 from ...
    (microsoft.public.win2000.ras_routing)
  • RE: Cant connect XP home to DSL modem - cant ping
    ... Is the Dlink configured for DHCP? ... > configuring an ip address and giving appropriate gateway settings etc, ... > unable to ping the dlink. ... > on the internet much because dial up is too slow. ...
    (microsoft.public.windowsxp.network_web)
  • Re: One to One NAT problem
    ... I ping to the public IP 221.xxx.xxx.120 but request timeout. ... I have try to reconfig the RRAS again but still fail. ... You cannot ping a private address through the Internet. ...
    (microsoft.public.win2000.ras_routing)
  • Win2000 routing cant be THIS hard???
    ... DSL ServerA ServerB.NIC1 / ServerC ... ServerB has RRAS installed and is set up with NAT, ... Internet is accessible from ... set at ServerA's console, and ping ServerC. ...
    (microsoft.public.win2000.networking)