Unable to workplace join IOS - Windows 8.1 ok


i have 2012r2 , wap/adfs working nice, can wpj 8.1 client no problem, ios device wont install profile saying unable connect server, here logs device.

all urls reachable fine devices, trusted public cert enterpriseregistration on upn also, ideas?

jul 16 10:06:52 martins-iphone profiled[39] <notice>: (note ) mc: enrolling in ota profile service...
jul 16 10:06:52 martins-iphone profiled[39] <notice>: (error) mc: failure occurred while retrieving profile during ota profile enrollment: nserror:
desc   : connection server not established.
desc: connection server not established.
domain : mchttptransactionerrordomain
code   : 23001
type   : mcfatalerror
params : (
"https://sts.domain.com/enrollmentserver/otaprofile/profile?operation=enroll",
400
)
jul 16 10:06:52 martins-iphone profiled[39] <notice>: (error) mc: installation failed. error: nserror:
desc   : profile installation failed
sugg   : connection server not established.
desc: profile installation failed
sugg: connection server not established.
domain : mcinstallationerrordomain
code   : 4001

thanks mark, helps if point trace file :)

i'm getting this:

</computer></system><applicationdata>url https://localhost:49443/adfs/services/trust/mex threw exception underlying connection closed: unexpected error occurred on send. system.io.ioexception: unable read data transport connection: existing connection forcibly closed remote host. ---&gt; system.net.sockets.socketexception: existing connection forcibly closed remote host&#xd;&#xa;   @ system.net.sockets.networkstream.read(byte[] buffer, int32 offset, int32 size)&#xd;&#xa;   --- end of inner exception stack trace ---&#xd;&#xa; 

port 49443 doesn't seem responding @ all, need see if needs config in iis.

there details of usage of port , drs here:

http://technet.microsoft.com/en-us/library/dn486819.aspx

device registration service (drs) in windows server 2012 r2 operates on port 443; clienttls user certificate authentication operates on port 49443

  • for active, non-browser clients using certificate transport mode authentication hard-coded point port 443, code change required continue use user certificate authentication on port 49443.
  • for passive applications no change required because ad fs redirects correct port user certificate authentication.
  • firewall ports between client , proxy must enable port 49443 traffic pass through user certificate authentication.

see also:

http://windowsitpro.com/windows-server-2012-r2/certificate-authentication-windows-server-2012-r2

have got port 49443 open on firewalls?

mark.



Windows Server  >  Windows Server 2012 Setup



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client