If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
After uninstalling ZoneAlarm (version 6.5), I could no longer access the web.
Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
Ads |
#2
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
Try running "netsh winsock reset" in a command prompt. If that doesn't
help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#3
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
Try running "netsh winsock reset" in a command prompt. If that doesn't
help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#4
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
Thank you for you fast answer. I'll try both options and report.
Actually, I used the ZA tool for removal and this may have been the problem (I have removed ZA several times manually; it takes a lot of time but I vere got this problem; the only othe time I had a somewhat similar problem was for machine from which i tried to remove Norton... the only way out was to reinstall WinXP ...). Kind regards "GTS" wrote: Try running "netsh winsock reset" in a command prompt. If that doesn't help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#5
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
Thank you for you fast answer. I'll try both options and report.
Actually, I used the ZA tool for removal and this may have been the problem (I have removed ZA several times manually; it takes a lot of time but I vere got this problem; the only othe time I had a somewhat similar problem was for machine from which i tried to remove Norton... the only way out was to reinstall WinXP ...). Kind regards "GTS" wrote: Try running "netsh winsock reset" in a command prompt. If that doesn't help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#6
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
Dear,
I am happy to report that while running "netsh winsock reset" in a command prompt (or using the tool MicrosoftFixit50199.msi available on MS web site and that seems to do the same thing) was unsuccessful, running winsockXP Fix from http://www.spychecker.com/program/winsockxpfix.html was. The computer works fine now. Thank you very mcug for your excellent suggestion. Paul. "Paul (Bornival)" wrote: Thank you for you fast answer. I'll try both options and report. Actually, I used the ZA tool for removal and this may have been the problem (I have removed ZA several times manually; it takes a lot of time but I vere got this problem; the only othe time I had a somewhat similar problem was for machine from which i tried to remove Norton... the only way out was to reinstall WinXP ...). Kind regards "GTS" wrote: Try running "netsh winsock reset" in a command prompt. If that doesn't help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#7
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
Dear,
I am happy to report that while running "netsh winsock reset" in a command prompt (or using the tool MicrosoftFixit50199.msi available on MS web site and that seems to do the same thing) was unsuccessful, running winsockXP Fix from http://www.spychecker.com/program/winsockxpfix.html was. The computer works fine now. Thank you very mcug for your excellent suggestion. Paul. "Paul (Bornival)" wrote: Thank you for you fast answer. I'll try both options and report. Actually, I used the ZA tool for removal and this may have been the problem (I have removed ZA several times manually; it takes a lot of time but I vere got this problem; the only othe time I had a somewhat similar problem was for machine from which i tried to remove Norton... the only way out was to reinstall WinXP ...). Kind regards "GTS" wrote: Try running "netsh winsock reset" in a command prompt. If that doesn't help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#8
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
You're welcome. Thanks for letting us know.
-- "Paul (Bornival)" wrote in message news Dear, I am happy to report that while running "netsh winsock reset" in a command prompt (or using the tool MicrosoftFixit50199.msi available on MS web site and that seems to do the same thing) was unsuccessful, running winsockXP Fix from http://www.spychecker.com/program/winsockxpfix.html was. The computer works fine now. Thank you very mcug for your excellent suggestion. Paul. "Paul (Bornival)" wrote: Thank you for you fast answer. I'll try both options and report. Actually, I used the ZA tool for removal and this may have been the problem (I have removed ZA several times manually; it takes a lot of time but I vere got this problem; the only othe time I had a somewhat similar problem was for machine from which i tried to remove Norton... the only way out was to reinstall WinXP ...). Kind regards "GTS" wrote: Try running "netsh winsock reset" in a command prompt. If that doesn't help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
#9
|
|||
|
|||
pinging a numeric address works but not an URL (alphameric)
You're welcome. Thanks for letting us know.
-- "Paul (Bornival)" wrote in message news Dear, I am happy to report that while running "netsh winsock reset" in a command prompt (or using the tool MicrosoftFixit50199.msi available on MS web site and that seems to do the same thing) was unsuccessful, running winsockXP Fix from http://www.spychecker.com/program/winsockxpfix.html was. The computer works fine now. Thank you very mcug for your excellent suggestion. Paul. "Paul (Bornival)" wrote: Thank you for you fast answer. I'll try both options and report. Actually, I used the ZA tool for removal and this may have been the problem (I have removed ZA several times manually; it takes a lot of time but I vere got this problem; the only othe time I had a somewhat similar problem was for machine from which i tried to remove Norton... the only way out was to reinstall WinXP ...). Kind regards "GTS" wrote: Try running "netsh winsock reset" in a command prompt. If that doesn't help you might also try WinSock XP Fix from http://www.spychecker.com/program/winsockxpfix.html Also, Zone Labs used to have a removal/repair tool to clean up remnants. I haven't looked lately, but it might be worth checking into. -- "Paul (Bornival)" wrote in message ... After uninstalling ZoneAlarm (version 6.5), I could no longer access the web. Suspecting a problem with the TCP/IP connectoins, I have noticed the followings: - pinging an IP numeric address in the local network or in another network works fine (although I got 2 spurious characters between "Pinging" and the IP address when replying - Thus I got "Pinging yö 130.104.xxx.yyy" where yö are the spurious characters [not seen in another compouter]) - pinging an URL (alphameric address) does not work anymore (thus a "ping www.mysite.com" which would normally work gives "Ping request could not find host www.mysite.com... (the address is resolved from another computer)". I checked that the DNS server replies to ping and is, therefore accessible; other computers using the same DNS server work fine) - tracert (to a numeric or an alphameric address) does not work: only one hop and then "no resources" I ran "sfc /scannow" to replace any corrupted Widows file (it ran to completion; I was asked several times to insert the WinXP CD Rom and suppose, thereby, that some files were indeed replaced), but to no avail. Any suggestion (apart from reinstalling Windows entirely ...). Can this be corrected using the Microsoft repair console (and avoiding having to reinstall Windows entirely ...) ? |
Thread Tools | |
Display Modes | |
|
|