It's possible, but you can't use the default Kerberos authentication in that scenario. Off the top of my head, I don't remember if the PSRemoting commands automatically fall through to NTLM authentication if Kerberos isn't avaialble, or if you have to specify it yourself by using the "-Authentication Negotiate" argument when calling New-PSSession, Invoke-Command, etc.
You'll also either have to set up an HTTPS listener, or use the TrustedHosts list (HTTPS being the more secure option, since it authenticates the remote computer before it exposes anything related to your user credentials.) There are examples of how to do both of these in the free "Secrets of PowerShell Remoting" ebook, which you can download from https://powershell.org/ebooks/ .
Anyway it goes on to tell you how to use the winrm command line syntax to manually add a list of hosts that are allowed to remote. This PDF file was the most helpful to me for figuring out how to do it, and it does work. However I need to get around to figuring out how to add a CIDR noted IP range to it.