Are you running Windows XP? Which Service Pack do you have installed? What model router is the system connected to? If the machine is configured to "obtain an IP address automatically", is the one it's receiving correct for the IP network it's on?
One of the commoner causes of lack of Internet connectivity is corruption of the Winsock 2 "Layered Service Provider" chain. Here are two sets of directions for fixing that.
First for SP2 or later:
Click the
Start button, and then click
Run.
The
Run window appears.
Type cmd in the Run window, and then press the key or click OK. The command DOS box appears.
At the prompt, type netsh winsock reset, and then press the "Enter" key. The message Successfully reset the Winsock Catalog appears.
Close the command window and reboot the system.
And for SP1:
Try downloading and running
WinsockXPFix. If that doesn't work, try
lspfix.
If one or the other fixes the problem, or even if they don't, it would be prudent to check the machine for malware using Ad-Aware and Spybot as described in
this article.
I'm running XP with service pack 2, with a dlink wireless router. I did all the task you asked and I still done have a connection. I can see the other computers on the system and access the printer thats shared on the router. Maybe it would be better to reinstall explorer? Would that reset everything?
What error messages do you receive when you try to access a Web site? Let's check to see whether it's the browser that's having name resolution problems, since that's what the symptom sounds like.
If the second one works but the first one doesn't, there's some sort of name resolution problem. To see whether it's just the browser or the system, open a cmd.exe window (Start/Run cmd.exe). In the window that opens, type
Does your system get that result? If it does, but Internet Explorer gets DNS errors, repairing Internet Explorer should fix things. From a cmd.exe window, type each of the following lines:
The error that I recieve when I try to access the internet is"The page cannot be displayed" "Cannot find server or DNS Error.
I typed in the "nslookup dslreports.com" these were my results:
DNS request timed out.
timeout was 2 seconds
*** Can't find server name for address 192.168.0.1: timed out
*** Default servers arent available
Server: inknown
address: 192.168.0.1
DNS request timed out
timeout was 2 seconds
DNS request timed out
timeout was 2 seconds
*** Request to UnKnown timed out
I still have a connection to my server and access to the other computers within the workgroup. I hope this info can give you more insight to my problem.
I hope this info can give you more insight to my problem.
J.Laperle,
It does indeed. Here's the "smoking gun":
Server: unknown address: 192.168.0.1 DNS request timed out timeout was 2 seconds DNS request timed out timeout was 2 seconds *** Request to UnKnown timed out
I suspect that 192.168.0.1 is the IP address of your D-Link wireless router.
It's likely that the router configured to be your LAN's DHCP server. One of the values its DHCP server is providing to clients is the IP address of the "DNS Server". You can verify that 192.168.0.1 is the router's IP address and that it's also the IP address listed as the DNS server by examining the output of
ipconfig /all in a cmd.exe window. Examine the IP addresses listed in the "Default Gateway", "DHCP Server", and "DNS Servers" lines. If they're all the same, and the value listed is 192.168.0.1, then we've confirmed that the router's acting as the DHCP server and is providing a "DNS proxy" service. However, it's not providing the DNS proxy service!
You said the problem began suddenly, and (I suspect!) without any configuration changes having been made. Let's first check that there's still a connection between the router and the Internet. Open a cmd.exe window, and in that window type
tracert -d 209.123.109.175.
You should first see this line:
Tracing route to 209.123.109.175 over a maximum of 30 hops
It should be followed by a series of lines, beginning with one that contains the IP address of your router:
1 11 ms <10 ms <10 ms 192.168.0.1 [...] The final two lines should be:
(n) 200 ms 90 ms 90 ms 209.123.109.175 Trace complete.
Note that the value of "(n)" is determined by the number of "hops" between your router and "dslreports.com", whose IP address we've chosen as the "tracert" target. Also the times listed will depend on your connection speed, and the speed of the connections along the way to dslreports.com.
If that output appears as described, your connection to the Internet is intact, but the "proxy DNS" server in the router is not. If instead, you get a "timed out" message after the first hop, your connection to the Internet has failed.
The next step will be troubleshooting the failed connection. How is your site connected to the Internet? I suspect it's via a cable or DSL modem. There are probably indicators on the modem showing the state of its connection. Are they in the normal state for the device?
If it looks like the Internet connection itself has failed, you should contact your ISP for help. If that's not what the "tracert" data suggests, post back with the results and we'll go from there.
The tracert timed out on all 30 attempts? Hope tis helps us more thx again
J.Laperle,
Even the first hop, the one to the router (192.168.0.1)? Since the router's successfully issuing an IP address (192.168.0.100) to the Precision 360, and the machine can reach other machines on your LAN, this sounds suspiciously like a firewall setting is preventing the P360 from reaching the Internet. Can the other machines on your LAN reach the Internet?
Yes all other pc's currently can access the internet. The pc i'm currently on and communicating to you with now had fast sucessful hops to 209.123.109.175. I have scanned for spyware and have found none.
Windows XP doesn't have a command for uninstalling and reinstalling TCP/IP. It does, however have a command for resetting it.
That command is (from a cmd.exe window)
netsh int ip reset c:\resetlog.txt
That command will reset the TCP/IP networking stack, and place a log of what it did in the file c:\resetlog.txt. The command is described in
this Microsoft article, along with sample log output. You may need to renew the machine's DHCP lease after resetting TCP/IP. That can be done from a cmd.exe window. Type:
ipconfig /release /renew
After that, try the "tracert" again. If it still doesn't result in success, we'll need to do further troubleshooting.
Here's a more general Microsoft article describing
troubleshooting TCP/IP problems with Windows XP. We're at about Step 2 of the manual troubleshooting process. Try working your way through the manual steps listed in that article.
Be sure that there isn't a firewall setting that could be interfering with Internet access from the machine. What that specifically means depends on what firewall software you're using. Do you have Service Pack 2 installed on the machine? Could this problem have begun after an automatic Windows update, or after an update to a third-party firewall?
(edit) Fixed typo causing unwanted "smiley".
(edit 2) I just thought of a way this problem could still be caused by the router. Could there have been an access control entry created in the router that would block the P360's IP address or MAC address from accessing the Internet? Most small routers support such a feature.
I am receiving the error message - Page cannot be displayed - cannot find server or DNS error. I found the fix but do not understand. The fix listed on MS website:
Cause - the certificate services 2.0 root certificate authority certificate is bound to IIS as a server certificate. During installation of Certificate Services 2.0 (which I don't show I downloaded/installed) a root certificate authority certificate is generated for the server. This certificate is used by certificate services only.
Resolution - 1) use server certificate wizard in IIS to remove the current certificate.
My problem is none of the certificates read exactly like the cause above, so I don't know which one I am supposed to delete.
After deletion I am supposed to generate a new request and then when received install it.
Does anyone know about certificates specifically and the cause of the above message.
JimW - I already looked at some of the responses and did winsock and others - nothing worked. I am pretty sure the certificate issue is my problem, I just am not experienced enough to follow these directions.
jwatt
4.4K Posts
0
March 31st, 2005 19:00
Are you running Windows XP? Which Service Pack do you have installed? What model router is the system connected to? If the machine is configured to "obtain an IP address automatically", is the one it's receiving correct for the IP network it's on?
One of the commoner causes of lack of Internet connectivity is corruption of the Winsock 2 "Layered Service Provider" chain. Here are two sets of directions for fixing that.
First for SP2 or later:
Click the Start button, and then click Run.
The Run window appears.
The command DOS box appears.
The message Successfully reset the Winsock Catalog appears.
And for SP1:
Try downloading and running WinsockXPFix. If that doesn't work, try lspfix.
If one or the other fixes the problem, or even if they don't, it would be prudent to check the machine for malware using Ad-Aware and Spybot as described in this article.
Jim
Message Edited by jimw on 03-31-2005 01:08 PM
J.Laperle
7 Posts
0
April 1st, 2005 13:00
jwatt
4.4K Posts
0
April 1st, 2005 16:00
What error messages do you receive when you try to access a Web site? Let's check to see whether it's the browser that's having name resolution problems, since that's what the symptom sounds like.
Here's a link to DSLReports.com using its name, and another one using its IP address.
If the second one works but the first one doesn't, there's some sort of name resolution problem. To see whether it's just the browser or the system, open a cmd.exe window (Start/Run cmd.exe). In the window that opens, type
nslookup dslreports.com
The answer should look like this:
Non-authoritative answer:
Name: dslreports.com
Address: 209.123.109.175
Does your system get that result? If it does, but Internet Explorer gets DNS errors, repairing Internet Explorer should fix things. From a cmd.exe window, type each of the following lines:
regsvr32 Shdocvw.dll
regsvr32 Shell32.dll
regsvr32 Oleaut32.dll
regsvr32 Actxprxy.dll
regsvr32 Mshtml.dll
regsvr32 Urlmon.dll
(edit) Internet Explorer should be closed while you're entering those commands.
Post back with the results.
Jim
Message Edited by jimw on 04-01-2005 10:29 AM
J.Laperle
7 Posts
0
April 4th, 2005 12:00
Jim,
The error that I recieve when I try to access the internet is"The page cannot be displayed" "Cannot find server or DNS Error.
I typed in the "nslookup dslreports.com" these were my results:
DNS request timed out.
timeout was 2 seconds
*** Can't find server name for address 192.168.0.1: timed out
*** Default servers arent available
Server: inknown
address: 192.168.0.1
DNS request timed out
timeout was 2 seconds
DNS request timed out
timeout was 2 seconds
*** Request to UnKnown timed out
I still have a connection to my server and access to the other computers within the workgroup. I hope this info can give you more insight to my problem.
Thanks
J.laperle
jwatt
4.4K Posts
0
April 4th, 2005 15:00
J.Laperle,
It does indeed. Here's the "smoking gun":
Server: unknown
address: 192.168.0.1
DNS request timed out
timeout was 2 seconds
DNS request timed out
timeout was 2 seconds
*** Request to UnKnown timed out
I suspect that 192.168.0.1 is the IP address of your D-Link wireless router.
It's likely that the router configured to be your LAN's DHCP server. One of the values its DHCP server is providing to clients is the IP address of the "DNS Server". You can verify that 192.168.0.1 is the router's IP address and that it's also the IP address listed as the DNS server by examining the output of ipconfig /all in a cmd.exe window. Examine the IP addresses listed in the "Default Gateway", "DHCP Server", and "DNS Servers" lines. If they're all the same, and the value listed is 192.168.0.1, then we've confirmed that the router's acting as the DHCP server and is providing a "DNS proxy" service. However, it's not providing the DNS proxy service!
You said the problem began suddenly, and (I suspect!) without any configuration changes having been made. Let's first check that there's still a connection between the router and the Internet. Open a cmd.exe window, and in that window type
tracert -d 209.123.109.175.
You should first see this line:
Tracing route to 209.123.109.175 over a maximum of 30 hops
It should be followed by a series of lines, beginning with one that contains the IP address of your router:
1 11 ms <10 ms <10 ms 192.168.0.1
[...]
The final two lines should be:
(n) 200 ms 90 ms 90 ms 209.123.109.175
Trace complete.
Note that the value of "(n)" is determined by the number of "hops" between your router and "dslreports.com", whose IP address we've chosen as the "tracert" target. Also the times listed will depend on your connection speed, and the speed of the connections along the way to dslreports.com.
If that output appears as described, your connection to the Internet is intact, but the "proxy DNS" server in the router is not. If instead, you get a "timed out" message after the first hop, your connection to the Internet has failed.
The next step will be troubleshooting the failed connection. How is your site connected to the Internet? I suspect it's via a cable or DSL modem. There are probably indicators on the modem showing the state of its connection. Are they in the normal state for the device?
If it looks like the Internet connection itself has failed, you should contact your ISP for help. If that's not what the "tracert" data suggests, post back with the results and we'll go from there.
Jim
jwatt
4.4K Posts
0
April 4th, 2005 16:00
J.Laperle,
Even the first hop, the one to the router (192.168.0.1)? Since the router's successfully issuing an IP address (192.168.0.100) to the Precision 360, and the machine can reach other machines on your LAN, this sounds suspiciously like a firewall setting is preventing the P360 from reaching the Internet. Can the other machines on your LAN reach the Internet?
Jim
J.Laperle
7 Posts
0
April 4th, 2005 16:00
Thx for the response Jim,
All indicators on the modem and network router are reading normal. When I entered ipconfig /all this is what came up
Host name.... :RESOURCE
Primary Dns Suffix..... :
Node Type........... :Hybrid
IP Routing Enabled ....... : No
WINS Proxy Enabled ...... : No
and just a bit lower it reads as followed but not all detail:
Dhcp Enabled....... : Yes
Autoconfiguration Enabled........ Yes
IP Address ............ 192.168.0.100
Subnet Mask........... 255.255.255.0
Default Gateway .... 192.168.0.1
DHCP Server ....... 192.168.0.1
DNS Servers ....... 192.168.0.1
The tracert timed out on all 30 attempts?
Hope tis helps us more thx again
J.Laperle
J.Laperle
7 Posts
0
April 4th, 2005 16:00
Thx for the response Jim,
All indicators on the modem and network router are reading normal. When I entered ipconfig /all this is what came up
Host name....RESOURCE
Primary
J.Laperle
7 Posts
0
April 4th, 2005 17:00
Jim,
Yes all other pc's currently can access the internet. The pc i'm currently on and communicating to you with now had fast sucessful hops to 209.123.109.175. I have scanned for spyware and have found none.
Thx again!
J.Laperle
jwatt
4.4K Posts
0
April 4th, 2005 17:00
Windows XP doesn't have a command for uninstalling and reinstalling TCP/IP. It does, however have a command for resetting it.
That command is (from a cmd.exe window)
netsh int ip reset c:\resetlog.txt
That command will reset the TCP/IP networking stack, and place a log of what it did in the file c:\resetlog.txt. The command is described in this Microsoft article, along with sample log output. You may need to renew the machine's DHCP lease after resetting TCP/IP. That can be done from a cmd.exe window. Type:
ipconfig /release /renew
After that, try the "tracert" again. If it still doesn't result in success, we'll need to do further troubleshooting.
Here's a more general Microsoft article describing troubleshooting TCP/IP problems with Windows XP. We're at about Step 2 of the manual troubleshooting process. Try working your way through the manual steps listed in that article.
Be sure that there isn't a firewall setting that could be interfering with Internet access from the machine. What that specifically means depends on what firewall software you're using. Do you have Service Pack 2 installed on the machine? Could this problem have begun after an automatic Windows update, or after an update to a third-party firewall?
(edit) Fixed typo causing unwanted "smiley".
(edit 2) I just thought of a way this problem could still be caused by the router. Could there have been an access control entry created in the router that would block the P360's IP address or MAC address from accessing the Internet? Most small routers support such a feature.
Jim
Message Edited by jimw on 04-04-2005 12:16 PM
Message Edited by jimw on 04-05-2005 12:47 PM
momruggles
1 Message
0
September 20th, 2005 01:00
I am receiving the error message - Page cannot be displayed - cannot find server or DNS error. I found the fix but do not understand. The fix listed on MS website:
Cause - the certificate services 2.0 root certificate authority certificate is bound to IIS as a server certificate. During installation of Certificate Services 2.0 (which I don't show I downloaded/installed) a root certificate authority certificate is generated for the server. This certificate is used by certificate services only.
Resolution - 1) use server certificate wizard in IIS to remove the current certificate.
My problem is none of the certificates read exactly like the cause above, so I don't know which one I am supposed to delete.
After deletion I am supposed to generate a new request and then when received install it.
Does anyone know about certificates specifically and the cause of the above message.
JimW - I already looked at some of the responses and did winsock and others - nothing worked. I am pretty sure the certificate issue is my problem, I just am not experienced enough to follow these directions.
I am running Windows XP home edition with SP1.