ping me comes back 127.0.0.1

  • Thread starter Thread starter Peter Kaufman
  • Start date Start date
P

Peter Kaufman

XP SP1 Pro. Not on domain, and can join a workgroup but cannot browse
it afterwards - even a newly created one.

Pinging my machine by name comes back 127.0.0.1 which doesn't seem
right. I can ping other machines on the LAN by IP but of course not by
name. Tried both DHCP and fixed IP.

Where do I look for the problem?

Thanks,

Peter
 
"Peter Kaufman" said in news:[email protected]:
XP SP1 Pro. Not on domain, and can join a workgroup but cannot browse
it afterwards - even a newly created one.

Pinging my machine by name comes back 127.0.0.1 which doesn't seem
right. I can ping other machines on the LAN by IP but of course not by
name. Tried both DHCP and fixed IP.

Where do I look for the problem?

Thanks,

Peter
Click to expand...

127.0.0.1 *IS* your own computer. That's its internal IP address separate
of anything assigned by a DHCP server or statically assigned for external
interface. It is also known by its name of "localhost" (i.e., localhost =
127.0.01 = your computer).

What host is providing the DCHP service to assign you an IP address? A
Windows host? A DHCP server in a router? A DCHP server in the cable modem?
Is your LAN connectoid's TCP configuration setup to use DHCP, or do you
specify a static IP addresses?

When you say you cannot ping by name, do you mean a hostname, like "elmer",
or an IP name, like www.intel.com? You might not be able to ping hostnames
if you have ICMP disabled in a router or firewall between you and the other
intranet hosts. You won't be able to ping by hostname to Internet hosts;
you'll only be able to ping those using their IP address or IP name.

Computers use IP addresses. They don't understand IP names. IP names are
only for the convenience of humans who are unable to remember IP addresses.
So you need something to cross reference the IP name that you use to the IP
address that the computer will use. That's the DNS server. Where is the
DNS server? Are you running one? Are you using your ISP's DNS server? If
you have a firewall (software or in a router), is it configured correctly,
like permitting UDP packets to pass through port 53?
 
"Peter Kaufman" said in news:[email protected]:

127.0.0.1 *IS* your own computer. That's its internal IP address separate
of anything assigned by a DHCP server or statically assigned for external
interface. It is also known by its name of "localhost" (i.e., localhost =
127.0.01 = your computer).
Click to expand...

I am aware of that . But pinging the computer I am sitting at by its
hostname should show the assigned IP, not 127.0.0.1 - right?
What host is providing the DCHP service to assign you an IP address? A
Windows host? A DHCP server in a router? A DCHP server in the cable modem?
Is your LAN connectoid's TCP configuration setup to use DHCP, or do you
specify a static IP addresses?
Click to expand...

Auto DHCP - Windows XP
When you say you cannot ping by name, do you mean a hostname, like "elmer",
Click to expand...

The hostname of the computer I am sitting at - i.e., Mycomputer
or an IP name, like www.intel.com? You might not be able to ping hostnames
if you have ICMP disabled in a router or firewall between you and the other
intranet hosts. You won't be able to ping by hostname to Internet hosts;
you'll only be able to ping those using their IP address or IP name.
Click to expand...

Nothing to do with Internet. Basically the problem is I cannot browse
any Workgroup I join with this computer, even a new one. I think I
said that already in the first line of my post.
Computers use IP addresses. They don't understand IP names. IP names are
only for the convenience of humans who are unable to remember IP addresses.
So you need something to cross reference the IP name that you use to the IP
address that the computer will use. That's the DNS server. Where is the
DNS server? Are you running one? Are you using your ISP's DNS server? If
you have a firewall (software or in a router), is it configured correctly,
like permitting UDP packets to pass through port 53?
Click to expand...

Again, nothing to do with the internet. I join a workgroup, say
Newgroup, then I cannot browse that workgroup. There is no DNS server.

Thanks,

Peter
 
Peter Kaufman said:
I am aware of that . But pinging the computer I am sitting at by its
hostname should show the assigned IP, not 127.0.0.1 - right?


Auto DHCP - Windows XP


The hostname of the computer I am sitting at - i.e., Mycomputer


Nothing to do with Internet. Basically the problem is I cannot browse
any Workgroup I join with this computer, even a new one. I think I
said that already in the first line of my post.


