- April 5, 2016 at 1:50 pm #37261
New-PSSession -ComputerName dc1,dc2,dc3
dc2 gets a new PSSession while dc1 and dc3 each get this error:
"The WinRM client cannot process the request because the server name cannot be resolved. For more information, see the about_Remote_Troubleshooting Help topic."
I have tried the following:
~ validated with nslookup; fully resolving dc1 and dc3
~ read about_Remote_Troubleshooting
~ read about_Remote_Requirements
~ re-run Enable-PSRemoting on both erroring dcs
~ validated port 5985 is LISTENING from my console (running under Administrator context)
What is causing WinRM failing to resolve the server name?
thank youApril 5, 2016 at 2:20 pm #37263
I tried the FQDN in the -ComputerName parameter and it created the sessions.April 5, 2016 at 2:44 pm #37265
Looks like you have a name resolution problem. The NETBIOS name doesn't work, so try to empty your cache with: nbtstat -R
If this doesn't work, check the network category on your computer and/or the domain controllers with Get-NetConnectionProfile. This should be set to "DomainAuthenticated".
If not, set them to DomainAuthenticated:
Set-NetConnectionProfile -InterfaceAlias 'Ethernet' -NetworkCategory DomainAuthenticated
After run Enable-PSRemoting again to create the appropiate firewall rules on the Windows Firewall.April 5, 2016 at 3:12 pm #37266
I simply had to add the DNS name to the network adapters DNS suffix search list.
You must be logged in to reply to this topic.