@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: ::1

Name: estimating02.domainname.local
Address: shows correct IP address

Is 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.

@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: ::1

Name: 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:

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.

@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.

@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:

@garak0410

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...

@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:

@garak0410

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:

@garak0410

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...

@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

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.

@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.

@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...

@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.

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...

@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:

@garak0410

Always a good idea

But always tempting to try anyway during business hours...

@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:

@garak0410

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...

@pchiodo said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:

@garak0410

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.

@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:

@garak0410

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!

@scottalanmiller said in Microsoft Event:

@garak0410 ah, as a consumer customer, not as a business customer. I see.

Right...in our business, I am digging them.

@scottalanmiller said in Microsoft Event:

@garak0410 said in Microsoft Event:

@scottalanmiller said in Microsoft Event:

@Dashrender said in Microsoft Event:

@garak0410 said in Microsoft Event:

@Dashrender said in Microsoft Event:

@momurda said in Microsoft Event:

I saw this
http://arstechnica.com/gadgets/2016/10/microsoft-announces-surface-studio-all-in-one-touchscreen-pc/
Looks sweet, that screen is just wow

And so is that worse that iMac price

Before the prices were released, I was already thinking of "selling stuff'" to get the Surface Studio...Ah no...unless my boss gets me one...

So they talked about this on Windows Weekly last night. Apparently the Studio is geared toward (and the event in general was too) to creatives - people who work on these Wacom type devices. Apparently the typical display these people work on costs $1500+ So that means only a $1500 PC (for the bottom end) - OK when considered in that context I suppose this is OK. But I wonder if these guys will really buy an All-in-one? Assuming these guys need computing power, won't they be replacing the PC every 3 years or so? But the monitors probably last more like 6 or even 10. So now you're throwing out the baby with the bath water. But then I have to ask, have we reached a point, even for these guys, that we no longer need faster and faster compute power for these tasks? Generally we don't use end user stations to do things like rendering - we send that off to a rendering farm

The iMac was very popular for this market. So this could easily fit in that niche.

Agreed...I think Microsoft is focusing on niches and businesses with Nadella. I for one am a fan of him, even if I do feel isolated as a consumer...

What makes you feel isolated as a customer?

Just not much that is Microsoft Branded that I can get excited about as a consumer/home user. Was a big fan of Zune, Windows Phone, Kinect, Windows Media Center, ROOMS on Windows Phone, Cortana, and to a lessor extent BING FOOD and DRINK (I entered 100s of entries only to have app closed and taken away from me)...I know technology changes and moves on but they often take away many things I like to use, promote and get excited about on a consumer level. Not complaining so much as I find it hard to get excited about anything offered to consumers as it either just becomes unsupported or never sees the light of day.

@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.