Re: AD, DHCP or maybe DNS problem?

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 they
are
on
the dame domain as Laptop 1 which can access the internet. With that
being
said I'm not sure if you still think this is a DNS problem?

Well you said that now you have everything working except Internet, and
you also said that you don't have Proxy or any other thing that
prevents/restricts users to access to the internet, so you must have a
DNS
resolution problem.

Do you have Forwarding enabled in the Dns server?

Yes, this is set up with the correct ip addresses.

Test the resolution on the DC - Go to command prompt and type ping
www.microsoft.com - check if returns the Ipaddress of the site
then go to the clients and check if the ping command returns the
Ipaddress
of the site.

All resolve the IP address, all requests time out.

Right click on it and choose properties then you should have the "File
and
Print Sharing for Microsoft Networks Selected"; however you should
disable/deselect this on the Public Interface (Security purposes).

The File and Print Sharing was selected previously. (there wasn't a
Public
Interface option for this nic, there are only 4 options in the
properties
page, Client for MS Networks, Network Lad Balancing, File and Printer
Sharing, and TCP/IP)

Check also if is preventing Internet access or any other access to
server
or Dns, etc. Best practices here are for test DISABLE the Norton
Firewall
and test, in this way you can immediately check if this as relation
with
your current problems.

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


"Jorge Silva" wrote:

In line



What is a multihomed DC?



Is a Domain controller with more than one Nic (Network Interface Card)
card



What do I need to change on my server to mave this work?



Well you said that now you have everything working except Internet,
and
you
also said that you don't have Proxy or any other thing that
prevents/restricts users to access to the internet, so you must have a
DNS
resolution problem.



- Do you have Forwarding enabled in the Dns server? If no go to the
Dns
console -> right click Dns server choose properties -> select
forwarders
tab -> Select All other Domains -> got to the Selected domain's
forwarder
Ipaddress list and place the ISP Dns server address -> click add ->
restart
Dns service.



Test the resolution on the DC - Go to command prompt and type ping
www.microsoft.com - check if returns the Ipaddress of the site, then
go
to
the clients and check if the ping command returns the Ipaddress of the
site.



Are you saying I shouldn't have WINS and DNS on the same computer?



No. What I said was in a Multihomed DC you could have problems with
Wins
and
Dns.


FYI I uninstalled WINS and see the same problem, do I need to
remove
some
records somewhere?



You'll only need WINS if you're using any APP in your network that
needs
NetBIOS resolution or if you have the need to browse over different
subnets
using for example Network Places.



As for configuring the DNS as you said I already had the interfaces
set
to
only use the local Nic.



- Great


As for setting the binding order the internal Nic was at the top of
the
list. How do I check to see if file sharing is only on that NIC?



- Right click on it and choose properties then you should have the
"File
and
Print Sharing for Microsoft Networks Selected"; however you should
disable/deselect this on the Public Interface (Security purposes).


I had lowered the windows firewall but there was a Norton Firewall
that
was
preventing Laptop 2 from Filesharing. That now works. So both the
desktop
and Laptop 2 have the same issues. They get an IP, can perform
Fielsharing
but can't connect to the internet.



Check also if is preventing Internet access or any other access to
server
or
Dns, etc. Best practices here are for test DISABLE the Norton Firewall
and
test, in this way you can immediately check if this as relation with
your
current problems.



--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Greg P" <gsp@xxxxxxxxxxxxxxxxx> wrote in message
news:25530004-70F9-484D-A87A-26A6B823685F@xxxxxxxxxxxxxxxx
Jorge,

What is a multihomed DC? What do I need to change on my server to
mave
this
work? Are you saying I shouldn't have WINS and DNS on the same
computer?
FYI I uninstalled WINS and see the same problem, do I need to
remove
some
records somewhere?

As for configuring the DNS as you said I already had the interfaces
set
to
only use the local nic.

As for setting the binding order the internal nic was at the top of
the
list. How do I check to see if file sharing is only on that NIC?

I had lowered the windows firewall but there was a Norton Firewall
that
was
preventing Laptop 2 from Filesharing. That now works. So both the
desktop
and Laptop 2 have the same issues. They get an IP, can perform
Fielsharing
.

Relevant Pages

  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
  • Re: Non-domain connection problem
    ... You said that you "hard coded the DNS server to a known DNS on the internet: ... Connect to Internet from Internal Network ... NSLOOKUP always looks for the SBS as the default gateway. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2006 Basic Configuration
    ... Why would we point Preferred DNS to itself? ... Configuring the Internal Network Interface ... In the Internet Protocol Properties dialog box, ... Select the Use the following DNS server addresses option. ...
    (microsoft.public.isa.configuration)
  • Re: IE cant connect to any sites
    ... On the General tab in the Temporary Internet Files Folder, ... Click on "LAN Settings" and make sure everything is blank, ... Network settings ... IP address automatically", click on the DNS tab, disable DNS here, click ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
Loading