Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Can't ping Vista PC


  • Please log in to reply
15 replies to this topic

#1 trx123

trx123

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 08 August 2014 - 03:59 PM

I have spent many hours and read many posts about this problem and finally have some evidence that Windows Firewall is the problem. Here's how I know:

 The only way I can ping the computer is to stop the firewall service and change the service startup from "automatic" to "disable." Then, only after rebooting the computer, I can finally ping it. I can still ping it even after I manually restart the firewall service and turn the firewall on. But if I reset the service startup to "automatic" and reboot the computer I can't ping anymore. Something gets hosed up during automatic startup. Any ideas are greatly appreciated, but keep in mind that I have tried all basic solutions, i.e. setting firewall rules, allowing incoming echo requests, network name, network and file sharing is on, etc.



BC AdBot (Login to Remove)

 


m

#2 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 08 August 2014 - 05:00 PM

Assuming we are not dealing with a corrupt OS which the firewall is intimately involved,  it should be just a matter of proper configuration.  First step is to configure the firewall to trust the local subnet.



#3 ecross

ecross

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:06:26 AM

Posted 09 August 2014 - 12:02 PM

Hi trx123

 

Allowing pings (ICMP echo requests) through the Windows Firewall on the Vista computer should have done trick.

 

What happens when you try to ping the Vista machine? Any errors, if so what? If you haven't already, you could try turning on the Windows Firewall logging and try pinging the Vista machine again. You can view the log file and see if anything is being blocked.

 

To configure the Windows Firewall log, follow these steps:

http://technet.microsoft.com/en-us/library/cc947815(v=ws.10).aspx



#4 trx123

trx123
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 09 August 2014 - 01:00 PM

When pinging the error is "request timed out." Other errors like Error code: 0x80070035 "The network path was not found" or "the computer STEVE-PC cannot be found" are all due to the same thing: the firewall is blocking access.

But I repeat, I can ping the computer and access shared files and printers if I stop the firewall service, set the service startup to "disabled" and reboot the computer. Even then, if I manually restart the service and turn the firewall back on everything is OK.

But if I set the service startup to "automatic" and reboot then the  firewall blocks communications. That should be a big clue, but I don't know what it could be.



#5 trx123

trx123
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 10 August 2014 - 09:34 PM

I enabled the Firewall logging and I can see that the packets are dropped. 

 

2014-08-10 19:25:14 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:15 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:15 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:16 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:16 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:16 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:17 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:17 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:18 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:19 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:20 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:21 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:22 DROP ICMP 2001:0:9d38:90d7:20ae:1863:8688:eff7 2001:0:9d38:6abd:105f:100d:bbfd:ab78 - - 0 - - - - 136 0 - RECEIVE
2014-08-10 19:25:22 DROP ICMP 2001:0:9d38:90d7:20ae:1863:8688:eff7 2001:0:9d38:6abd:105f:100d:bbfd:ab78 - - 0 - - - - 136 0 - RECEIVE
2014-08-10 19:25:23 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:24 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:25 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:40 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:41 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:42 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:25:48 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:25:51 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:25:54 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:25:57 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:00 DROP UDP 192.168.1.104 239.255.255.250 47964 1900 208 - - - - - - - RECEIVE
2014-08-10 19:26:00 DROP UDP 192.168.1.104 239.255.255.250 47964 1900 247 - - - - - - - RECEIVE
2014-08-10 19:26:00 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:03 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:06 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:09 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:12 DROP ICMP 192.168.1.107 192.168.1.100 - - 60 - - - - 8 0 - RECEIVE
2014-08-10 19:26:12 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:14 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:26:15 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:26:15 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:16 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:26:17 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:26:17 DROP ICMP 192.168.1.107 192.168.1.100 - - 60 - - - - 8 0 - RECEIVE
2014-08-10 19:26:17 DROP UDP 2001:0:9d38:6abd:897:12a5:dbb9:8bff 2001:0:9d38:6abd:105f:100d:bbfd:ab78 3540 3540 414 - - - - - - - RECEIVE
2014-08-10 19:26:17 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:26:18 DROP UDP 192.168.1.107 192.168.1.255 137 137 78 - - - - - - - RECEIVE
2014-08-10 19:26:18 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:18 DROP UDP 2001:0:9d38:6abd:897:12a5:dbb9:8bff 2001:0:9d38:6abd:105f:100d:bbfd:ab78 3540 3540 414 - - - - - - - RECEIVE
2014-08-10 19:26:21 DROP UDP 192.168.1.107 239.255.255.250 53327 1900 161 - - - - - - - RECEIVE
2014-08-10 19:26:22 DROP ICMP 192.168.1.107 192.168.1.100 - - 60 - - - - 8 0 - RECEIVE
2014-08-10 19:26:27 DROP ICMP 192.168.1.107 192.168.1.100 - - 60 - - - - 8 0 - RECEIVE
2014-08-10 19:26:33 DROP 2 192.168.1.1 224.0.0.1 - - 28 - - - - - - - RECEIVE
2014-08-10 19:26:33 DROP 2 192.168.1.107 239.255.255.250 - - 32 - - - - - - - RECEIVE
2014-08-10 19:26:33 DROP 2 192.168.1.107 224.0.0.252 - - 32 - - - - - - - RECEIVE
2014-08-10 19:26:34 DROP 2 192.168.1.104 239.255.255.250 - - 32 - - - - - - - RECEIVE
2014-08-10 19:26:43 DROP UDP 192.168.1.107 239.255.255.250 49152 3702 804 - - - - - - - RECEIVE
2014-08-10 19:26:43 DROP UDP 192.168.1.107 239.255.255.250 49152 3702 804 - - - - - - - RECEIVE
 



#6 ecross

ecross

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:06:26 AM

Posted 11 August 2014 - 07:53 AM

Your log file shows that ICMP packets being dropped but also see other packets being dropped too. There are several attempts that UDP on ports 137 being dropped. TCP ports 139 and 445, and UDP ports 137 and 138 are required for file and printer sharing.



#7 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 11 August 2014 - 11:29 AM

trx123 do you not know how to set the firewall to trust your local subnet?



#8 trx123

trx123
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 11 August 2014 - 01:25 PM

Wand3r3r, is this what you mean?  I tried it but it didn't make any difference

 

  1. Control Panel → Network and Intranet → Network and Sharing Center
  2. Bottom left there is a 'See Also' section, click on 'Internet Options'.
  3. Select Local intranet zone on the Security tab then click the Sites button
  4. Click Advanced button
  5. Enter file://[computer name]
  6. Make sure 'Require server verification...' is unticked


#9 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 11 August 2014 - 03:03 PM

Your example above involves internet access/security. You have a LAN not a WAN issue.  You would configure the local windows firewall not internet security.

 

You go here to configure the firewall

 

control panel

all control panel items

windows firewall



#10 trx123

trx123
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 11 August 2014 - 05:11 PM

I have searched your phrase "how to set windows firewall to trust your local subnet" but I can't find and exact answer. Please explain what you mean.

In Windows Firewall Settings, Advanced  tab, "Select the check box for each connection you want Windows Firewall to help protect." The only check box is "Local Area Connection." The box is checked.



#11 ecross

ecross

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:US
  • Local time:06:26 AM

Posted 11 August 2014 - 05:50 PM

The Advanced tab that shows the Local Area Connection just means what network connection Windows Firewall will protect. You'll want to keep that box checked. Under the Exceptions tab is where you can unblock programs and services.

 

http://www.techrepublic.com/article/tap-into-the-vista-firewalls-advanced-configuration-features/



#12 trx123

trx123
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 11 August 2014 - 06:39 PM

I appreciate your help, but as I said in my original post, I already tried all obvious solutions. Exceptions and inbound rules are all OK, I have checked them multiple times. I don't know why you are calling these settings "letting the firewall trust your local subnet." Maybe it's just IT jargon. Disabling the firewall service automatic startup insures that the service does not start when I reboot the computer. In that case, I can ping even after restarting the service manually and turning the firewall on. But I can't ping if I let the service start automatically even if I stop the service manually and turn the firewall off. I thought that should be a big clue as to what's going on.



#13 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 12 August 2014 - 05:22 PM

Simple google search on "configure windows firewall to allow local network" brings up

 

how to enable ping

https://kb.iu.edu/d/aopy

 

search on configure vista firewall to allow local traffic gives us this

http://www.dummies.com/how-to/content/how-to-allow-local-traffic-through-windows-7-or-vi.html

 

Hopefully between the two you will come to understand how to configure the firewall.

 

Web searching is always your informational friend



#14 trx123

trx123
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 12 August 2014 - 07:47 PM

The websites you mentioned are about the most obvious solutions which I verified multiple times. The problem is not the configuration of the firewall. I repeat, If I start the firewall service manually and turn the firewall on (after rebooting with the firewall service disabled) then everything is OK. It is only when I set the firewall service to start automatically that it gets hosed up.



#15 Wand3r3r

Wand3r3r

  • Members
  • 2,027 posts
  • OFFLINE
  •  
  • Local time:04:26 AM

Posted 13 August 2014 - 05:45 PM

You say you verified the configuration but you don't know how to add a subnet to be trusted.  I find these statements conflicting.

 

That aside it would appear the firewall service is corrupted.  Only solution I know of [assuming you are up on all the MS patches] is to do a repair install of Vista.  Don't forget repair is not the same as new.  Your files and programs stay intact.

 

http://www.vistax64.com/tutorials/88236-repair-install-vista.html


Edited by Wand3r3r, 13 August 2014 - 05:45 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users