dns error

R

rosie

I have windows 2000 professional & comcast cable. I can't
connect to the internet I keep getting this error message
anyone please help me.

res://c:\WINNT\system32\shdoclc.dll/dnserror.htm-
MicrosoftInternetExplorer
 
H

Herb Martin

Can you "ping" the Internet, say www.Yahoo.com?

(Open a command prompt and leave it open...)

Ping www.yahoo.akadns.net

Ping 216.109.117.204

The second is the same place but skips the DNS resolution.
If the first fails and the second works you machine isn't properly
configured with a DNS server address (in NIC properties)
In that case output following to a text file and report it here:

ipconfig /all > ip.txt

IF the second one fails, try the following and report the result:

tracert 216.109.117.204

If you have some kind of firewall you can test DNS buy using
both http://www.yahoo.akadns.net and http://216.109.117.204
in Internet Explorer (again the latter skips DNS.)

[Firewalls commonly block the protocol used by TraceRt and Ping.]
 
R

rosie

-----Original Message-----
Can you "ping" the Internet, say www.Yahoo.com?

(Open a command prompt and leave it open...)

Ping www.yahoo.akadns.net

Ping 216.109.117.204

The second is the same place but skips the DNS resolution.
If the first fails and the second works you machine isn't properly
configured with a DNS server address (in NIC properties)
In that case output following to a text file and report it here:

ipconfig /all > ip.txt

IF the second one fails, try the following and report the result:

tracert 216.109.117.204

If you have some kind of firewall you can test DNS buy using
both http://www.yahoo.akadns.net and http://216.109.117.204
in Internet Explorer (again the latter skips DNS.)

[Firewalls commonly block the protocol used by TraceRt and Ping.]

--
Herb Martin
I have windows 2000 professional & comcast cable. I can't
connect to the internet I keep getting this error message
anyone please help me.

res://c:\WINNT\system32\shdoclc.dll/dnserror.htm-
MicrosoftInternetExplorer
I can't get on line at all. I came up with so many error
codes. One of them says it's necessary to maintain system
stability 0x000004c7.My DHCP Server sent a DHCPNACK
message I don't know what that is. I'm just beside myself.
 
G

Guest

Herb,
I took the firewall off & was able to ping. Results:
c:\>ping 216.109.117.204
Pinging 216.109.117.204 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 216.109.117.204:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = Oms, Maximum = Oms, Average = Oms

C:\>
c:\>ipconfig /all > ip.txt

C:\>tracert 216.109.117.204

Tracing route to 216.109.117.204 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
this repeats down to #30

Trace complete

C:\ping www.yahoo.akadns.net

Pinging www.yahoo.akadns.net [216.109.118.72] with 32
bytes of data:

Reply from 216.109.118.72: bytes=32 time=30ms TTL=50
Reply from 216.109.118.72: bytes=32 time=20ms TTL=50
Reply from 216.109.118.72: bytes-32 time=20ms TTL=50
Reply from 216.109.118.72: bytes=32 time=10ms TTL=50

Ping statistics for 216.109.118.72:
Packets: Sent = 4, Received =- 4, Lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 30ms, Average = 20ms
C:\>
Comcast has been to my house twice. each time they insert
a floppy disc & remove something. it works to connect
maybe twice then i get the same dns error. I asked comcast
if I can copy disc he said no it's their own special
program & he's not sure what it is. I'm completely at a
loss. Anyone help please!!
-----Original Message-----
Can you "ping" the Internet, say www.Yahoo.com?

(Open a command prompt and leave it open...)

Ping www.yahoo.akadns.net

Ping 216.109.117.204

The second is the same place but skips the DNS resolution.
If the first fails and the second works you machine isn't properly
configured with a DNS server address (in NIC properties)
In that case output following to a text file and report it here:

ipconfig /all > ip.txt

IF the second one fails, try the following and report the result:

tracert 216.109.117.204

If you have some kind of firewall you can test DNS buy using
both http://www.yahoo.akadns.net and http://216.109.117.204
in Internet Explorer (again the latter skips DNS.)

[Firewalls commonly block the protocol used by TraceRt and Ping.]

--
Herb Martin
I have windows 2000 professional & comcast cable. I can't
connect to the internet I keep getting this error message
anyone please help me.

res://c:\WINNT\system32\shdoclc.dll/dnserror.htm-
MicrosoftInternetExplorer


.
 
H

Herb Martin

