Doug.
Unfortuanetly that doesn't help, it still won't open up the application but
ONLY logging in via Remote Desktop.
I can physically sit at the server, log in as the same user, and it works
without fail. I log in via Remote Desktop, use the exact same user, it will
not open.
Any other idea's would be more than welcomed!
Thanks,
Julie
"Doug Sherman [MVP]" wrote:
> RAS refers to remote access - generally by direct dial up or VPN. I assume
> you are talking about Remote Desktop. Try this:
>
> On the Windows 2003 machine, go to Administrative Tools and open Terminal
> Services Configuration. Right click on RDT-Tcp and select Properties.
> Click the Permissions tab. Check the Administrators group and make sure it
> has full control. If this group is not listed, add it. Use AD Users and
> Computers (or Computer Management if you do not have a domain) to remove the
> user account you log in with from Remote Desktop Users. By default Remote
> Desktop Users have only user level access - Administrators have full
> control.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
>
> "JetCityJules" <(E-Mail Removed)> wrote in message
> news:9B4EBB6A-9541-49CB-B395-(E-Mail Removed)...
> > I have setup a Win 2003 Server, enabled Remote connection, and I can
> actually
> > log in and see everything, but I'm having a problem opening up an
> application.
> >
> > If I'm physically sitting at the Win 2003 machine logged in as
> > Administrator, the application opens without any problem, however, when I
> log
> > in via Remote the application will not open.
> >
> > I do know that the application needs to have access to the Win registry,
> and
> > I suspect that there are some limitations to the registry if I'm logged in
> > remotely, but I don't know this for sure, and I can't really find any help
> > online about it. Any assistance would be appreciated.
> >
> > Thanks,
> > Julie
> >
>
>
>
|