Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up
-
Check your Windows Firewall settings and ensure that Windows Remote Management is checked... (screenshot is from a non-domain joined machine)
-
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Check your Windows Firewall settings and ensure that Windows Remote Management is checked... (screenshot is from a non-domain joined machine)
Tried that...still get this and then it says it cannot be connected...
-
@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:
Check your Windows Firewall settings and ensure that Windows Remote Management is checked... (screenshot is from a non-domain joined machine)
Tried that...still get this and then it says it cannot be connected...
Check the WinRM service is started?
-
@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:
Check your Windows Firewall settings and ensure that Windows Remote Management is checked... (screenshot is from a non-domain joined machine)
Tried that...still get this and then it says it cannot be connected...
Check the WinRM service is started?
It was stopped and on manual...started it and set to automatic...rebooted...still can't access it on this one PC...will test on another PC where I know the user is out today.
So really, what could have caused all these Windows Firewall settings and remote services to be so messed up? I'm guessing it was the "Scorched Earth" of Symantec removal but weird it was hit and miss...
-
@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:
Check your Windows Firewall settings and ensure that Windows Remote Management is checked... (screenshot is from a non-domain joined machine)
Tried that...still get this and then it says it cannot be connected...
Check the WinRM service is started?
It was stopped and on manual...started it and set to automatic...rebooted...still can't access it on this one PC...will test on another PC where I know the user is out today.
So really, what could have caused all these Windows Firewall settings and remote services to be so messed up? I'm guessing it was the "Scorched Earth" of Symantec removal but weird it was hit and miss...
Symantec's removal process has always been painful, and has always done odd things like this, based on what patches were installed when Symantec was installed.
-
@DustinB3403 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:
@dafyre said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
Check your Windows Firewall settings and ensure that Windows Remote Management is checked... (screenshot is from a non-domain joined machine)
Tried that...still get this and then it says it cannot be connected...
Check the WinRM service is started?
It was stopped and on manual...started it and set to automatic...rebooted...still can't access it on this one PC...will test on another PC where I know the user is out today.
So really, what could have caused all these Windows Firewall settings and remote services to be so messed up? I'm guessing it was the "Scorched Earth" of Symantec removal but weird it was hit and miss...
Symantec's removal process has always been painful, and has always done odd things like this, based on what patches were installed when Symantec was installed.
This may be for another post, but once this is done, then I need to find out why our drafting program, that writes heavily to network shares, just randomly locks up during the heavy writing. Exiting and going back in will fix it but it returns later...no logs generated, wireshark doesn't report anything...wondering if there is a firewall setting on file server I need to check...
-
@garak0410 I would find it odd that a firewall rule would only cause issues during heavy usage.
I would lean towards a NIC issue as being the culprit.
-
I agree probably a NIC issue. I'd do a TCP stack reset. Of course that will knock it offline, so after-hours.
-
Nice find on the firewall being the main cause.
Sometimes a reboot is required before settings really take effect.
What network do the machines think they are in? Public/work/private?
It needs to match the firewall rule you enabled.
You should deploy the firewall settings you want via GPO to ensure they don't randomly change... or if they do, they change back on the next GPO update.
-
@Dashrender said in Most Workstations Don't Ping But Are Connected - Some Network Apps Are Locking Up:
I agree probably a NIC issue. I'd do a TCP stack reset. Of course that will knock it offline, so after-hours.
NIC on the virtual host since the file server is on a VM? Not everyone is locking up...but tends to be the same 4-5 people...can't imagine that many NIC's causing it and I've yet to duplicate it on my machine, WHEN I have the time...
-
@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:
I agree probably a NIC issue. I'd do a TCP stack reset. Of course that will knock it offline, so after-hours.
NIC on the virtual host since the file server is on a VM? Not everyone is locking up...but tends to be the same 4-5 people...can't imagine that many NIC's causing it and I've yet to duplicate it on my machine, WHEN I have the time...
Yes, on the VM, not the host.
