Posts

Showing posts from January, 2025

SOLVED: Change the listening port on Windows Admin Center v2 because of error SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions.

Image
When you try and start Windows Admin Center v2 you might find that the "Windows Admin Center" service starts and then stops and the following error is logged in the event viewer. Exception Info: System.Net.Sockets.SocketException (10013): An attempt was made to access a socket in a way forbidden by its access permissions. This maybe because there is another application running on port 443 (the default Windows Admin Center port). You can check this by running the PowerShell cmdlet and note the process identifer (in my case this is running the Hyper-V virtual machine replication service). Get-NetTCPConnection -LocalPort 443|SELECT LocalAddress, OwningProcess Edit the configuration file C:\Program Files\WindowsAdminCenter\Service\appsettings.json And edit the following two locations And... Setting these values to an available port (in this example 8443) and restart the service. While you're here why not check out our  IT documentation tool ?
Post a Comment
Read more

SOLVED: Copy and paste to or from a VMware workstation virtual machine doesn't work on Windows host or stops working intermittently

Image
You might find when you try to copy and paste to or from a VMware workstation virtual machine that it doesn't work on your Windows host machine or that it stops working intermittently. There's a few things you can try... Close and re-open VMware workstation (but select to Run in Background so that your virtual machines are not stopped in the process). This will often resolve the issue. Stop and start the VMware tools service on the guest machine. Reinstall (or upgrade) the VMware tools on the guest. Using a version of VMware tools that is not aligned with the version of VMware Workstation will often cause issues. Reboot the guest machine. Reboot the host machine. While you're here why not check out our  IT documentation tool ?
Post a Comment
Read more

SOLVED: PowerShell Remoting (WinRM) only listening on certain and not all IP addresses

Image
We've recently had an issue trying to connect to PowerShell remoting on a certain machine. Connections resulted in the following issue: Connecting to remote server machine name failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic. The firewalls (both Windows Firewall and external firewalls) were configured correctly and running  winrm enumerate winrm/config/listener  showed the listener was correctly configured. However, running the following command doesn't show it listening on all IP address...
Post a Comment
Read more