The TCP/IP stack is corrupt, remove TCP/IP and added it again. Try using fixed
IPs, if that doesn't correct the problem you're going to have to reinstall
unless somebody else has a fix for corrupt TCP/IP stacks. Sorry.

HTH,

Jose



"Tommy Holmes, Jr." wrote:

> Well, I have tried my best to do as Mark instructed and have returned for
> further assistance.  First, I cannot find "reg clean" on this computer;  we
> have "Registry Checker" which merely makes a backup of the registry and
> "Regedit" which accesses the database.  Can't find it in Win98 help either.
>
> Next, when we re-installed the NIC, we limited the installed network
> protocols to TCP/IP and the client to Client for Microsoft Networks just to
> keep things simple.  Confirmed that the TCP/IP configuration settings were
> correct for our Gateway and for our DNS server at the ISP.  Confirmed that
> we automatically were assigned a valid internal TCP/IP address and submask.
> Confirmed that TCP/IP was "bound" to the correct network adapter in the
> configuration.  Confirmed that Computer Name and Workgroup name carried over
> unchanged from the re-install.  However, with TCP/IP alone, we cannot "see"
> or "browse" the other computers on the LAN.  Nor, can we use the HPINP
> Wizard to open communications with the HP printer server/printer or open an
> internet connection using IE or Netscape.  Doesn't that suggest that the
> TCP/IP protocols are installing other than properly?  What in the world
> might one do to address that?

                  Visit our website regularly for FAQs,
               articles, how-to's, tech tips and much more
                          http://freepctech.com