10 replies
by hotrodgers
by parbo
Check this tecnet article Q191064.
If you do have a client i suggest that you remove all networking components , rboot and reload them and configure tcp/ip
by hotrodgers
by buffalodan
fatal error, unable to read IP configuration would indicate that TCP/IP is not initializing.
First step, open a dos window and attempt to ping the loopback IP address:
Ping 127.0.0.1
this forces windows to ping an IP address internal to yournic card, this ping does not leave your machine...
If this succeeds, then TCP/IP has at least initialized. IF this ping fails, then TCP/IP is corrupted, or improperly configured, and has failed to initialize, warranting removal and re-installation/configuration.
If this ping succeeds, then this indicates that there is a configuration error, involving the aquisition of a valip ip address, if assigning IP addresses manually, look for typos, both in the assigned ip address, and in the assigned default gateway,
If you are obtaining an IP address dynamically, an incorrect subnet mask could prevent you from obtaining a correct ip address on oyur subnet
WinIP config rely's upon a corrctly initialized and configured TCP/IP protocol to function,
is this the only protocol installed on this machine? (curious why you can browse, without being able to read your own IP address...)
Good luck with this...
by hotrodgers
by big ray
by hotrodgers
by oneydpirat
As described previously, you should indeed remove the TCP/IP from the network stack but do not remove only the NIC protocol-remove any other protocols as well. It might also be a good idea, as there may be a larger issue in place, is to remove the entire stack and rebuild it or even simply removing the client along with the protocols.
Hope that helps more than confuses
by hotrodgers
by hotrodgers
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending