Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up
-
I'm confused, are you pinging from the server or from the PCs? Assuming you're pinging from the server, if the PC isn't responding, I don't know how that could be the server at all.
-
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
I'm confused, are you pinging from the server or from the PCs? Assuming you're pinging from the server, if the PC isn't responding, I don't know how that could be the server at all.
Let me bring the post back on track...sorry it is all over the map but you should see my day to day workload (and the pressure to software develop too).
Since removing Symantec Endpoint and Migrating to Webroot, our network hasn't been the same with the biggest issue being that I can't ping a handful of workstations (often TO and FROM the domain controller and file server but also my PC)...Also on these PC's that won't ping, I can no longer see C$ shares...and finally, remote COMPUTER MANAGEMENT will no longer work on ANY PC in the domain.
SO let's pick on the PC called Estimating02. From my PC, I cannot ping it. When I ping it, it will show the following (edited for security)
Pinging estimating02.domainname.local [10.0.0.xx] with 32 bytes of data:
Reply from xx.0.0.xx: Destination host unreachable.
Reply from xx.0.0.xx: Destination host unreachable.
Reply from xx.0.0.xx: Destination host unreachable.
Reply from 0.0.0.xx: Destination host unreachable.
Ping statistics for xx.0.0.xx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
-
The showing of your own IP is because your computer is stating the not reachable reply...
-
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
The showing of your own IP is because your computer is stating the not reachable reply...
Right...just trying to be thorough.
If I do a path ping to estimating02, it stop at our default gateway, which is our internet router (hardware)...if I path ping a PC I know is pinging, it goes right to it...
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
These things make me think estimate02 is where the problem is. Likely a firewall issue.
Did your try resetting the network stack?
You could also try completely removing the Nic and the networking protocols. Then reboot and readd.
I really feel the the removal of Symantec is the root of your issue.
There might be a Symantec cleanup program you can run that might fix things.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
The showing of your own IP is because your computer is stating the not reachable reply...
Right...just trying to be thorough.
If I do a path ping to estimating02, it stop at our default gateway, which is our internet router (hardware)...if I path ping a PC I know is pinging, it goes right to it...
You mean tracert?
-
All right, clearly you have multiple issues. They appear to be all Windows Firewall related:
In the case that you posted, it is clear on the affected system - estimating02 - that inbound requests are being denied. Both from your system and the DC
Additionally, it is not a DNS issue, as this seems to be resolving just fine.
So on estimating02, go turn off any firewalls (just for testing) and try pinging it again. I think you'll find everything works. So then, simply restore the defaults of the Windows Firewall and re-input your exceptions. Then install Webroot.
-
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
These things make me think estimate02 is where the problem is. Likely a firewall issue.
Did your try resetting the network stack?
You could also try completely removing the Nic and the networking protocols. Then reboot and readd.
I really feel the the removal of Symantec is the root of your issue.
There might be a Symantec cleanup program you can run that might fix things.
Well, estimating02 is just the guinea pig...over half of our PC's are having this issue...and poor estimating02 was rebuilt last week and never had Symantec on it...was rebuild and went straight to WebRoot.
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
All right, clearly you have multiple issues. They appear to be all Windows Firewall related:
In the case that you posted, it is clear on the affected system - estimating02 - that inbound requests are being denied. Both from your system and the DC
Additionally, it is not a DNS issue, as this seems to be resolving just fine.
So on estimating02, go turn off any firewalls (just for testing) and try pinging it again. I think you'll find everything works. So then, simply restore the defaults of the Windows Firewall and re-input your exceptions. Then install Webroot.
I will give this a shot...if resolved, then I'll tackle why our main drafting program crashes when writing to file server. Will report back results.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
These things make me think estimate02 is where the problem is. Likely a firewall issue.
Did your try resetting the network stack?
You could also try completely removing the Nic and the networking protocols. Then reboot and readd.
I really feel the the removal of Symantec is the root of your issue.
There might be a Symantec cleanup program you can run that might fix things.
Well, estimating02 is just the guinea pig...over half of our PC's are having this issue...and poor estimating02 was rebuilt last week and never had Symantec on it...was rebuild and went straight to WebRoot.
This is likely still a firewall issue. You may find that you have to do this on all your systems. As a side note. if you have Webroot installed, you do not need Windows Firewall. I have found this to be the cause of many issues.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
These things make me think estimate02 is where the problem is. Likely a firewall issue.
Did your try resetting the network stack?
You could also try completely removing the Nic and the networking protocols. Then reboot and readd.
I really feel the the removal of Symantec is the root of your issue.
There might be a Symantec cleanup program you can run that might fix things.
Well, estimating02 is just the guinea pig...over half of our PC's are having this issue...and poor estimating02 was rebuilt last week and never had Symantec on it...was rebuild and went straight to WebRoot.
Ok good to know. Sadly in the last few days I've had a few windows 10 PCs drop off the LAN because of what I assume is a bad update process. I had to change a reg entry to fix.
So back to you... Are you managing the firewall through GPO?
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
These things make me think estimate02 is where the problem is. Likely a firewall issue.
Did your try resetting the network stack?
You could also try completely removing the Nic and the networking protocols. Then reboot and readd.
I really feel the the removal of Symantec is the root of your issue.
There might be a Symantec cleanup program you can run that might fix things.
Well, estimating02 is just the guinea pig...over half of our PC's are having this issue...and poor estimating02 was rebuilt last week and never had Symantec on it...was rebuild and went straight to WebRoot.
This is likely still a firewall issue. You may find that you have to do this on all your systems. As a side note. if you have Webroot installed, you do not need Windows Firewall. I have found this to be the cause of many issues.
A-OK...going to try this now...
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
About this ping...when it lists the FQDN and IP, it shows the IP assigned to this PC.
On the first reply, it showed MY PC address
On the last 3 Replies, it showed our Default Gateway Name.Pinging from the domain controller, it did the same, with it showing the IP of the domain controller first and then the IP of default Gateway the next 3 times.
On ESTIMATING02, he can ping the domain controller and my PC just fine.
These things make me think estimate02 is where the problem is. Likely a firewall issue.
Did your try resetting the network stack?
You could also try completely removing the Nic and the networking protocols. Then reboot and readd.
I really feel the the removal of Symantec is the root of your issue.
There might be a Symantec cleanup program you can run that might fix things.
Well, estimating02 is just the guinea pig...over half of our PC's are having this issue...and poor estimating02 was rebuilt last week and never had Symantec on it...was rebuild and went straight to WebRoot.
This is likely still a firewall issue. You may find that you have to do this on all your systems. As a side note. if you have Webroot installed, you do not need Windows Firewall. I have found this to be the cause of many issues.
By default Webroot will disable the firewall.
-
Since support is included.... Call Webroot and open a ticket. I have always found them very helpful
-
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Since support is included.... Call Webroot and open a ticket. I have always found them very helpful
This is a good point - Webroot is very powerful and some of its features may be causing slow write times from the drafting program. Webroot support can help sort that out.
Again, you can always test this theory by temporarily disabling Webroot on the affected station.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
All right, clearly you have multiple issues. They appear to be all Windows Firewall related:
In the case that you posted, it is clear on the affected system - estimating02 - that inbound requests are being denied. Both from your system and the DC
Additionally, it is not a DNS issue, as this seems to be resolving just fine.
So on estimating02, go turn off any firewalls (just for testing) and try pinging it again. I think you'll find everything works. So then, simply restore the defaults of the Windows Firewall and re-input your exceptions. Then install Webroot.
I will give this a shot...if resolved, then I'll tackle why our main drafting program crashes when writing to file server. Will report back results.
Turned off WIndows Firewall on estimating02 and my PC (webroot firewall is still running since for now)...still can't ping.
Unless I am looking in the wrong spot, I can only turn off WebRoot firewall via the group management and then only all PC's under that...
-
You can simply uninstall it on the workstation your testing, and then reinstall it when finished.
If this doesn't work, then we'll have to start looking elsewhere. Do you have a copy of NMap?
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
You can simply uninstall it on the workstation your testing, and then reinstall it when finished.
If this doesn't work, then we'll have to start looking elsewhere. Do you have a copy of NMap?
Uninstalled WebRoot and turned off Windows Firewall on Estimating02. Still doesn't ping.
Now, let's talk about Estimating01. I can ping it and it isn't one of the PC's having pinging issues. BUT, if he tried to ping me, it id's my PC as a 192 address and then simply shows 4 REQUEST TIMES OUT.
Not trying to complicate this issue but thought I would add that out there...
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
You can simply uninstall it on the workstation your testing, and then reinstall it when finished.
If this doesn't work, then we'll have to start looking elsewhere. Do you have a copy of NMap?
Uninstalled WebRoot and turned off Windows Firewall on Estimating02. Still doesn't ping.
Now, let's talk about Estimating01. I can ping it and it isn't one of the PC's having pinging issues. BUT, if he tried to ping me, it id's my PC as a 192 address and then simply shows 4 REQUEST TIMES OUT.
Not trying to complicate this issue but thought I would add that out there...
Does your computer have a 192 address on it anywhere at all?
Also, is your network one big flat network, or do you have various VLANS / subnets ?
-
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
You can simply uninstall it on the workstation your testing, and then reinstall it when finished.
If this doesn't work, then we'll have to start looking elsewhere. Do you have a copy of NMap?
Uninstalled WebRoot and turned off Windows Firewall on Estimating02. Still doesn't ping.
Now, let's talk about Estimating01. I can ping it and it isn't one of the PC's having pinging issues. BUT, if he tried to ping me, it id's my PC as a 192 address and then simply shows 4 REQUEST TIMES OUT.
Not trying to complicate this issue but thought I would add that out there...
Does your computer have a 192 address on it anywhere at all?
Also, is your network one big flat network, or do you have various VLANS / subnets ?
I keep my network simple since I am the SOLO IT Director for everything...no VLANS OR SUBNETS
We do have ONE single PC on our network that is domain connected BUT also has a second NIC for a 192 address for IP Camera's we have and yes, WebRoot is on this PC. And my PC is wireless compatible but WiFi was not turned on...but I did turn it on and lo and behold, that was the 192 address that Estimating01 sees when trying to ping me. After I flipped Wi-Fi on and back off, then Estimating01 saw me...so non issue here...but still....Something has really been hosed up since the AV Migration...thank goodness we are up and running.
Guess we'll go back to picking on Estimating02...