Again, nothing to do with the internet. I join a workgroup, say
Newgroup, then I cannot browse that workgroup. There is no DNS server.

Thanks,

Peter
Click to expand...


I had a similar problem when setting up a workgroup w/ w2k computers.
I could ping them but wasn't able to connect to them thru My Network
Places or share files/printers.

What I found was that the browser service is apparently set on manual
by default(at least on W2K). I went to Start - Programs -
Administrative Tools - Services - Computer Browser and started the
service and set it to automatic so that it starts with the computer.
That solved my problem, I hope it works for you!

Fred (e-mail address removed)
 
"Fred" said in news:[email protected]:
I had a similar problem when setting up a workgroup w/ w2k computers.
I could ping them but wasn't able to connect to them thru My Network
Places or share files/printers.

What I found was that the browser service is apparently set on manual
by default(at least on W2K). I went to Start - Programs -
Administrative Tools - Services - Computer Browser and started the
service and set it to automatic so that it starts with the computer.
That solved my problem, I hope it works for you!

Fred (e-mail address removed)
Click to expand...

I didn't think of the Computer Browser service. Peter didn't mention he was
running a mixed intranet (i.e., the other hosts are Windows 95/98/NT4). I
had almost forgot about old unroutable NetBEUI. I don't think you need the
Computer Browser service running if your network is just Windows 2000 and XP
hosts. However, I don't remember configuring the Computer Browser service
in my Windows XP install, and it is configured for Automatic startup.

Description of the Microsoft Computer Browser Service
http://support.microsoft.com/?kbid=255205

The NetBEUI Protocol Is Not Available in Windows XP
http://support.microsoft.com/?kbid=306059

You Cannot Access Shared Files and Folders or Browse Computers in the
Workgroup
http://support.microsoft.com/?kbid=188001
 
One thing I could have made clearer in my first post that may narrow
this down - sorry for not mentioning it clearly before.

Once joining the workgroup and rebooting, I cannot even attempt to
browse it - the problem it isn't that I cannot see other computers.
The error message is that I do not have access to the workgroup, so
the window on the network does not even open - the computer is denied
access to the workgroup. If I join an entirely new workgroup (with no
other members) the same thing happens.

I think that because when I ping the host name from the computer it
comes back 127.0.0.1 rather than the actual assigned (either by auto
DHCP or manually) IP either TCP/IP or something relating to the
networking is screwed up, but I am not sure where to investigate
further or how to fix it.

Thanks all,

Peter
 
"Peter Kaufman" said in news:[email protected]:
One thing I could have made clearer in my first post that may narrow
this down - sorry for not mentioning it clearly before.

Once joining the workgroup and rebooting, I cannot even attempt to
browse it - the problem it isn't that I cannot see other computers.
The error message is that I do not have access to the workgroup, so
the window on the network does not even open - the computer is denied
access to the workgroup. If I join an entirely new workgroup (with no
other members) the same thing happens.

I think that because when I ping the host name from the computer it
comes back 127.0.0.1 rather than the actual assigned (either by auto
DHCP or manually) IP either TCP/IP or something relating to the
networking is screwed up, but I am not sure where to investigate
further or how to fix it.

Thanks all,

Peter
Click to expand...

Something else to try:

Network Connections applet in Control Panel
Right-click the LAN connection, select Repair

Under the Properties for the LAN connectoid, presumably TCP/IP protocol is
installed. How about "Client for Microsoft Networks"?

Under the Advanced tab in properties, are you using the XP firewall? Are
you using some other software firewall on that computer? Tried disabling
it?

Are you using a NIC (network interface card) or an onboard network
controller (on the motherboard and provided by the chipset)? If an onboard
controller, have you installed the chipset drivers?

You didn't mention anything about your hardware setup. How many hosts in
the network? How is your computer hooked up? To a hub or switch? Wired or
wireless? Is there a router between you and the other hosts?
 
"Peter Kaufman" said in
One thing I could have made clearer in my first post that may narrow
this down - sorry for not mentioning it clearly before.

Once joining the workgroup and rebooting, I cannot even attempt to
browse it - the problem it isn't that I cannot see other computers.
The error message is that I do not have access to the workgroup, so
the window on the network does not even open - the computer is denied
access to the workgroup. If I join an entirely new workgroup (with no
other members) the same thing happens.

