Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: iviikel on April 07, 2020, 07:39:18 am
-
Is there any way to enable echo on a repair or is the special sauce a secret? In my Citrix environment using machine creation services and app layering the resulting servers cannot start the Network Location Awareness service. When I run the "Network Repair" it fixes the issue. I'm trying to track down root cause by recreating what this repair is doing but following the repair info and running the commands manually doesn't fix the issue. I seem to be missing something that isn't in the repair info but is happening when running the repair from the tool.
-
I'm not familiar with Citrix VM Servers but the status of the Network Location Awareness service should be Automatic and Running.
You can check this by going Start - type services.msc and press enter when it comes up and scroll down to its location.
I'm not sure if these cmds run from an admin Command Prompt will help but they can for normal network problems.
netsh winsock reset
netsh int ip reset resetlog.txt
shutdown /r /t 00
Then see how things are after the reboot.
I will pass your query onto Shane but I haven't had a reply to a couple of emails I've sent him.
With this Caronavirus going around, I have no idea if he has become infected.
-
Sadly tried those steps and no luck...
tried these commands manually...
ipconfig /flushdns
netsh winsock reset
netsh int ip reset
netsh winsock reset all
netsh int ipv4 reset all
netsh int ipv6 reset all
netsh int httpstunnel reset all
netsh int isatap reset all
netsh int portproxy reset all
netsh int tcp reset all
and importing these reg keys manually...
Winsock.reg
Winsock2.reg
This didn't fix it, but running the "Network Repair" did without a reboot.
Luckily testing is extremely easy as MCS servers with Citrix utilize a dif disk so every reboot I can break it.
Thanks
-
This can be archived, I found what was being run during the repair using processmonitor and was able to track down the exact command that was running to resolve the issue. (Setting permissions).
Thanks
-
That's good news.
However, I thought you had just run the Network Repair on its own ?
If it's a Permissions issue then perhaps creating a new account could help if something is corrupting those.