Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 11866 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Endpoint Protection Error 1219 Failed to Connect to Remote Share... Could not add Network Connection

shackbill

Im working on the online Training Endpoint Protection Lab (Part 4 Remote CID) and created a folder named SophosUpdate, created a share called SophosUpdate2, and assigned Read/Write Share and Full Control NTFS as instructed.  I added the share to the Ditribution in Config Update Manager and then entered the username/password. Then Update Now. I get the following error:

5/15/2014 7:56:05 PM	Error	Deployment to share '\\METROEASTSERVER\SophosUpdate2\CIDs\S000' failed to connect to the remote share with error 'Could not add network connection to \\METROEASTSERVER\SophosUpdate2; user SophosUpdateUser A Windows API call returned error 1219'.

 All other entries in the log are Success. There are no CID or Warehouse folders/files in the folder/share i created.  I double checked username and password and did this whole thing twice with same results. Any ideas please?

shareperms.pngshareperms.png

:49910


This thread was automatically locked due to age.
Parents
  • 0
    One more hint (split into several parts):
    1219 is a standard Windows error - using just 'windows error 1219' didn't bother me with RPC among the top hits
    SUM runs in fixed user context
    You can trick the "local" API (actually server and client are identical) with an alias - for the price of additional complications on the server side ;)
    The path/share is different - the server is what counts and this is the same
    Did I say that aliases complicate things?

    I'm not teasing you - try to see the whole picture. Simple "solutions" are for untrained monkeys. It's not even lateral thinking that's needed. I do think you've created a problem which isn't one. Think about it.

    Christian
    P.S.: if you have questions you don't want to disclose to the public you can send me a PM


    :49942
Reply
  • 0
    One more hint (split into several parts):
    1219 is a standard Windows error - using just 'windows error 1219' didn't bother me with RPC among the top hits
    SUM runs in fixed user context
    You can trick the "local" API (actually server and client are identical) with an alias - for the price of additional complications on the server side ;)
    The path/share is different - the server is what counts and this is the same
    Did I say that aliases complicate things?

    I'm not teasing you - try to see the whole picture. Simple "solutions" are for untrained monkeys. It's not even lateral thinking that's needed. I do think you've created a problem which isn't one. Think about it.

    Christian
    P.S.: if you have questions you don't want to disclose to the public you can send me a PM


    :49942
Children
No Data