How do I set up a secure WinRM connection?

Question

Windows Server

Good afternoon!
Faced a problem of the following character.
You need to configure everything in the WinRM domain, everything seems to work well, the policy can be connected to computers via PSSesion.
However, if I try to put a restriction on the policy, that is, allow Windows Remote Management only to a specific IP address or host. Everything no longer works at all.
I tried to make a rule in the Ogene Wall by opening a connection from a specific IP address. However, the fire eraser does not let you in. Writes the following in the logs

2018-09-03 18:31:36 DROP UDP fe80::9423:bf4f:a61f:e3c1 ff02::fb 5353 5353 84 - - - - - - - RECEIVE
2018-09-03 18:31:37 DROP UDP fe80::9423:bf4f:a61f:e3c1 ff02::fb 5353 5353 185 - - - - - - - RECEIVE
2018-09-03 18:31:38 DROP UDP fe80::9423:bf4f:a61f:e3c1 ff02::fb 5353 5353 84 - - - - - - - RECEIVE
2018-09-03 18:31:40 DROP UDP fe80::9423:bf4f:a61f:e3c1 ff02::fb 5353 5353 185 - - - - - - - RECEIVE
2018-09-03 18:31:42 DROP UDP fe80::9423:bf4f:a61f:e3c1 ff02::fb 5353 5353 84 - - - - - - - RECEIVE
2018-09-03 18:31:50 DROP UDP fe80::9423:bf4f:a61f:e3c1 ff02::fb 5353 5353 84 - - - - - - - RECEIVE
2018-09-03 18:36:07 DROP TCP 192.168.4.137 192.168.4.129 63276 5985 52 S 231533463 0 8192 - - - RECEIVE
2018-09-03 18:36:10 DROP TCP 192.168.4.137 192.168.4.129 63276 5985 52 S 231533463 0 8192 - - - RECEIVE
2018-09-03 18:36:17 DROP TCP 192.168.4.137 192.168.4.129 63276 5985 48 S 231533463 0 8192 - - - RECEIVE
2018-09-03 18:37:27 DROP TCP 192.168.4.137 192.168.4.129 63563 5985 52 S 2226797805 0 8192 - - - RECEIVE
2018-09-03 18:37:30 DROP TCP 192.168.4.137 192.168.4.129 63563 5985 52 S 2226797805 0 8192 - - - RECEIVE
2018-09-03 18:37:36 DROP TCP 192.168.4.137 192.168.4.129 63563 5985 48 S 2226797805 0 8192 - - - RECEIVE

Tell me who has come across winRM how to set up a secure connection.
Thank you

Answer 1

Try using the hostname instead of the machine's ip address

Answer 2

Well, the fact that you have packages dropping on the "wall of fire" - at the setting of the "wall" itself)) and according to winRM - what do you mean by the word "safe"? At the application level, this is, for example, HTTP / HTTPS. You, as far as I understand, want to limit the connection by resource. Tools must be used for their intended purpose. If you need to restrict access to somewhere from any sources, just the "fiery wall" exists, and take care of its settings. And in the policies there are Trusted Hosts - but this restriction is not in terms of resources, but in terms of goals. Created for admins so that you can safely protect important resources.