I took the firewall off & was able to ping. Results:
c:\>ping 216.109.117.204
Pinging 216.109.117.204 with 32 bytes of data:
Request timed out.

I would disagree - ping failed.
So we know we have something WORSE than (or in additon to)
a DNS problem. Either routing is failing or ICMP is blocked, but
since you took down the firewall the likely culprit is routing.

Consider though that the ping (ICMP) might be block later in
the route (e.g., at the ISP) -- this is the reason that when ping
fails we switch to Tracert to determine HOW FAR and through
WHICH ROUTERS the traffic is suffessful.
Tracing route to 216.109.117.204 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.

So you have an IMMEDIATE routing failure -- every machine
"routes" for itself even if it isn't a router. This implies that either
the machine is misconfigure or the FIRST router is failing.
C:\ping www.yahoo.akadns.net
Pinging www.yahoo.akadns.net [216.109.118.72] with 32
bytes of data:

Reply from 216.109.118.72: bytes=32 time=30ms TTL=50

The above should not happen, at least no for a variety of sites.
You failed to ping 216.109.117.204 by address and succeeded
with a DIFFERENT site by name -- you really should consistently
test the SAME IP (by name and address.)

Remember: ALL IP traffic ALWAYS travels by IP -- DNS names
are just a courtesy for humans that must first be resolved BEFORE
the actual message is sent.

Comcast has been to my house twice. each time they insert
a floppy disc & remove something. it works to connect
maybe twice then i get the same dns error. I asked comcast
if I can copy disc he said no it's their own special
program & he's not sure what it is. I'm completely at a
loss. Anyone help please!!

Go back and test with teh SAME IPs (as your successes)
using mainly Ping and Tracert.

You are going to have to learn IP troubleshooting but it sounds
like Comcast has routing or config problems.

You saved the IPConfig but didn't send it.
 
R

rosie

c:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :trnsv01.nj.comcast.net
IP Address............: 68.45.101.57
Subnet Mask...........: 255.255.255.0
Default Gateway.........: 68.45.101.1

c:\>ipconfig/all

Windows 2000 IP Configuration

Host Name............: roe
Primary DNS Suffix.......:
Node Type............: Broadcast
IP Routing Enabled........: No
Wins Proxy Enabled........: No
DNS Suffix Search List......: trnrsv01.nj.comcast.net

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix.: trnrsv01.nj.comcast.net
Description...........: SiS 900 PCI Fast Ethernet Adapter
Physical Address.........: 00-0A-E6-P6-63-5F
DHCP Enabled...........: Yes
Autoconfiguration Enabled....: Yes
IP Address............: 68.45.101.57
Subnet Mask...........: 255.255.255.0
Default Gateway.........: 68.45.101.1
DHCP Server...........: 172.30.118.34
DNS Servers...........: 68.46.144.6
68.46.144.5
Lease Obtained..........: Sunday, March 14, 2004 2:45:02 AM
Lease Expires..........: Sunday, March 21, 2004 2:45:02 AM

c:\>

herb this is how my screen looks. Is this really bad?
-----Original Message-----
I took the firewall off & was able to ping. Results:
c:\>ping 216.109.117.204
Pinging 216.109.117.204 with 32 bytes of data:
Request timed out.

I would disagree - ping failed.
So we know we have something WORSE than (or in additon to)
a DNS problem. Either routing is failing or ICMP is blocked, but
since you took down the firewall the likely culprit is routing.

Consider though that the ping (ICMP) might be block later in
the route (e.g., at the ISP) -- this is the reason that when ping
fails we switch to Tracert to determine HOW FAR and through
WHICH ROUTERS the traffic is suffessful.
Tracing route to 216.109.117.204 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.

So you have an IMMEDIATE routing failure -- every machine
"routes" for itself even if it isn't a router. This implies that either
the machine is misconfigure or the FIRST router is failing.
C:\ping www.yahoo.akadns.net
Pinging www.yahoo.akadns.net [216.109.118.72] with 32
bytes of data:

Reply from 216.109.118.72: bytes=32 time=30ms TTL=50

The above should not happen, at least no for a variety of sites.
You failed to ping 216.109.117.204 by address and succeeded
with a DIFFERENT site by name -- you really should consistently
test the SAME IP (by name and address.)

Remember: ALL IP traffic ALWAYS travels by IP -- DNS names
are just a courtesy for humans that must first be resolved BEFORE
the actual message is sent.

