Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Remote Client Authentication Fails On Install Package Push

Updated: 21 May 2010 | 5 comments
OIStaff's picture
0 0 Votes
Login to vote

Hi.

I'm attempting to push out a client install package on this network (SBS 2003 Active Directory) from the SEPM machine - the machine is part of this domain.

When I go to push I'm prompted with a Remote Client Authentication box.

When I enter the creds, I get the following messsage:

Mulitiple connections to a server or shared resource be the same user, using more than one user name, are not allowed.  Disconnect all previous connections to the server or shared resource and try again.

This message is only thrown when pushing to the SBS 2003 computer.

Help appreciated.

discussion Filed Under:

Comments

OIStaff's picture
31
Oct
2009
0 Votes 0
Login to vote

Also.  This install is part

Also.  This install is part of a dual boot installation.

It seems that this push is trying to access the admin share?  In this case, I have three admin shares - c$, e$ and f$ - f$ is where the sbs 2003 install resides.

not sure if this matters but just in case.

OIStaff's picture
31
Oct
2009
0 Votes 0
Login to vote

and ... no matter what i

and ... no matter what i enter in the auth box i get that same message.  its like it's not even verifying the creds.

Rafeeq's picture
31
Oct
2009
0 Votes 0
Login to vote

Hi

Hi Olstaff,

Please find this document yest C$ should have access

Error: "No Network Provider accepted the given network path" when using ClientRemote Install to deploy clients

http://service1.symantec.com/SUPPORT/ent-security.nsf/ppfdocs/2005062312163948

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

OIStaff's picture
31
Oct
2009
0 Votes 0
Login to vote

Rafeeq Found this. 

Rafeeq

Found this.  http://support.microsoft.com/kb/938120  this article was referenced in a MS post by a Symantec SBE 12 tech.  He had this same problem.

This is more what the issue seems to be.

What I don't get here is from my XP client, when I use Start\Run and try to browse to the admin shares on the server via \\servername\e$ i get the same error reference here.  but if i enter \\192.168.16.2\e$ i get in after supplying credentials.

Not sure why this is.

Odd thing here

Prachand's picture
31
Oct
2009
0 Votes 0
Login to vote

else what you can do instaed

else what you can do instaed is just copy the exe and run it on the machine locally , it will install SEP and also the client will be managed.
Even you can share the exe and run it locally

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)