Bruce L.
May 8th 03, 01:03 PM
Hi Everyone,
Reading through other posts, I came across MS 811259.
This document describes how to replace the winsock and
winsock2 registry keys. Following this procedure
resolved my problem.
Bruce L.
>-----Original Message-----
>Hi,
>
>To make a long story short, I had problems on my PC
after
>installing a product, and after several iterations of
>attempting to repair it from the product CD, got almost
>everything back the way it was, except for hostname
>resolution.
>
>1) nslookup hostname works, and returns a valid IP addr
>2) nslookup IP addr returns the hostname from above
>3) ping IP address works
>4) ftp IP address works
>5) ICS between 2 PCs works fine
>
>The problem:
>ping hostname ALWAYS tries to ping 0.0.0.1, regardless
of
>whether the hostname is valid or not. That is, doing
>ping junk still tries to access 0.0.0.1, and obviously
>times out.
>
>I know little to nothing about DNS, and am looking for
>any little hint to what could cause this.
>
>Thanks in advance,
>Bruce L.
>.
>
Reading through other posts, I came across MS 811259.
This document describes how to replace the winsock and
winsock2 registry keys. Following this procedure
resolved my problem.
Bruce L.
>-----Original Message-----
>Hi,
>
>To make a long story short, I had problems on my PC
after
>installing a product, and after several iterations of
>attempting to repair it from the product CD, got almost
>everything back the way it was, except for hostname
>resolution.
>
>1) nslookup hostname works, and returns a valid IP addr
>2) nslookup IP addr returns the hostname from above
>3) ping IP address works
>4) ftp IP address works
>5) ICS between 2 PCs works fine
>
>The problem:
>ping hostname ALWAYS tries to ping 0.0.0.1, regardless
of
>whether the hostname is valid or not. That is, doing
>ping junk still tries to access 0.0.0.1, and obviously
>times out.
>
>I know little to nothing about DNS, and am looking for
>any little hint to what could cause this.
>
>Thanks in advance,
>Bruce L.
>.
>