Comcast has been to my house twice. each time they insert
a floppy disc & remove something. it works to connect
maybe twice then i get the same dns error. I asked comcast
if I can copy disc he said no it's their own special
program & he's not sure what it is. I'm completely at a
loss. Anyone help please!!

Go back and test with teh SAME IPs (as your successes)
using mainly Ping and Tracert.

You are going to have to learn IP troubleshooting but it sounds
like Comcast has routing or config problems.

You saved the IPConfig but didn't send it.


.
 
H

Herb Martin

rosie said:
herb this is how my screen looks. Is this really bad?

No, it's not necessary bad at all -- let's take a look....
c:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :trnsv01.nj.comcast.net
IP Address............: 68.45.101.57
Subnet Mask...........: 255.255.255.0
Default Gateway.........: 68.45.101.1

Ok, your default gateway and machine are correctly
on the same subnet. Get in the habit of finding that
value (here it is 68.45.101.1 which might change some
other day) and PING it to see if it responds.
c:\>ipconfig/all

DHCP Enabled...........: Yes
Autoconfiguration Enabled....: Yes
IP Address............: 68.45.101.57
Subnet Mask...........: 255.255.255.0
Default Gateway.........: 68.45.101.1
DHCP Server...........: 172.30.118.34
DNS Servers...........: 68.46.144.6
68.46.144.5

We can ping or tracert to these DNS servers to see if
routing is (likely) working.

tracert 68.46.144.6
tracert 68.46.144.5

And we can NSLookup against EACH of them to see
if both respond

nslookup www.LearnQuick.Com 68.46.144.6
nslookup www.LearnQuick.Com 68.46.144.5

It looks ok. Note you almost certainly do NOT
have a DNS problem (we can double check) but
rather a ISP hardware or routing problem.
[/QUOTE]
 
R

rosie

Windows 2000 IP Configuration

Host Name..........: roe
Primary DNS Suffix........:
Node Type..........: Broadcast
IP Routing Enabled..........: No
WINS Proxy Enabled..........: No
DNS Suffix Search List........: trnrsv01.nj.comcast.net

Ethernet adapter Local Area Connection 4:

Connection specific DNS Suffix.....:
trnrsv01.nj.comcast.net
Description.....: SiS900 PCI Fast Ethernet Adapter
Physical Address.....: 00 0A E6 F6 63 5F
DHCP Enabled.....: Yes
Autoconfiguration Enabled.....: Yes
IP Address.....: 68.45.101.57
Subnet Mask.....: 255.255.255.0
Default Gateway.....: 68.45.101.1
DHCP Server.....: 172.30.118.34
DNS Servers.....: 68.46.144.6
68.46.144.5
Lease Obtained.....: Sunday, March 21, 2004 6:27:36 PM
Lease Expires.....: Sunday March 28, 2004 6:27:36 PM

c:\>ping 68.45.101.1

Pinging 68.45.101.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

c:\>tracert 68.45.101.1

Tracing route to 68.45.101.1 over a maximum of 30 hops

1 * * * Request timed out. same line repeated to # 8

9 <10 ms 10 ms 10 ms cdnt02 a
rtr.trnrsv01.nj.comcast.net [68.45.101.1]

Trace complete.

c:\>tracert 68.46.144.6

Tracing route to ns02.trnrsv01.nj.comcast.net [68.46.144.6]
over a maximum of 30 hops:

1 * * * Request timed out.
2 20ms 10 ms 10 ms ge 4 4
ar01.turnersville.nj.nj04.comcast.net [68.
87.51.41]
3 20 ms 10 ms 10 ms pos 7 1
cr01.turnersville.nj.core.comcast.net [6
8.87.19.225]
4 10 ms 20 ms 10 ms pos 3 0
gsr01.trnrsv01.nj.core.comcast.net [68.8
7.18.10]
5 10 ms 10 ms 30 ms 68.46.144.165
6 * 10 ms 10 ms ns02.trnrsv01.nj.comcast.net [ 68.46.144.6]

Trace complete.

c:\>ping 68.45.101.1
ping 68.45.101.1 is not recognized as an internal or
external command,
operable program or batch file.

C:\>ping 68.45.101.1

Pinging 68.45.101.1 with 32 bytes of data:

Reply from 68.45.101.1: bytes 32 time=10ms TTL 64
Reply from 68.45.101.1: bytes 32 time<10ms TTL 64
Reply from 68.45.101.1: bytes 32 time=10ms TTL 64
Reply from 68.45.101.1: bytes 32 time 10ms TTL 64

