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.
-
@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...
-
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
-
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Fix one and maybe you figure out how to fix them all.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Estimating02 CAN ping the Domain Controller, DHCP/DNS Server and File Server.
The Domain Controller, DHCP/DNS Server and File Server cannot ping Estimating02.When doing a tracert from Domain Controller to Estimating02 it stops on the first hop attempt from the domain controller with DESTINATION HOST UNREACHABLE.
-
@garak0410 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:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Estimating02 CAN ping the Domain Controller, DHCP/DNS Server and File Server.
The Domain Controller, DHCP/DNS Server and File Server cannot ping Estimating02.From the Domain Controller ...
nslookup estimating02.yourdomain.local and ensure the IP it returns matches with estimating02's actual IP?
-
@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:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Estimating02 CAN ping the Domain Controller, DHCP/DNS Server and File Server.
The Domain Controller, DHCP/DNS Server and File Server cannot ping Estimating02.From the Domain Controller ...
nslookup estimating02.yourdomain.local and ensure the IP it returns matches with estimating02's actual IP?
Server: localhost
Address: ::1Name: estimating02.domainname.local
Address: shows correct IP address -
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@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:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Estimating02 CAN ping the Domain Controller, DHCP/DNS Server and File Server.
The Domain Controller, DHCP/DNS Server and File Server cannot ping Estimating02.From the Domain Controller ...
nslookup estimating02.yourdomain.local and ensure the IP it returns matches with estimating02's actual IP?
Server: localhost
Address: ::1Name: estimating02.domainname.local
Address: shows correct IP addressIs Estimating02 able to surf the internet without issues, and it only has problems accessing SMB file shares / in-house stuff?
Or is the only problem when this one application tries to do stuff?
-
@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:
@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:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Estimating02 CAN ping the Domain Controller, DHCP/DNS Server and File Server.
The Domain Controller, DHCP/DNS Server and File Server cannot ping Estimating02.From the Domain Controller ...
nslookup estimating02.yourdomain.local and ensure the IP it returns matches with estimating02's actual IP?
Server: localhost
Address: ::1Name: estimating02.domainname.local
Address: shows correct IP addressIs Estimating02 able to surf the internet without issues, and it only has problems accessing SMB file shares / in-house stuff?
Or is the only problem when this one application tries to do stuff?
Estimating02 is only having the problem where the program MBS (which writes heavily to a network share) will just lock up at random during writing. (side note...even PC's that ping are having this random lockup issue). It is the one application that is having the problem. We use Microsoft Dynamic's (on a VM on a second virtual host) and had no issues...
No internet surfing problems for estimating02.
And a reminder...on the PC's that I can't ping, and I am sure it stands to reason, I can no longer access their C$ as a Domain Admin.
-
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@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:
@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:
@garak0410 said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
What happens with estimating02 if you try to ping the DHCP, DNS, or AD servers? Is that what is not working?
I will go try right now...and again, only picking on estimating02 because the user is out today...over half our PC's are having this "not pining" problem and those same users are having that one program randomly lock up when doing heavy writing to a network share.
Estimating02 CAN ping the Domain Controller, DHCP/DNS Server and File Server.
The Domain Controller, DHCP/DNS Server and File Server cannot ping Estimating02.From the Domain Controller ...
nslookup estimating02.yourdomain.local and ensure the IP it returns matches with estimating02's actual IP?
Server: localhost
Address: ::1Name: estimating02.domainname.local
Address: shows correct IP addressIs Estimating02 able to surf the internet without issues, and it only has problems accessing SMB file shares / in-house stuff?
Or is the only problem when this one application tries to do stuff?
Estimating02 is only having the problem where the program MBS (which writes heavily to a network share) will just lock up at random during writing. (side note...even PC's that ping are having this random lockup issue). It is the one application that is having the problem. We use Microsoft Dynamic's (on a VM on a second virtual host) and had no issues...
No internet surfing problems for estimating02.
And a reminder...on the PC's that I can't ping, and I am sure it stands to reason, I can no longer access their C$ as a Domain Admin.
So the issue with MBS started after you uninstalled Symantec?
Have you run one of the Symantec uninstaller / cleanup tools on this system and not just removed it from Add/Remove Programs?
