ping loopback with tcp/ip disabled

Windows XP

    Sponsored Links

    Next

  • 1. Whats happening
    When i access the internet, a dialog opens and say that my computer will be turned off in 60 seconds, and then its going down and turn off my computer.... what can i do???
  • 2. Incoming Connetion - What port used?
    Hello, If I am trying to get my Windows XP computer to accept incoming connections using TCP/IP, what ports will I have to open on my router to be able to connect? Thanks! ~~Andy~~
  • 3. Locked up Intel PRO/100 VE
    I have an IBM Thinkpad with an Intel PRO/100 VE LAN adapter. It currently appears to be working properly on a LAN that is configured properly but it will not exchange TCP/IP traffic on the LAN. Please see my post "LAN connect failure after Windows XP re-install" of 6/11/2004 for details on that. On Intel's site there is a note that this adapter may show just these symptoms - apparently operational with no diagnostics but "locked up" - if it is physically installed while power is applied to the connector. Their suggestion was to unpower the machine, remove the adapter, re-power the machine, unpower the machine and then re-install the adapter. This was NOT the situation with my machine - the adapter is built in and has never been touched - but I did remove all power (including the battery) to swap out a hard disk. Before that LAN operation was perfect. Now it is non-operational although the LAN adapter shows "connected" with no sign of problem in XP's Network Connections. Has anyone seen similar behavior? Is there any way to "reset" this adapter without physically removing it?

ping loopback with tcp/ip disabled

Postby d2FsbHlfbGxhbWEx » Sat, 03 Feb 2007 12:12:07 GMT

Pinging the loopback address tests confirms that TCP/IP is running, correct?

Is there any reason that I can still ping the loopback address even though I 
have disabled TCP/IP? Or is my understanding of what pinging the loopback 
address does wrong?

Re: ping loopback with tcp/ip disabled

Postby Steve Winograd [MVP] » Sat, 03 Feb 2007 18:52:31 GMT

In article < XXXX@XXXXX.COM >,



The loopback address is internal to the TCP/IP stack and can be used
even with no installed network adapters.

How did you disable TCP/IP?
-- 
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see.  I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
 http://www.**--****.com/ 

Re: ping loopback with tcp/ip disabled

Postby d2FsbHlfbGxhbWEx » Sun, 04 Feb 2007 11:26:01 GMT







I disabled TCP/IP through the properties of the connection under the 
networking tab. A lab in the Microsoft 272 book instructed me to disable 
TCP/IP by unchecking the box there, which should keep pinging the loopback 
from working. It did not, and my instructor did not have an answer as to why.

Does unckecking the box not actually disable TCP/IP for the connection?

Re: ping loopback with tcp/ip disabled

Postby Steve Winograd [MVP] » Sun, 04 Feb 2007 16:46:19 GMT

In article < XXXX@XXXXX.COM >,



Unchecking the box disables TCP/IP on that network connection, and
only on that network connection.  It has no effect on other network
connections, and it has no effect on the loopback address.

The loopback address isn't associated with any network connection.
It's internal to the TCP/IP stack, and TCP/IP runs even when TCP/IP
isn't bound to any network connections.   To demonstrate that, you can
un-install all network adapters, open a command prompt window, and use
the "route print" command to show the TCP/IP route table.  It will
show:
  
   127.0.0.1  255.0.0.0  127.0.0.1  127.0.0.1  1
-- 
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see.  I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
 http://www.**--****.com/ 

Similar Threads:

1.TCP/IP computer can ping world, world can't ping computer

Hi

I'm having a really strange situation going on with one of my Win2000
computers.

As the subject line states, it can ping and access the world (within
and outside of the LAN), however, no other computer can ping it (ie.
ping 192.168.2.3).

This machine is able to browse the web and ping everywhere, but no
other computer can ping it, which means that my XPPro laptop, which
doesn't have the netbui protocol installed, can't access the shares on
the w2k computer.

This machine is connected to a belkin 4 port router (which acts as the
DHCP server). If I set the machine to use a static IP address, it
can't browse the web at all.

I ran winsockfix.exe on it, which kinda resolved the internet access
problem (as long as the computer uses a dynamic IP address).

Also, I have no firewall running.

I already tried replacing the network card (as instructed in other,
similar, threads).

Next stop seems to be a full reinstall of windows 2000 unless someone
comes up with another clever idea.

Thanks in advance!!!!!

Alex

Here's a dump from ipconfig /a:
Windows 2000 IP Configuration



	Host Name . . . . . . . . . . . . : ws04
	Primary DNS Suffix  . . . . . . . : 
	Node Type . . . . . . . . . . . . : Broadcast

	IP Routing Enabled. . . . . . . . : Yes

	WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Local Area Connection 3:



	Connection-specific DNS Suffix  . : 
	Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For
Complete PC Management NIC (3C905C-TX)
	Physical Address. . . . . . . . . : 00-04-75-C9-4C-CB

	DHCP Enabled. . . . . . . . . . . : Yes

	Autoconfiguration Enabled . . . . : Yes

	IP Address. . . . . . . . . . . . : 192.168.2.3

	Subnet Mask . . . . . . . . . . . : 255.255.255.0

	Default Gateway . . . . . . . . . : 192.168.2.1

	DHCP Server . . . . . . . . . . . : 192.168.2.1

	DNS Servers . . . . . . . . . . . : 192.168.2.1
	Lease Obtained. . . . . . . . . . : Wednesday, December 17, 2003
5:26:49 PM

	Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07
PM

2.Failed TCP/IP Internet Loopback Test Error Code NC315-5W

Hi,

I ran PC Doctor to test the connection on my network adapter (Realtek 
RTL8139/810x Family Fast Ethernet NIC) 

The test failed on the following:

Failed TCP/IP Internal Loopback Test Error Code NC315-5W

Failed Network Communication Test Error Code NC315-1W

If anyone could advise on this it would be much appreciated.

Thanks in advance.

3.Failed TCP/IP Internal Loopback Test & Failed Network Comms Test

Hi,

I ran PC Doctor to test the connection on my network adapter (Realtek 
RTL8139/810x Family Fast Ethernet NIC) 

The test failed on the following:

Failed TCP/IP Internal Loopback Test Error Code NC315-5W

Failed Network Communication Test Error Code NC315-1W

If anyone could advise on this it would be much appreciated.

Thanks in advance.

4.std tcp/ip verses hp std tcp/ip printer port

What is the difference between...
[standard tcp/ip]...
and...
[hp standard tcp/ip]...
when setting up a local printer port?
Any insight will be appreciated.
Thanks, Tracey


5.Microsoft TCP/IP V6 and Internet Protocol (TCP/IP) in network settings

Just noticed that I have both Microsoft TCP/IP V6 and Internet Protocol 
(TCP/IP) showing in network settings.

Is this (a) normal, and (b) likely to cause a conflict ? (XP Pro machines)

Should I remove one or the other?

Jeff



6. Configuring TCP/IP Settings, Enable TCP/IP

7. TCP/IP ping

8. TCP/IP - Can only Ping localhost (127.0.0.1)



Return to Windows XP

 

Who is online

Users browsing this forum: No registered users and 91 guest