We have SBS 2003 R2 domain controller and also a 2003 R3 as a backup and this is the box which runs additional tasks such as the antivirus console etc...
I have followed a couple of guides on how to setup a group policy and change settings on the server so that I can offer remote assistance. The idea being that I can VPN into the network and then connect to the server using terminal services and then use remote assistance to fix any problems with the machines remotely.
However when I enter the machine name to connect to and try and connect I get an error "Automation server can't create object".
I can connect directly to the admin share on the client and I am logged into the server as a domain admin.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The firewall on the server is not running.
Firewall exclusion are set on the clients as part of a group policy and defined in this article - http://support.microsoft.c
I did try opening tcp port 3389 but it made no difference.
I found this :-
http://www.ditii.com/2007/
It appears to be the problem I am experiencing as its the same error I get in the event log.
Do you know of a way to get it working from a server 2003 machine?
Telneting to that port didnt work straight away but I dont think anything is listening on that port until the initial DCOM connection is established.
I opened up remote desktop on my client and then could telnet to the port but still got the same error on the server.
I have applied group policy settings to enable remote desktop on the clients and if I can get that working and connect to the users console that may be an alternative but I dont know if that is possible unless I log in as them.
I will need to setup another machine as a test client to progress furthur. Using terminal services to connect to the server and then connect back to my machine made my machine very unhappy and I had to press the power button to get it to shut down LOL.
Running netstat -an will list the ports.
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
This will appear on the client machine.
Remember that other ports are used in the outbound connection (example of two I have connected at present)
TCP 10.x.x.18:2214 10.x.x.30:3389 ESTABLISHED
TCP 10.x.x.18:2307 10.x.x.163:3389 ESTABLISHED
When I tried the telnet it connects first time.
Re-running the netstat command shows the new entry along with my others above.
TCP 10.x.x.18:3389 10.x.x.30:3235 ESTABLISHED
I couldnt get this working so in the end I used GSVNCJ (http://vncj.com/default.a
Business Accounts
Answer for Membership
by: WimDLPosted on 2009-06-18 at 04:44:13ID: 24656426
is port 3389 opened in your VPN environment and on the SBS server? If this port is blocked anywhere between your remote pc (included) and the sbs server (included), then RDP won't work.