By default, PowerShell remoting uses Kerberos authentication and works only in domain environments, and only when you specify computer names, not IP addresses. Configuring PowerShell...
By default, PowerShell remoting uses Kerberos authentication and works only in domain environments, and only when you specify computer names, not IP addresses.
PS C:\> Start-Service -Name WinRM
Next, take a look at these lines:
Set-Item wsman:\localhost\client\trustedhosts server_* -Force Set-Item wsman:\localhost\client\trustedhosts 10.10.10.* -Force -Concatenate Set-Item wsman:\localhost\client\trustedhosts 192.168.2.110 -Force -Concatenate Get-ChildItem wsman:\localhost\client
They illustrate how you configure the TrustedHosts list to allow NTLM authentication with various targets. In the example, you would now be able to connect to any machine name that starts with “server_”, plus all IP addresses that start with “10.10.10.”, plus the IP address 192.168.2.110.
When you do connect to any of these systems, for example using Enter-PSSession, make sure you also explicitly specify the user account with -Credential. Transparent authentication is supported for Kerberos only in a domain environment.
Europe: April 20-22: 3-day PowerShell Conference EU in Hannover, Germany, with more than 30+ speakers including Jeffrey Snover and Bruce Payette, and 60+ sessions: www.psconf.eu.
Asia: October 21-22: 2-day PowerShell Conference Asia in Singapore. Watch latest announcements at www.psconf.asia
North America: April 4-6: 3-day PowerShell and DevOps Global Summit in Bellevue, WA, USA with 20+ speakers including many PowerShell Team members: https://eventloom.com/event/home/PSNA16
All events have limited seats available so you may want to register early.
Contact our sales team to get a personalized demo of our database management software for SQL Server!
