In article <(E-Mail Removed)>, "Fred Marshall"
<fmarshallx@remove_the_x.acm.org> wrote:
>I just configured a small LAN and had a heck of a time because one of the XP
>computers wouldn't ping it's own IP address. This is a LAN using a Linksys
>router. Internet access was always solid but the connectivity over the LAN
>was problematic.
>
>So, I'd check the XP machine by pinging itself.
>127.0.0.1 worked
>192.168.2.xxx did not work - ever.
>
>After doing all the normal stack repairs, etc. the ping still didn't work.
>But the workgroup finally came alive.
>
>Any insights?
>
>Thanks,
>
>Fred
When a computer can't ping its own IP address,the problem is probably
caused by a firewall program (Norton, McAfee, PC-cillin, ZoneAlarm,
etc) that's incorrectly installed or incorrectly configured.
If you've installed a firewall program, make sure to disable XP's
built-in Windows Firewall. Running both is likely to cause problems.
To see if a firewall program is causing the problem, enable the
Windows Firewall, then uninstall (don't just disable) the firewall
program. Some firewall programs don't uninstall cleanly, so go to
Start | Run | Msconfig | Startup and disable any firewall remnants.
Then reboot and try the ping again.
--
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://mvp.support.microsoft.com