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.

ClientRemote Installation issue

Updated: 21 May 2010 | 5 comments
Ncaahoopfan's picture
0 0 Votes
Login to vote
Folks:
I am running SSC 10.1.5.5000 on Windows 2003.
 
I have successfully used "tools > ClientRemote Install" to deploy the client-side tools on a few dozen machines (with various XP Pro, Windows 2000 Server, and Windows 2003 Server).
 
I have a one base image that won't let me install the client remotely.  During the remote installation process, I am to find the machine and provide the 'Windows NT Login' information.  However instead of accepting it, I am presented with this error:  "Access to the network resource was denied."  
 
As a test, I purposely mistyped the password and got a different error - so I am sure that I am connecting to the box and authenticating as the local admin.
 
This is definitely a problem on my end, but for the life of me, I can't figure it out.  I have an overzealous self-appointed security whiz on my team who probably disabled something that the installation requires.
 
-- OS is Windows 2000 SP4
-- I added the forceguest DWORD to the 'LSA' license key
-- I have ensured that admin$ and c$ were present
-- I compared started windows services to a working machine - they matched.
 
The error is because Symantec isn't allowed to connect to either the admin$ or c$ -- any thoughts to why?
 
Thanks in advance
- Jeff
discussion Filed Under:

Comments

Kit Fisto's picture
07
Aug
2007
0 Votes 0
Login to vote

Hi:
 
You said you have a base image, I'm thinking you did clone that computers, right? Did you change the SID on each one?
 
Are you trying to authenticate using MACHINENAME\username or DOMAINNAME\username?
Obviously, username has administrative rights on target computer.
 
Are you able to access \\MACHINENAME\c$ from Windows? (For example, typing that on the "Run" box). If you're able to see it, then try the remote setup (and should work).
 
If you're unable, there's something wrong with credentials.
 
Try running "net use * /delete" (without the quotes) from a command line (that will erase any active connection and credentials). After the delete, try again.
 
Hope this helps.
 
Regards.
 
                     ---Carlos.
Katahdin's picture
23
Oct
2007
0 Votes 0
Login to vote

I found that opening "My Computer", "Tools", "Folder Options", clicking on the "View" tab, and disabeling the "Use simple File sharing (Recommended" selection, worked for me (providing the root of the "C" drive was set up for sharing.
ooisk888's picture
23
Oct
2007
0 Votes 0
Login to vote

That's right, the simple file sharing can cause you endless headache.
 
Another problem, Windows XP needs to logon the local system successfully before you can connect to it through (adminstrative) file shares. So if you use a domain administrator account that has never logon to the local system, then you need to resort to using the Administrator account for the local machine.
 
Anyway this is what I have troubleshoot before.
 
 
Cheers
SK
 
Pink Panther's picture
24
Sep
2009
0 Votes 0
Login to vote

Have you checked Windows

Have you checked Windows Firewall on client? It happened to me so.

RickJDS's picture
24
Sep
2009
0 Votes 0
Login to vote

This login prompt comes up

This login prompt comes up for me when the client is offline or has a firewall enabled.