Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up
-
@coliver 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:
Users already reporting lockups in that one program which extensively writes to a network share. These problems have only occurred since removing Symantec Endpoint from our servers when we migrated to WebRoot. I did not load WebRoot (as of yet) on servers.
Symantec! Oh that's not good it has been known for destroying workstations when it is removed.
Yes, this. Did you run the special removal tool, or just do a standard uninstall?
-
@coliver 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:
Users already reporting lockups in that one program which extensively writes to a network share. These problems have only occurred since removing Symantec Endpoint from our servers when we migrated to WebRoot. I did not load WebRoot (as of yet) on servers.
Symantec! Oh that's not good it has been known for destroying workstations when it is removed.
Yep... sadly you might be in for a reinstalling/reimaging good time.
Try a network stack reset to see if that fixes your issue.
-
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
@coliver 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:
Users already reporting lockups in that one program which extensively writes to a network share. These problems have only occurred since removing Symantec Endpoint from our servers when we migrated to WebRoot. I did not load WebRoot (as of yet) on servers.
Symantec! Oh that's not good it has been known for destroying workstations when it is removed.
Yep... sadly you might be in for a reinstalling/reimaging good time.
Try a network stack reset to see if that fixes your issue.
I sure hope not...especially on these servers...I will try the network stack reset...thankfully, these problems are more annoying than show stopping but it is driving me crazy...
-
@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:
@coliver 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:
Users already reporting lockups in that one program which extensively writes to a network share. These problems have only occurred since removing Symantec Endpoint from our servers when we migrated to WebRoot. I did not load WebRoot (as of yet) on servers.
Symantec! Oh that's not good it has been known for destroying workstations when it is removed.
Yep... sadly you might be in for a reinstalling/reimaging good time.
Try a network stack reset to see if that fixes your issue.
I sure hope not...especially on these servers...I will try the network stack reset...thankfully, these problems are more annoying than show stopping but it is driving me crazy...
Consider yourself lucky that your problems are more just annoying than show stopping. Symantec is persona non grata to most of us for many reasons. One is that uninstalling their software breaks systems.
-
@travisdh1 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:
@coliver 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:
Users already reporting lockups in that one program which extensively writes to a network share. These problems have only occurred since removing Symantec Endpoint from our servers when we migrated to WebRoot. I did not load WebRoot (as of yet) on servers.
Symantec! Oh that's not good it has been known for destroying workstations when it is removed.
Yep... sadly you might be in for a reinstalling/reimaging good time.
Try a network stack reset to see if that fixes your issue.
I sure hope not...especially on these servers...I will try the network stack reset...thankfully, these problems are more annoying than show stopping but it is driving me crazy...
Consider yourself lucky that your problems are more just annoying than show stopping. Symantec is persona non grata to most of us for many reasons. One is that uninstalling their software breaks systems.
Oh I agree, which is one of the reasons I put off upgrading for 5 years (this place was already on Symantec)...and for the most part, it has been very quiet since WebRoot...but the not pinging workstations and this one program locking up when writing to network share is going to annoy me until I get it working again.
-
If you have Windows Firewall disabled, re-enable it, then turn it off, but leave the service running, and see if the problems go away.
Start with one workstation and the server that appears to be dropping when writing.
-
Another thing to check for is the Symantec Network Threat Protection driver. You'll find this under Device Manager network connections as Teefer2 or something similar.
If you find it, it may be difficult to remove, as standard methods tend to fail.
You might want to look in the registry and delete the 'Config' entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network
Then you should be able to remove your network cards and the teefer2 entries from device manager.
Reboot, and then reconfig the network cards. Make sure you have the latest updated drivers.
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Another thing to check for is the Symantec Network Threat Protection driver. You'll find this under Device Manager network connections as Teefer2 or something similar.
If you find it, it may be difficult to remove, as standard methods tend to fail.
You might want to look in the registry and delete the 'Config' entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network
Then you should be able to remove your network cards and the teefer2 entries from device manager.
Reboot, and then reconfig the network cards. Make sure you have the latest updated drivers.
IF I am looking in right spot, I only see one Network Adapter...MICROSOFT HYPER-V NETWORK ADAPTER on our file server that I removed Symantec from (but didn't install WebRoot as of yet).
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
If you have Windows Firewall disabled, re-enable it, then turn it off, but leave the service running, and see if the problems go away.
Start with one workstation and the server that appears to be dropping when writing.
On the file server (where the files write to), Windows Firewall is On. Now, if I ping back to a workstation that I know has both "can't ping" and that drafting program lockup, it won't ping...DESTINATION HOST UNREACHABLE. I don't think it is related as another PC that can ping both ways also locked up with the drafting program.
It's maddening I tell you!
-
Hmm. in reading your error message it refers to COM+, but this doesn't seem right. It appears WMI may not have the correct fire wall rules.
On the Hyper-V server try this:
netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes
netsh advfirewall firewall set rule group="Remote Event Log Management" new enable=yes
Pretty sure Symantec mucked up Windows Firewall.
You might try turning it off for testing and see if the problems go away. Then you'll know specifically if it is firewall related.
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Hmm. in reading your error message it refers to COM+, but this doesn't seem right. It appears WMI may not have the correct fire wall rules.
On the Hyper-V server try this:
netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes
netsh advfirewall firewall set rule group="Remote Event Log Management" new enable=yes
Pretty sure Symantec mucked up Windows Firewall.
You might try turning it off for testing and see if the problems go away. Then you'll know specifically if it is firewall related.
Trying this...
I did find an old SpiceWorks ticket (thank goodness for documenting) I opened over a year ago when we moved to the Cloud Based Symantec. It was titled New Anti-Virus - DHCP/DNS Issues. But my fault, I didn't document it very well at the solution...at the time, it said I couldn't ping or even connect to C$ on most workstations...my solution read as this:
"The File/Print sharing option was not allowed in firewall profile. I added it but it still didn't work. It was set to RED and not green."
That doesn't tell me much...don't know if I changed it on the Symantec End, Windows Firewall end and if that, which server?
I really do think Symantec mucked up some things...
Also side note, I have Webroot uninstalled on a suspect machine that will not PING and I actually have all of WebRoot's firewall turned off for all machines...still pinging issues...so guessing it is on the server(s) that I removed Symantec from.
-
@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:
Hmm. in reading your error message it refers to COM+, but this doesn't seem right. It appears WMI may not have the correct fire wall rules.
On the Hyper-V server try this:
netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes
netsh advfirewall firewall set rule group="Remote Event Log Management" new enable=yes
Pretty sure Symantec mucked up Windows Firewall.
You might try turning it off for testing and see if the problems go away. Then you'll know specifically if it is firewall related.
Trying this...
I did find an old SpiceWorks ticket (thank goodness for documenting) I opened over a year ago when we moved to the Cloud Based Symantec. It was titled New Anti-Virus - DHCP/DNS Issues. But my fault, I didn't document it very well at the solution...at the time, it said I couldn't ping or even connect to C$ on most workstations...my solution read as this:
"The File/Print sharing option was not allowed in firewall profile. I added it but it still didn't work. It was set to RED and not green."
That doesn't tell me much...don't know if I changed it on the Symantec End, Windows Firewall end and if that, which server?
I really do think Symantec mucked up some things...
Also side note, I have Webroot uninstalled on a suspect machine that will not PING and I actually have all of WebRoot's firewall turned off for all machines...still pinging issues...so guessing it is on the server(s) that I removed Symantec from.
I was going to mention that it really sounded like a server side issue with the multiple clients failing on the writes. Google search also provided some Symantec removal tools that might be of assistance.
You might also attempt to restore the firewall to defaults. You can do this through the Windows Firewall config. There should be an option on the left hand side to restore defaults.
Like I said previously, you can try and just turn off the firewall on the server and see if the problems go away. If so, you know that it has something to do with the firewall.
-
@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:
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Hmm. in reading your error message it refers to COM+, but this doesn't seem right. It appears WMI may not have the correct fire wall rules.
On the Hyper-V server try this:
netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes
netsh advfirewall firewall set rule group="Remote Event Log Management" new enable=yes
Pretty sure Symantec mucked up Windows Firewall.
You might try turning it off for testing and see if the problems go away. Then you'll know specifically if it is firewall related.
Trying this...
I did find an old SpiceWorks ticket (thank goodness for documenting) I opened over a year ago when we moved to the Cloud Based Symantec. It was titled New Anti-Virus - DHCP/DNS Issues. But my fault, I didn't document it very well at the solution...at the time, it said I couldn't ping or even connect to C$ on most workstations...my solution read as this:
"The File/Print sharing option was not allowed in firewall profile. I added it but it still didn't work. It was set to RED and not green."
That doesn't tell me much...don't know if I changed it on the Symantec End, Windows Firewall end and if that, which server?
I really do think Symantec mucked up some things...
Also side note, I have Webroot uninstalled on a suspect machine that will not PING and I actually have all of WebRoot's firewall turned off for all machines...still pinging issues...so guessing it is on the server(s) that I removed Symantec from.
I was going to mention that it really sounded like a server side issue with the multiple clients failing on the writes. Google search also provided some Symantec removal tools that might be of assistance.
You might also attempt to restore the firewall to defaults. You can do this through the Windows Firewall config. There should be an option on the left hand side to restore defaults.
Like I said previously, you can try and just turn off the firewall on the server and see if the problems go away. If so, you know that it has something to do with the firewall.
While I don't think it would affect anything during business hours, I'll hold off on turning the firewall off until later...
-
Always a good idea
-
@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Always a good idea
But always tempting to try anyway during business hours...
-
Turned off Windows Firewall on our Domain Controller which is also our DNS and DHCP server...still difficulty pinging some workstations and remote COMPUTER MANAGEMENT still doesn't work...
I think I want to tackle one thing at a time...the pinging issue....I'd say about half the workstations won't ping...even with both Webroot and Windows Firewall turned off on the the DHCP/DNS server.
So radical idea...should I install WebRoot on the server(s)? I don't think it will work because WebRoot sells itself in working along side other AV programs and it may not turn off the left over Symantec. Just thinking aloud...
-
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.