Ping statistics for 68.45.101.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli seconds:
Minimum = 0ms, Maximum = 10ms, Average = 7ms
C:\>nslookup www.learnquick.com 68.46.144.6
Server: ns02.trnrsv01.nj.comcast.net
Address: 68.46.144.6

Name: www.learnquick.com
Address: 161.58.177.171

C:\>nslookup www.learnquick.com 68.46.144.5
Server: ns01.trnrsv01.nj.comcast.net
Address: 68.46.144.5

Name: www.learnquick.com
Address: 161.58.177.171

C:\>

Herb this is driving me insane. If I take my firewall off
I could get online to my comcast homepage. I don't know
why it keeps doing this. Any more ideas or advice? please
 
H

Herb Martin

Herb this is driving me insane. If I take my firewall off
I could get online to my comcast homepage. I don't know
why it keeps doing this. Any more ideas or advice? please

It is very common for firewalls to block ICMP (ping and tracert);
it is less common to block one but not both. It is also fairly
common for someone to use a firewall and be frustratged by
losing functionality.

A common 'solution' (and wrong) is to just disable the firewall
so completely that there is little point in having it there.
Default Gateway.....: 68.45.101.1
DNS Servers.....: 68.46.144.6
c:\>ping 68.45.101.1
Pinging 68.45.101.1 with 32 bytes of data:
Request timed out.

Unless you default gateway is just configured to ignore
"ping" (uncommon but possible) then this is serious and there
would be little point in continuing the trouble shooting until
this part is solved. (Not the "unless" though)
c:\>tracert 68.45.101.1
Tracing route to 68.45.101.1 over a maximum of 30 hops
1 * * * Request timed out. same line repeated to # 8
9 <10 ms 10 ms 10 ms cdnt02 a
rtr.trnrsv01.nj.comcast.net [68.45.101.1]

Ok, this is very odd. 1) It worked when ping failed 2) it
is ONE HOP away yet didn't work until the 9th hop.

Where did you issue this tracert? ON the gateway or an
internal machine? If on an internal machine if is YOUR
problem perhaps.

This looks like some kind of problem with your ISPs
routing but it so goofy that this is difficult to say for certain.
I would ask the ISP about this at the least.
c:\>tracert 68.46.144.6
Tracing route to ns02.trnrsv01.nj.comcast.net [68.46.144.6]
6 * 10 ms 10 ms ns02.trnrsv01.nj.comcast.net [ 68.46.144.6]

Tracing to the DNS server seems to work fine which is somewhat
surprising given the behavior above.

BTW, this is NOT a DNS issue -- DNS is working fine. It might
be a "ping" (ICMP) only problem except that you were having
trouble to start with.

When you get the problem (original problem you posted) in IE,
you might try using the IP address, e.g.,

http://www.LearnQuick.Com can also be reached at:
http://161.58.177.171 (you can get these numbers using NSLookup.)

Note: SOME websites won't work this way because they are really
"multiple sites" on a single IP-machine but most of the big companies,
e.g., MS, yahoo, dell, etc, probably will and many small companies,
like mine too.

If the DNS name fails and the IP works, then THAT is prima facie
evidence of a DNS resolution problem -- but if you can use NSLookup
that is evidence it is NOT DNS and so implies some sort of weird,
or intermittent routing or (directly) a router problem.
 
A

Ace Fekay [MVP]

In
Herb Martin said:
It is very common for firewalls to block ICMP (ping and tracert);
it is less common to block one but not both. It is also fairly
common for someone to use a firewall and be frustratged by
losing functionality.

A common 'solution' (and wrong) is to just disable the firewall
so completely that there is little point in having it there.
<snip>

Herb, I've seen these issues with Comcast. Provided it's not a personal
firewall causing it, which doesn't seem the case here (or maybe) but need to
disable it to make certain to eliminate that possibilty. I used to deal with
Suburban Cable, the provider in the Philly region before Comcast bought them
out, it was fine, but once Comcast came into play, all kinds of issues came
about. Considering that Rosie has possibly had this as on going problem,
then I would suspect Comcast's routing is not configured correctly, as is
the consensus among my peers in this area, that this happens often. It takes
about 4 - 5 hops just to get out of their network, including NAT'd subnets.
So I wouldn't doubt this is on Comcast's side. Another issue is that there
can be an issue with the actual line coming into the house. Since they have
multiple 2-way amps and nodes before they even hit the pole. I had to have
Comcast come in 3 times since Dec (when I got rid of my T1 and got their
service), complaining about intermittent connectivity, each time saying that
it;s not their fault, until one day, it was so bad, I called them and said,
listen get someone out here right now, it;s happening again and if you
don't, I'm dropping the service, including their TV service, since some
channels that day just wouldn't come in. They had a crew out there in an
hour. They determined it was a line issue, and had to get an infrastructure
maintenance crew to take care of the line and the amps coming in, replacing
whatever and finally they straightened it out.

