VBScript: Remote Desktop Disconnected

oscar_cisco10

unread,

Sep 11, 2009, 10:32:02 AM9/11/09

to

Hi Guys,

Would some one give me some advice if you already encountered this error in
RWW in SBS 2008. RWW is working fine, I can login in the RWW with no problem.
I can even rdp to any client workstation with no problem; however when i try
to rdp to the domain controller; it prompted me a vbscript error. Please
refer below exact error:

An internal error has occured (error 50331675). For more information contact
your network administrator or Microsoft Product Support.

I can connect to the domain controller before with no problem. I made some
research but to no avail of solution with error 50331675. I only found
solution for error 50331676. What about error 50331675?

A big thanks for those who will give their experts advise.

Thank You,

Oscar

Robbin Meng [MSFT]

unread,

Sep 14, 2009, 5:42:42 AM9/14/09

to

Hi Oscar,

Thanks for your post.

I didn't find the information about "error 50331675" , but it is similar to "error 50331676". First, I would like to know if this issue occurs to any users(including Domain
Administrator or DC local Administrator) you used to RDP to the DC server? Or just occurs to normal domain users?

I would like recommend you a web article which lists the general root causes and suggestions:

VBScript: Remote Desktop Disconnected
http://chicagotech.net/sbs/rwwvbscript11.htm

Note: The third party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change
without notice. Microsoft in no way guarantees the accuracy of this third-party contact information.

Another similar thread:

RWW VBScript Error: An internal error has occurred
http://forums.techarena.in/small-business-server/543057.htm

Hope this helps.

Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================

oscar_cisco10

unread,

Sep 15, 2009, 2:35:01 PM9/15/09

to

Hi Robbin,

All the accounts in RWW were fine. No problem rdp to any workstation; only
rdp with the server via RWW. The links below were checked and tested but did
not fix the issue. error 50331675 - I havent found any solution for this; i
only just seen error 50331676 which is a certificate issue. I dont have any
certificate issue with the server. i really appreciate for helping me with my
problem.

Thanks,

Oscar

Jason

unread,

Sep 22, 2009, 1:34:01 AM9/22/09

to

I'm having error 50331675 come up. Can you please let me know if you find a
fix.

Signal

unread,

Sep 23, 2009, 8:20:13 PM9/23/09

to

I am having the same error. Is this recent problem as I don't see many posts
on this error code?

All suggestions welcome!

Jason

unread,

Sep 24, 2009, 12:09:02 PM9/24/09

to

I was using SBS 2008.

To fix the problem I removed the Terminal Services Gateway Role, rebooted
then re-installed the role. During the installation of the Gateway role you
will be prompted with some options. I chose to allow access to all machines
on the network and also added domain users in the allowed list. Everything's
working fine now.

Jason

Signal

unread,

Sep 24, 2009, 2:04:02 PM9/24/09

to

Somtimes, things are so simple that we forget to look at the obvious....
thanks.

Worked for me too, same set up.

Robbin Meng [MSFT]

unread,

Sep 28, 2009, 3:50:13 AM9/28/09

to

Hi,

Sorry for not responding earlier. I was on vacation and just come back today.

Thanks a lot for your attention and the great sharing on this issue. Oscar, have you tried Jason's work round and does it fix your issue?

Thanks for your time and efforts.