We help IT Professionals succeed at work.

Remote Control Agent Error: Connection Failed (0x800401e4)

ssiimmppllee
ssiimmppllee asked
on
I have a client pc that I cannot connect to using Remote control through the SCCM console.

When I try to start the tools I receive a pop window that states Connection Failed (0x800401e4)

* I can connect to the pc using SCCM Remote assistance
* I can connect using RDP from the run window (mstsc)
* I did reinstall the client both from the console as a push. And locally at the computer.
* I removed the pc and rejoined the domain

When this first started the client pc did have com errors in the event log. These errors would have pointed to an older version of MDAC. But I did confirm that the version was correct. However, after I removed the pc and rejoined the domain the com errors went away. But here is the error just in case it helps.
Event Type:      Error
Event Source:      COM
Event Category:      None
Event ID:      10013
Date:            1/24/2008
Time:            9:48:35 AM
User:            N/A
Computer:      PC9599
Description:
DCOM server attempted to listen on an invalid endpoint. Protseq:  ncacn_ip_tcp Endpoint: 2701 Flags:    0x0

This is the only error that I could find in event logs.


I dont know which SCCM log file I should check if someone could help me with that too.

Comment
Watch Question

would you care to try teamviewer ?

can you connect using the sccm and others or not or witherrors ?

Author

Commented:
Thanks for the reply. Our design is to use the SCCM tools and not third party at this moment.

I'm not sure what you are asking in the second part of the question.

We can connect via SCCM using remote contoll, we can connect useing RDP,

We can not connect using SCCM remote tools. And this is what I need help with. There are no errors in the eventlog. When I try to connect using remote tools nothing happens inthe remotecontroll log.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2633642&SiteID=17

http://myitforum.com/cs2/blogs/socal/archive/2007/03/12/sccm-2007-how-to-site-configuration.aspx

http://www.myitforum.com/forums/Can_SCCM_remotely_execute_task%3F/m_172296/tm.htm

the above links are somthing to try helping about the sccm .. anyways

.. i am assuming your configuration is all ok.

so you need to post about your networking , ports , isa , firewall ...
Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
Have you got any other remote takeover software installed already on that client? For example, the Landesk software or dameware mini-remote services clash with the sms takeover software

Keith
waiting for your reply
Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
Smart_Man

I expect the asker is in bed and it is now the weekend.... You mau not hear anything till next week :)

Author

Commented:
Thanks for the posts everyone.

We are not using anythird party remote tools. But I will check this closer on this station in case the user did allow a vendor to take remote with a seperate tool.

This one is odd and escapes me because the image on the desktop and all hardware is identical throughout. And there are no issues like this anywhere else. Granted we are in the early stages of deploying both XP and SCCM. We have deployed approx 300 stations and they all work. We are using the XP Firewall in our enviroment allong with our hardware devices. but have set the needed ports in the GPO.

Smart_Man I am revieing the links you posted now and will let you know either way.

Author

Commented:
Smart_Man the links are not fitting my issue. I am going to check with the user to see if she recieved support from a vendor.
okay. :) waiting for your reply. hope we can assist .

Author

Commented:
Well, that was a dead end. There has been no third party support apps deployed to this pc. Any other ideas?
Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
Can you verify the sms/sccm agent is deployed/service is started? use the psexec tool to check or use the 'manage' option from the desktop - (right-click my computer icon) -  and select her computer from the list.

Can you rdp onto the box?

Author

Commented:
Yes the services are started. I can perform all functions except for remote tools. RDP works, and so does Remote tools.
looks like you need to double check the services / rights(permmissions, and if you include more info about how exactly you are trying to connect
Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
Does either the sccm or the scom consoles show any issues when the tools/agents were deployed?
Can you remove the agents and then redeploy them?
Anything is the users event log regarding the deployment?
Has the user got their local firewall enabled but without the exception for scom/sccm?
Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
As a side item, about the portmapper.... In brief, winsock-oriented applications can use any port they like to establish connections although normally they are above the well-known-port area and start oabove 1023. The port mapper service simply tells the clients (when they ask) what port to use. If you rebooted your server, the port mapper may identify a different port for everyone to use.

The initial error you mentioned means that the client could not establish a connection to the port mapper to identify the port number to contact it on.  Similar to dhcp and wins or dns really. You could get a different ip address on each reboot but the wins table/dns service keeps your ip and machine/name together for others to find. Port ,mapper does the same but with services and port numbers.

Keith

Author

Commented:
Services / rights look right. I have compared them to a working client.

I have tried two ways to connect.  

1. Through the SCCM console, right click on pc, Start, Remote tools
2. Launch RC.exe, enter IP address of pc.

Does either the sccm or the scom consoles show any issues when the tools/agents were deployed?
We are not monitoring desktops with SCOM and the Server shows no errors.
The logs on the agent show a successful install of the tools.

Can you remove the agents and then redeploy them?
I tried this and am still having the same problem. I deployed the agent from the SCCM console; I also installed it locally on the desktop.

Anything is the users event log regarding the deployment?
Logs show a success.

Has the user got their local firewall enabled but without the exception for scom/sccm?
The local firewall is enabled. But the exceptions are being pushed through GPO. I confirmed that they are all set correctly.

I am not familiar with the portmapper. Is there a way to trace the activity?

Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
netstat -an on the client should give you a list of established connections. You may want to compare this with a working user's machine

Author

Commented:
Some more info

I just repaired WMI by clearing the repository and reinstalled the agent again.

When I tried to launch remote tools the first time after this I was prompted to enter a username, domain name, password. I did so and it failed. After this I receive the same error as before without being prompted for authentication.
Keith AlabasterEnterprise Architect
CERTIFIED EXPERT
Top Expert 2008

Commented:
what is the result of the netstat?
waiting for your reply

Author

Commented:
Sorry group, I was out of the office. I need to wait until I can have access again to this pc. Our packging group has also inserted themselfs to find out if a recent app is conflicting with remote tools. I will keep you posted.

Author

Commented:
I found the problem. And I am a bit embarrassed at what it was.

The effected clients were located at the second site. I found that the "Remote Tools Client Agent Properties" were not the same at the second site as at the primary site. I copied the settings for Remote Tools from the Primary site to the Secondary site. This resolved the problem.


Thanks for all your help on this.
I am closing this as the accepted solution being

The effected clients were located at the second site. I found that the "Remote Tools Client Agent Properties" were not the same at the second site as at the primary site. I copied the settings for Remote Tools from the Primary site to the Secondary site. This resolved the problem.


I am splitting the points because all your suggestions helped me to eliminate the all other possibilities.