I think that because when I ping the host name from the computer it
comes back 127.0.0.1 rather than the actual assigned (either by auto
DHCP or manually) IP either TCP/IP or something relating to the
networking is screwed up, but I am not sure where to investigate
further or how to fix it.

Thanks all,

Peter
Click to expand...
Something else to try:
Network Connections applet in Control Panel
Right-click the LAN connection, select Repair
Click to expand...

Good idea. I'll try it.
Under the Properties for the LAN connectoid, presumably TCP/IP protocol is installed. How about "Client for Microsoft Networks"?
Click to expand...
Under the Advanced tab in properties, are you using the XP firewall? Are
you using some other software firewall on that computer? Tried disabling it?
Click to expand...

Yeah, I have been thinking about the possibility of other antivirus
firewall - XP is not on for sure.
Are you using a NIC (network interface card) or an onboard network
controller (on the motherboard and provided by the chipset)? If an onboard
controller, have you installed the chipset drivers?
Click to expand...

Naw, that is not it. I can ping other computers by IP. Good idea for
next time, if there is one, though.
You didn't mention anything about your hardware setup. How many hosts in the network?
Click to expand...

I mentioned this several times already. The problem occurs with only
one host (or many hosts). That is what I find so odd. I join a brand
new workgroup but then get an error when trying to browse it!
How is your computer hooked up? To a hub or switch? Wired or wireless?
Is there a router between you and the other hosts?
Click to expand...

Direct into an older hub, but I do have connectivity and the other two
computers on the LAN don't evidence any problems. Not applicable in
this case, but again an excellent tip for other potential cases.

I still wonder about the significance of that ping coming back
127.0.0.1. Any thoughts on that other than a 3rd party firewall?

I'll check the firewall thing and repairing the connection when I am
back there in a few days. It'll be interesting to see what IP I have
after repairing.

Thanks,

Peter
 
"Peter Kaufman" said in news:[email protected]:
"Peter Kaufman" said in



Good idea. I'll try it.



Yeah, I have been thinking about the possibility of other antivirus
firewall - XP is not on for sure.


Naw, that is not it. I can ping other computers by IP. Good idea for
next time, if there is one, though.


I mentioned this several times already. The problem occurs with only
one host (or many hosts). That is what I find so odd. I join a brand
new workgroup but then get an error when trying to browse it!


Direct into an older hub, but I do have connectivity and the other two
computers on the LAN don't evidence any problems. Not applicable in
this case, but again an excellent tip for other potential cases.

I still wonder about the significance of that ping coming back
127.0.0.1. Any thoughts on that other than a 3rd party firewall?

I'll check the firewall thing and repairing the connection when I am
back there in a few days. It'll be interesting to see what IP I have
after repairing.

Thanks,

Peter
Click to expand...

Another thing to try:

- Right-click on your LAN connectoid in Network Connections.
- Select Properties.
- Double-click TCP/IP to look at its properties.
- Click the Advanced button.
- Open the WINS tab panel.
- Check what you have configured for NetBIOS.

Mine is currently configured in the Default setting (which means NetBIOS is
enabled). If you also have this setting or it is disabled, try the Enabled
setting. Back on the General tab panel for TCP/IP properties, are you
automatically configuring DHCP? If using the user-configured alternate
configuration, did you specify a WINS server? Or over under the WINS tab
panel, is a WINS server specified? If so, is it up? If you are using DHCP
to allocate a WINS server then you don't need to configure for a WINS
server.

If you run "nbtstat -c" at a DOS prompt, are any NetBIOS names listed (to
show you did get connects from other hosts)? If you run "nbtstat -n", do
you at least see your hostname? Do you see the workgroup? After using the
IP addresses for the other hosts to ping them, does "arp -a" report their IP
address and MAC (physical) address?

It still might be a firewall problem. I have Norton Internet Security 2003
and when enabled I cannot ping my hostname. If I enter "ping polarbear",
where polarbear is my hostname, it just times out. Same thing if I ping the
IP address assigned to my computer. So apparently my firewall is blocking
ICMP (to prevent pings) even when they originate on that computer (but
probably must first get sent to the external interface of the NIC which when
it comes back then it hits the firewall). It I disable my firewall, I can
ping my hostname or IP address.
 
Back
Top