Re: Remote desktop connection to workstation

Merv,

I do understand what you are saying. I wouldn't say we're trying to
"workaround" the RWW problem. I didn't attempt to use RWW until I discovered
that the RDC wasn't working. It would be nice if we could get the RDC to
work, but if you don't think thats possible, thats okay. The error that I am
getting when trying to access RWW is:

Server Error in '/Remote' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to
service this request. Please review the following specific parse error
details and modify your source file appropriately.
Parser Error Message: Could not load type 'remote.Global'.
Source Error: Line 1: <%@ Application Codebehind="Global.asax.cs"
Inherits="remote.Global" %>
Source File: c:\inetpub\Remote\global.asax Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032

Do you know how we can fix this error?

Thanks,
Aaron

"Merv Porter [SBS-MVP]" wrote:

> Well, you can use a straight RDC connection but RWW is more robust and a bit
> more secure becuase of the way it implements an RDC session. Also, if RWW
> doesn't work, other things on your SBS may not work either (although you
> might not have encountered other problems "yet"). Best to get SBS working
> properly than to try to establish a "workaround".
>
> That said, what is the exact text of the "Parser error" that you're getting?
>
> --
> Merv Porter [SBS MVP]
> ===================================
> "Aaron Hoffman" <AaronHoffman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:ECA1F2D9-07D0-42A9-A081-E7FC395348ED@xxxxxxxxxxxxxxxx
> > Merv,
> >
> > The reason that I was trying to work around the Remote Web Workplace was
> > because I'm recieving a "Parser Error" when going to:
> > https://<WAN_IP_Address>/remote. Is it possible to connect to a
> > workstation
> > using the Remote Desktop Connection? To my understand, when you use the
> > "Connect to my computer" in RWW it is connecting the same way as remote
> > desktop connection. The reason that I changed the individual port number
> > on
> > the workstation was so that I can use the ip address of the computer
> > followed
> > by a colon and the port number, ie. 192.168.0.101:3390. If I need to
> > connect
> > to another workstation, I can then change its default port so that I can
> > connect directly without interfering. By using the Remote Desktop
> > Connection,
> > it is much easier and faster to connect, but if the only way we can get
> > through is the RWW then I suppose that is what we will have to do.
> >
> > Aaron
> >
> > "Merv Porter [SBS-MVP]" wrote:
> >
> >> Aaron,
> >>
> >> Instead of Remote Desktop Connection, I think you mean Remote Web
> >> Workplace
> >> (RWW). Correct me if I'm wrong.
> >>
> >> There's no need to change the default port on the workstation from 3389
> >> to
> >> 3389. Change it back.
> >>
> >> Configure the network per the following diagram:
> >> http://www.smallbizserver.net/Default.aspx?tabid=154
> >>
> >> Turn off DHCP on the router.
> >> Assign the external SBS NIC a static IP in the same subnet as the router
> >> (as
> >> indicated in the diagram)
> >> Re-run CEICW (including enabling the firewall and selecting the services
> >> you
> >> want). If you don't have a domain name, use the static WAN IP address of
> >> the router when you configure the Web Server Certificate.
> >> Then try to access the workstation via Remote Web Workplace from an
> >> external
> >> computer using: https://<WAN_IP_Address>/remote
> >>
> >>
> >> --
> >> Merv Porter [SBS MVP]
> >> ===================================
> >>
> >> "Aaron Hoffman" <Aaron Hoffman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> message
> >> news:78020A0F-03C6-4EA4-A6D9-A23F734C10B9@xxxxxxxxxxxxxxxx
> >> > Hi,
> >> > We have Windows Server 2003 SBS and want to use Remote Desktop
> >> > Connection
> >> > to
> >> > access a Windows XP Pro workstation that is behind the server. I
> >> > believe
> >> > the
> >> > network configuration is causing some problems. We have a DSL (static
> >> > ip)
> >> > connection coming into the office which then runs into the router. The
> >> > router
> >> > then issues an IP address to the SBS server on the external NIC
> >> > (network
> >> > interface card). Each workstation is connected to the server through a
> >> > switch
> >> > and the server-side DHCP issues each workstation an ip address. I am
> >> > able
> >> > to
> >> > access the server via the static ip connection, but it cannot find the
> >> > workstation. In addition, I changed the default port of 3389 on the
> >> > workstation to 3390 so that it would not be confused with the server. I
> >> > did
> >> > open the port on the router as well. From inside the network, the
> >> > workstation
> >> > can be accessed, but we cannot connect remotely. Maybe there is some
> >> > other
> >> > setting that needs to be configured. Is it possible that we cannot
> >> > access
> >> > the
> >> > workstation because the router and the fact that we have 2 NIC's on the
> >> > server? It seems that there has to be some way for us to get around
> >> > that.
> >> > I
> >> > appreciate any help that you can offer. Thank you, Aaron
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Remote desktop connection to workstation
    ... On another workstation (one that still has port 3389 as the default), ... I didn't attempt to use RWW until I ... >>> using the Remote Desktop Connection? ...
    (microsoft.public.windows.server.sbs)
  • Re: Bypass SBS server and Connect directly to workstation ??
    ... RWW and 'connect to my computer' is not everything to everybody, ... Les Connor [SBS Community Member - SBS MVP] ... > workstation you have permissions for, ... >>> changing the listening port affect Connecting via Remote Web Work ...
    (microsoft.public.windows.server.sbs)
  • RE: =?Utf-8?Q?RE:_Pre-RWW_setup_user_accts_can?= =?Utf-8?Q?=E2=80=99t_log_in?=
    ... This newsgroup only focuses on SBS technical issues. ... | All users are members of the "Remote Web Workplace Users" group. ... | All users were created using the SBS Add User Wizard before RWW was ... I understand the issue to be: the user accounts ...
    (microsoft.public.windows.server.sbs)
  • =?Utf-8?Q?RE:_Pre-RWW_setup_user_accts_can?= =?Utf-8?Q?=E2=80=99t_log_in?=
    ... All users are members of the "Remote Web Workplace Users" group. ... All users were created using the SBS Add User Wizard before RWW was ... User accounts created after RWW implemented were created using the ... SBS Add User Wizard and work correctly. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Web Workplace only works for Administrator
    ... They need to be members of the Mobile Users Group and the Remote Web Workplace Users Group. ... Close port 80 on your router - you don't need this open unless you are running a web server on your SBS box and if youare, then don't - get it hosted externally. ... Might be a good idea to close 3389 too - if you get RWW working, users can logon to their workstations this way instead of directly through the RDP port. ...
    (microsoft.public.windows.server.sbs)