jmorlan MVM 2008-Jun-25 8:08 pm Glad you got it solved and thanks for sharing the solution. · actions · 2008-Jun-25 8:08 pm ·
Forums → Software and A Can Ping B But B Cannot Ping A However, after trying everything else I could think of, I deleted the rule that allowed this trusted range within the McAfee Firewall settings.

I am unable to even ping localhost/ Also, if you want to enable printer and file sharing, for XP open windows explorer (start menu>all programs>accessories>windows explorer). Once I connect my laptops to the router over wifi, I am able to access internet from both of them. his comment is here I'll check tracert and the event log. –Judah Himango Mar 30 '10 at 14:47 add a comment| up vote 1 down vote This pointed me in the right direction.

SSH into many systems with passphrase-less RSA keys Theorems demoted back to conjectures Where is the Abbey of the Albertian Order of St. I ended up un-installing all Norton software (Norton 360 and Symantec Live Update), rebooted and everything worked great. There were conflicting entries for the IP range I use, some Trusted and some Public. can you type cmd in search>then type> ipconfig /all > %userprofile%\desktop\ipdetails.txt This will generate a file called ipdetails.txt.

I'm not a big Vista guy so I'm not exactly sure what's going on here. I guess its the same with other wifi with good-fair signal because when I go to my friends place sometime at weekends it does the same. I initially thought that something may be wrong with my router, but since I am able to do a one way ping, I dont think that is the reason. The computer with the problem is receiving the address

If your friend has other symptoms (such as limited users being unable to logon, or the Event Logging Service failing to start), Windows may have been broken by installing a Windows Please check to see if a third party firewall program installed on the Vista computer and that it is properly configured for the local area network. However I've noticed that the memory I got back has been going down at the same rate as before (see link to thread below). So it seems it's something other than a firewall issue.