TCP/IP getting unbound from LAN -Win2000 Proff

  • Thread starter Thread starter Subbu
  • Start date Start date
S

Subbu

Hi,
Could anyone help me in the following problem.

I have a NICard installed and I have installed TCP/IP
and it shows all the properties info etc. However, when I
do loopback pinging (ping 127.0.0.1) the request is timed
out.

Then I uninstall TCP/IP and again reinstall TCP/IP, it
works fine. But when I boot again, it does not ping.

Looks as though TCP/IP is getting unbound from LAN.

Is there any way out? Could anyone help me to resolve this
problem?

thanks and regards
subbu
 
Not being able to ping 127.0.0.1 normally indicate hardware problems. Try to
reinstall the drivers for your NIC. If that do not help I suggest you to try
another NIC.

AT
 
Marina
I don't understand your question.

Could you please elaborate.

The network card is fine and first time it responds to
loopback pinging.

But when I reboot, it gets unbound.

Regards

subbu
 
But when I reboot, it gets unbound.
Do you with this say that the bindings for your LAN get unchecked in
Adapters and Bindings?

AT
 
Which operating system we're talking about?
Do you have installed a proxy software as well?
Could you switch it out and give it a try?
biercing
 
Hi Subbu,

Do you have all servicepacks and hotfixes applied to your computer? There
are quite some nasty viruses and worms that can cause all kinds of problems,
like the one you're having.
You should have SP4 and the ms03-039 patch at least.

Marina
 
Hi AT
No, TCP/IP is not getting unchecked. It remains checked.
But when you do loopback pinging it does not work. Then I
have to uninstall TCP/IP from my LAN,restart and then
reinstall again. Now, if I do loopback pinging it works,
till the system is on and not rebooted.

So, its TCP/IP getting unbound from LAN, eventhough in the
properties, it remain checked and showing all its contents.
thanks
subbu
 
As I said before, to not be able to ping 127.0.0.1 indicate a hardware or
driver problem.
Try this! Uninstall your network adapter from your Device Manager. Then
reboot and let your system "find a new device". Hopefully it will assign
another IRQ or I/O adress. If this not help I suggest that you manually
change your adapter to another IRQ.

AT
 
Back
Top