Jump to content


rjayblue83

Connection Error SMSTS Log

Recommended Posts

We are having an issue where after imaging the user tries to log in and sees the "No logon servers available error". The machine is joined to the domain, and is in AD. When looking at the SMSTS log, we are seeing the below errors. We are not seeing any issues with our servers and this is only happening at a couple sites and for only one model. We can image this model fine at our primary site. Any ideas?

 

socket 'connect' failed; 8007274c TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
hr, HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
sending with winhttp failed; 80072ee2 TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
End of retries TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
Send (pReply, nReplySize), HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052) TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
failed to send the request TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
DoRequest (sReply, false), HRESULT=80072ee2 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835) TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
Failed to send status message (80072ee2) TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
smStatusMessage.Send(), HRESULT=80072ee2 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\utility.cxx,529) TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)
Non fatal error 0x80072ee2 in sending task sequence execution status message to MP TSManager 5/12/2014 9:52:47 AM 3572 (0x0DF4)

 

 

Share this post


Link to post
Share on other sites

Both of those issues sound like networking issues... 80072ee2 is a timeout and No logon servers available is usually an indication that it cannot connect with the domain controllers... Are you sure there is nothing driver with the networkdrivers or the networklayer between the client and server?

Share this post


Link to post
Share on other sites

Did you check the DC for a login from the client or the network routers/switches to ensure that they are assigning an IP (assuming DHCP)? If nothing else login locally on the client and see if you can see the network from there - maybe you have a network or firewall rule that is blocking the client to DC communication?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.