samba - May 2015 - Trouble Connecting Windows 8.1 RSAT to Samba Domain

I saw the following thread in the samba list archives but no solution:

http://marc.info/?l=samba&m=141214808508452&w=2

Host OS:  CentOS ver 7.1503
Samba:  Version 4.1.17-SerNet-RedHat-11.el7
Samba4 is running with internal DNS.
I'm able to add a domain user with samba-tool and connect Win 8.1 client to
the domain.

When I run Microsoft Server Manager and try to "manage" the server
using
Administrator credentials, I receive the following error:

"Target computer not accessible 5/4/2015."

The Server Manager activity notification states, "The refresh failed
because WinRM is not running and could not be started."

I have performed ipconfig /all on the Win 8.1 client and Samba4 box is
listed in the "DNS Server" output.

Does anyone know how to resolve the WinRM errors?

--------------------------------------------------

Sidenote:  I'm curious how many Samba4 domain admins choose to use the RSAT
tools; or, whether most prefer to use samba-tool to config and manage the
domain users, groups, and services.

--------------------------------------------------

Thank you for your help.

Hello Mike,

Am 04.05.2015 um 15:50 schrieb Mike:
> I saw the following thread in the samba list archives but no solution:
> 
> http://marc.info/?l=samba&m=141214808508452&w=2
> 
> Host OS:  CentOS ver 7.1503
> Samba:  Version 4.1.17-SerNet-RedHat-11.el7
> Samba4 is running with internal DNS.
> I'm able to add a domain user with samba-tool and connect Win 8.1
client to
> the domain.
> 
> When I run Microsoft Server Manager and try to "manage" the
server using
> Administrator credentials, I receive the following error:
> 
> "Target computer not accessible 5/4/2015."
> 
> The Server Manager activity notification states, "The refresh failed
> because WinRM is not running and could not be started."
> 
> I have performed ipconfig /all on the Win 8.1 client and Samba4 box is
> listed in the "DNS Server" output.
Can you give some step-by-step instructions, so I an try to reproduce it?

I just installed the RSAT, opened ADUC, DNS, etc. or started mmc.exe and
added the corresponding snap-ins.




> Sidenote:  I'm curious how many Samba4 domain admins choose to use the
RSAT
> tools; or, whether most prefer to use samba-tool to config and manage the
> domain users, groups, and services.
This answer is part of my SambaXP presentation (http://www.sambaxp.org/)
in two weeks. ;-)

Slides, raw data and a full report of the user survey I will publish
after the conference and announce here on the list, as well.


Regards,
Marc

Marc,

Sounds like a great presentation and I wish I could attend.
The steps are:

1.  Downloaded and installed the RSAT for Windows 8.1 X64.

2.  Log into Windows 8.1 client with Domain Administrator account.

3.  Execute Server Manager.

4.  From Server Manager Dashboard, I choose "Manage" from the top
menu, and
then Add Servers.

5.  The Add Servers screen shows up with the Active Directory Tab
highlighted.  It already shows the samba server domain name.  Example:  if
full domain name is internal.example.com, what shows in the Location: field
is "internal".

6.  I fill in the CN:  a10 and click Find Now.  The Samba server machine
name shows up in the field below.  I highlight it and then click the
">"
button to make it show up in the "Selected" field to the right.  Then
click
OK.

7.  I'm then back at the All Servers page and I click the Refresh option
under Tasks drop-down menu.  The refresh fails and produces a red flag
icon.  The error details state:

a10:  Refresh failed with the following error:  The RPC Server is
unavailable.
a10:  Configuration refresh failed with the following error:  The metadata
failed to be retrieved from the server, due to the following error:  WinRM
cannot complete the operation.  Verify that the specified computer name is
valid, that the computer is accessible over the network, and that a
firewall exception for the WinRM service is enabled and allows access from
this computer.  By default, the WinRM firewall exception for public
profiles limits access to remote computers within the same local subnet.

The windows client is on the same local subnet.
The windows client can authenticate to the samba server using the domain
User account and/or the Administrator account.
All necessary ports are open on the samba server.
The computer name is correct and hostname -f reports
a10.internal.example.com.

I appreciate your help.  Please let me know if there's anything else I can
provide.
Best regards,
Mike

On Mon, May 4, 2015 at 2:14 PM, Marc Muehlfeld <mmuehlfeld at samba.org>
wrote:
> Hello Mike,
>
> Am 04.05.2015 um 15:50 schrieb Mike:
> > I saw the following thread in the samba list archives but no solution:
> >
> > http://marc.info/?l=samba&m=141214808508452&w=2
> >
> > Host OS:  CentOS ver 7.1503
> > Samba:  Version 4.1.17-SerNet-RedHat-11.el7
> > Samba4 is running with internal DNS.
> > I'm able to add a domain user with samba-tool and connect Win 8.1
client
> to
> > the domain.
> >
> > When I run Microsoft Server Manager and try to "manage" the
server using
> > Administrator credentials, I receive the following error:
> >
> > "Target computer not accessible 5/4/2015."
> >
> > The Server Manager activity notification states, "The refresh
failed
> > because WinRM is not running and could not be started."
> >
> > I have performed ipconfig /all on the Win 8.1 client and Samba4 box is
> > listed in the "DNS Server" output.
>
> Can you give some step-by-step instructions, so I an try to reproduce it?
>
> I just installed the RSAT, opened ADUC, DNS, etc. or started mmc.exe and
> added the corresponding snap-ins.
>
>
>
>
>
> > Sidenote:  I'm curious how many Samba4 domain admins choose to use
the
> RSAT
> > tools; or, whether most prefer to use samba-tool to config and manage
the
> > domain users, groups, and services.
>
> This answer is part of my SambaXP presentation (http://www.sambaxp.org/)
> in two weeks. ;-)
>
> Slides, raw data and a full report of the user survey I will publish
> after the conference and announce here on the list, as well.
>
>
> Regards,
> Marc
>