MMC snap-in frustration: managing a pc remotely

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hi All! My name is X and I'm frustrated ...I have to learn for MCSA because of my work. I hold other non-MS certs but this one gives me headaches, I'm clueless and can't find the answer on my own.

My trouble is I'm learning for 70-290 and I can't get past the lesson where it tells you how to remotely administer pc's using a snap-in. I simply can't get it right.

My setup is one server running w2k3 ent sp2 and one client running xpsp2 both hosted on vmware. I don't have any domains set up, I have the same account names on both systems, belonging to the same groups and having same passwords.
On XP I'm running windows firewall but an exception has been set so It can accept incoming DCOMs. The pc's can fully communicate with each other but obviously I'm missing something since every time I try to access something remotely through a mmc snap-in (for example remote managing device manager on xp) I get either an Access denied message or other errors depending on the resource I want to access. (for example 'Unable to open service control manager database on xxx.xxx.xxx.xxx Error 5: Access is denied.")
If I try to open the mmc console logging with a user name on the remote system it opens the console but I'm still unable to access remote resources.

I'm clueless. I have to admit I come from a Linux background and this stuff is new to me.

If it would be possible could I get some step by step info on how YOU would set up this to work?
I've checked other forums but got ambiguous answers as if I should already know this and that.

Your help is very much appreciated.
A million thanks in advance!

 

If I do that I'll get a "No network provider accepted the given network path" error.
If I try to do the same but with an IP address, I get the logon screen but user name is set to Guest and is grayed out, thus can't be changed.

If I try to access the server from XP with either IP or computer name it works, even without prompting for a password.

It's a mess, isn't it?
What could be wrong?

 

csh,

I think that's your problem.

 

Nope
Disabling windows firewall on the client site allows me to ping it with its name but still doesn't solve my problem managing the computer through a mmc snap-in such as computer management. I still get access denied errors.

Any other clues?

 

r.h.lee, wow! could that be the problem? If so the MS Press I'm learning from has serious flaws because it doesn't mention that.
More than that, it tells me to add an exception for DCOMs in windows firewall on the remote system for either local policy or domain if computer is member of a domain.

 

csh,

Which MS Press book are you using?

 

Thanks!
I could successfully map a remote drive but I still can't access anything from the mmc

 

r.h.lee, I'm trying to learn from " MCSA/MCSE Self-Paced Training Kit (Exam 70-290): Managing and Maintaining a Microsoft Windows Server 2003 Environment, Second Edition - that's a Microsoft Press release.

 

Sparky,

Accesing resources because of authenticated permissions and managing a computer are slightly different. Through computer management, you can configure the computer to be a DNS server, an IIS server, an SQL server, and so on. Can you do that through simply authenticating your login into your user account on a remote computer? That's why it's a little different from each other.

 

No, I got straight connected, without the need to enter any user or password.
Maybe because I have the same accounts on both systems with same passwords and belonging to the same groups?

However, that's not my concern at this point...

 

How can I tell? I'm only seeing one group of administrators on both systems and these users are part of it.

 

Yes it is, on both systems. I also tried the mentioned workarounds from your link and still didn't work
I even disabled windows firewall...still the same thing.