Re: Remote desktop connection to workstation



What permissions do you have on the following folder? (Specifically I'm
looking for the Local Service and Network Service having full permission to
that folder )

\%systemroot%\microsoft.net\fr­amework\v1.1.4322

--
Merv Porter [SBS MVP]
===================================
"Aaron Hoffman" <AaronHoffman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC61ECFB-491E-4391-BAC1-AEBFDFB735AE@xxxxxxxxxxxxxxxx
> Well, I'm unable to access the internal web site (companyweb) from the
> internet, however I can access it directly from the server using the
> browser. When I attempt to access RWW using https://<servername>/remote
> from
> both the server itself and another computer I recieve the "Parser Error"
> as
> mentioned previously.
>
> Aaron
>
> "Merv Porter [SBS-MVP]" wrote:
>
>> Tell us a little bit about your network configuration.
>>
>> Are you hosting a public web site on the server?
>>
>> On another workstation (one that still has port 3389 as the default), can
>> you access RWW using https://<servername>/remote
>>
>> --
>> Merv Porter [SBS MVP]
>> ===================================
>> "Aaron Hoffman" <AaronHoffman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:13A78F29-F752-495B-8099-60AD216EBD36@xxxxxxxxxxxxxxxx
>> > 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: Windows 2003 Server - Everyone Group
    ... this folder only accessable by the users in the "special" group. ... Configure User and Group Access on an Intranet in Windows Server ... NTFS files system permissions control ... group that you want to set permissions for, click Check Names to verify the ...
    (microsoft.public.win2000.networking)
  • Re: Office Docs wont Open? and BU Drive not Recognized?
    ... Create a new Folder: ... On the server share... ... SHARING tab | Permissions | Share Permissions | Group or User Names ... If I copy the document to the local Client, the document opens ...
    (microsoft.public.windows.server.sbs)
  • Re: enableSessionState Error in /Remote
    ... Check permissions on the following directory. ... It's possible the Network Service account doesn't have the needed ... Check to see that the Local Service and Network Service ... Everything is standard except the DHCP server which is on a Seperate> box. ...
    (microsoft.public.windows.server.sbs)
  • Re: An NT Security Gotcha that looks like a Jet Security issue
    ... >people remotely via Windows Terminal Server. ... >code when it was run by a user that didn't have full permissions on ... There's a top-level DATA folder, ... >ApplicantsDB and Quickbooks. ...
    (comp.databases.ms-access)
  • Re: Exchange Move Issues?
    ... I'm a bit confused on what permissions to assign for SBS, ... When you finish moving the databases, ... You can move the log files and database files to any folder that you want to ... Note Only assign permissions to the Server Operators group if the Exchange ...
    (microsoft.public.windows.server.sbs)