If this is an ongoing problem, and it's not Rosie's config, then if I were
her, I would complain until I get some sort of resolve. There's always
Verizon DSL. Slower, but no hiccups whatsoever, as per a couple of my
neighbors.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
H

Herb Martin

Herb, I've seen these issues with Comcast. Provided it's not a personal
firewall causing it, which doesn't seem the case here (or maybe) but need to
disable it to make certain to eliminate that possibilty. I used to deal with
Suburban Cable, the provider in the Philly region before Comcast bought
them

In no sense was saying he might not need to temporarily
disable or remove a firewall to troubleshoot or just to
get help from the ISP.

I was referring to people who block themselves with a tight
firewall and instead of learning to use it, just disable it (permantly.)
 
R

rosie

-----Original Message-----
In Herb Martin <[email protected]> posted their thoughts, then I offered mine
<snip>

Herb, I've seen these issues with Comcast. Provided it's not a personal
firewall causing it, which doesn't seem the case here (or maybe) but need to
disable it to make certain to eliminate that possibilty. I used to deal with
Suburban Cable, the provider in the Philly region before Comcast bought them
out, it was fine, but once Comcast came into play, all kinds of issues came
about. Considering that Rosie has possibly had this as on going problem,
then I would suspect Comcast's routing is not configured correctly, as is
the consensus among my peers in this area, that this happens often. It takes
about 4 - 5 hops just to get out of their network, including NAT'd subnets.
So I wouldn't doubt this is on Comcast's side. Another issue is that there
can be an issue with the actual line coming into the house. Since they have
multiple 2-way amps and nodes before they even hit the pole. I had to have
Comcast come in 3 times since Dec (when I got rid of my T1 and got their
service), complaining about intermittent connectivity, each time saying that
it;s not their fault, until one day, it was so bad, I called them and said,
listen get someone out here right now, it;s happening again and if you
don't, I'm dropping the service, including their TV service, since some
channels that day just wouldn't come in. They had a crew out there in an
hour. They determined it was a line issue, and had to get an infrastructure
maintenance crew to take care of the line and the amps coming in, replacing
whatever and finally they straightened it out.

If this is an ongoing problem, and it's not Rosie's config, then if I were
her, I would complain until I get some sort of resolve. There's always
Verizon DSL. Slower, but no hiccups whatsoever, as per a couple of my
neighbors.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================


.
Hi Ace. Comcast didn't charge me for the month of
internet services because I was down so much. They were
out to my home last week & installed a new line
underground. I was able to get online right away but only
for 1 day then I have to disable firewall to get on. I
will call comcast again. They were out twice before
installing the new line & inserted a floppy disc & removed
something. I asked what or if I could copy the disc they
told me no it was cables own program.
 
R

rosie

-----Original Message----- (or maybe) but need
to possibilty. I used to deal
with before Comcast bought
them

In no sense was saying he might not need to temporarily
disable or remove a firewall to troubleshoot or just to
get help from the ISP.

I was referring to people who block themselves with a tight
firewall and instead of learning to use it, just disable it (permantly.)

--
Herb Martin


.
Herb I just want to thank you from the bottom of my
heart. You've been absolutely wonderful with all your
help. Thank you again
 
A

Ace Fekay [MVP]

In
rosie said:
internet services because I was down so much. They were
out to my home last week & installed a new line
underground. I was able to get online right away but only
for 1 day then I have to disable firewall to get on. I
will call comcast again. They were out twice before
installing the new line & inserted a floppy disc & removed
something. I asked what or if I could copy the disc they
told me no it was cables own program.

Hmm, curious what they removed? That is highly strange that they would do
that. I would be very curious before any tech would insert anything on my
machine, let alone run it. I would actually call and ask what exactly they
did, which if nothing else, would be helpful if we were to know so we can
explain it for yourself

So I guess the line down is the partial issue, the firewall would be the
other one, if not configured properly.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top