Small Business Server 2003 and NetMeeting Remote Desktop Sharing

I have a client with SBS2003 Premium installed.  I cannot enable NetMeeting Remote Desktop Sharing on their server.  The "Sharing" option and "Remote Desktop Sharing" are both dimmed on the NetMeeting Tools menu.

I also cannot start the Net Meeting Remote Desktop Sharing service on the server.  It says that the service started and stopped immediately.

There are no entries in the event log that refer to the service at all.

I can get to the server using Remote Desktop Connection without any problem, but I need to use NetMeeting so I can see the actual server desktop to be able to provide support.

NetMeeting worked just fine on the same server when it was running SBS 2000, but it has been disabled since the upgrade to SBS 2003.

I have the same environment on three other client servers that I have installed and they work just fine.

Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Enable Remote Desktop from: Control Panel>System>Remote tab>Remote Desktop.

Use Remote Desktop from the client to connect to it.

portdataAuthor Commented:
Reread my question.

I already have remote desktop connection working.

I need to get NetMeeting Remote Desktop Sharing to work on the SBS 2003 server.
Sorry, I misread your question....too many "Remotes" in there!! :o)

Not sure you can do this on a 2003 server.  I think the security to turned up to prevent this.  I will check.

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

portdataAuthor Commented:
I already tried that a few weeks ago when I first found the KB article.

You cannot install NetMeeting on SBS2003 that way.  It comes preinstalled and will only run the bundled version.

FYI, I am a Microsoft Certified Partner specializing in SBS.

I have NetMeeting installed on my own SBS 2003 server and on another client's SBS 2003 server as well.  It works!

This one machine is just different in some way.

I will call MS support if I need to, but I thought I'd give Experts Exchange a shot first.  That usually yields good results and takes less time and costs less.
I agree with you, this should work.  The article mentions only the supplied version of Netmeeting works.

Was this an upgrade from 2000?  I suspect if it was there are some differences in the final result over a clean install.  It would be interesting to figure out just what.

I wasn't questioning your ability in any way, just trying to extract a bit more info from you.

I will continue to help if you still want it.  BTW, check my profile if you're not sure about me.

portdataAuthor Commented:
I didn't mean to suggest that I was insulted in any way.  Nor did I intend to insult you either.

I just wanted you to know who I am, where I am coming from and that I have been around this block a few times and am not a rookie looking to lay off a problem and get it solved the easy way.

I assigned 500 points to the problem because it has me up a tree.

I have installed and maintained more than 25 small business server networks over the past 5-10 years.  I was also a winner of the Microsoft Sweet Success award for SBS 2003 earlier this year.  And, with all of that, I still have this problem that will not go away.

I would welcome any help.  I obviously have not gotten it fixed yet myself - made worse by the fact that I am working on five different projects at once and really need this one to go away.  

It appears that I may have exposed a bug or other problem in SBS 2003.

This was an upgrade from SBS 2000, but so was my own.  And mine works correctly.  When this server was running SBS 2000, NetMeeting worked just fine.  When I completed the upgrade and attempted to start NetMeeting, it would not start.

So, I did the expedient thing at the time - I ignored it and worked around the problem.

But now, my client mentioned that he saw a message on the server about a possible deadlock and I wanted to see the message without driving an hour to get there.  But, only Net Meeting will give me the live desktop view.
For now, why don't you install Tight VNC so you can see the desktop.

In the meantime, we should try to get more info if possible.  When you try to start the Netmeeting service and it fails, are there any events in the Event Logs that get written?

I'd like to see you connect to the server with an XP SP2 box and open ADUC so the .adm files get updated.  Then we can use GPMC to see if there are any GPOs in the Resultant Set of Policies that might have NetMeeting locked down or disabled.

I've seen some companies that specifically disable prevent NetMeeting use - this was setup on OUs using a GPO.  If the server was moved into one of these OUs by mistake then, perhaps, the GPO is applying to the DC when it shouldn't.

Another one I have used is Dameware.
That also gives you the desktop as viewed by the client. As for netmeeting, I don't use it in preferance to this tool, among other reasons.
 As Netman stated, it sounds like a GPO, but I would expect you've looked in the obvious places. Hmmm, what kind of upgrade did you do? An in place upgrade of the DC, or a step upgrade to the OS, then a DCPromo?
If the later, it will take some work. If, for whatever reason, the machines local policy had the setting for netmeeting disabled, then the only way out may be to apply an admin template with the correct settings.
Good Luck!
portdataAuthor Commented:
Ijust checked GP on the server and everything related to NetMeeting was "not configured".

I configured all of the Net Meeting options and updated the group policy (user and computer).  Nothing changed.

I will be at the client site tomorrow morning and will reboot the server.

Let's see what effect that has.

Enough for today!
Good gawd, sounds like enough for a month, at least! I hate those niggly little problems. THey eat me up, too. 8-)
If you want to see the actual desktop, enable remote desktop, then start the client like this:

mstsc /console

That will connect to the actual desktop of the server, allowing you to see what is happening on the screen. It works wonderfully and is how I manage all of my servers. I used to do Netmeeting, pcAnywhere, VPN etc and they have all been dropped in favour of the remote desktop.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Hey, thanks!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.