Had the user start a Quick Assist session, and I can see that ScreenConnect is installed, but for some reason the service bombs the instant it's started. Nmap scan the device - ZERO open ports on it, which would explain why I can't get to anything. Can I even get to the c$ administrative share? Nope. CompMgmt? Nope, won't connect to it either. Huh, OK, can I pop into PowerShell remoting and enable Remote Desktop temporarily? Nope, connection refused. Had the user go to run ScreenConnect manually, but it would just launch and close out. Check on the network controller, yep, the PC is on the network, but no ScreenConnect connectivity despite the user saying they had internet no problem. But this one had not connected to ScreenConnect in over 450 days. Normally I ScreenConnect in to the PC, bing bang there we go. Had an interesting case the other day user called in asking for some assistance getting set up on a PC.
0 kommentar(er)
