Re: ping me comes back 127.0.0.1
From: *Vanguard* (no-email_at_no-spam.invalid)
Date: 02/10/04
- Next message: SteveS: "Installing an atapi zip drive (100 meg)"
- Previous message: Marty: "windows updating"
- In reply to: Peter Kaufman: "Re: ping me comes back 127.0.0.1"
- Next in thread: Peter Kaufman: "Re: ping me comes back 127.0.0.1"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 9 Feb 2004 22:23:39 -0600
"Peter Kaufman" said in news:uinb20p1k9ja9k2dav1hv9pmsle593slkm@4ax.com:
> "Peter Kaufman" said in
> news:9ai920p70n5kdrs0irn60v8t6l4dq5qeb7@4ax.com:
>> 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
>
>> Something else to try:
>> Network Connections applet in Control Panel
>> Right-click the LAN connection, select Repair
>
> 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"?
>
>> 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?
>
> 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?
>
> 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?
>
> 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?
>
> 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
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.
-- ____________________________________________________________ *** Post replies to newsgroup. E-mail is not accepted. *** ____________________________________________________________
- Next message: SteveS: "Installing an atapi zip drive (100 meg)"
- Previous message: Marty: "windows updating"
- In reply to: Peter Kaufman: "Re: ping me comes back 127.0.0.1"
- Next in thread: Peter Kaufman: "Re: ping me comes back 127.0.0.1"
- Messages sorted by: [ date ] [ thread ]