Re: Help with Remote Desktop, Terminal Services
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 09 Dec 2006 05:03:18 -0800
see my 2 replies to your other posts in this thread.
You are running SBS, so you don't have Terminal Services at all.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
bweaverusenet@xxxxxxxxx wrote on 08 dec 2006 in
microsoft.public.windows.terminal_services:
More info..
This is really strange. This morning I connected to the server
over VPN from another network and tried Remote Desktop -- it
worked. I tried tsweb -- it also worked. I mapped a network
share and that worked. Excellent. But...
Double-checking, I closed the connections and began again. VPN,
then RD. "client could not connect to the remote computer."
Tried tsweb "you are not authorized to view this page" http
403.6. Tried my admin id, tried a user's id and neither worked.
So I would guess this means (a) it isn't a firewall issue since
it worked once (I have ZoneAlarm installed and told it to allow
RD), (b) it isn't a licensing issue, since I did get access this
morning through both RD and tsweb.
Does this help narrow it down? Any more suggestions? I'm
perplexed.
Thanks for the ideas so far.
bweaverusenet@xxxxxxxxx wrote:
Hi. I need some help setting up Remote Desktop correctly.
Our church has no building at the moment, and several people
must work remotely. I have set up a Windows Server 2003 system
on my home network for them to access remotely. I have set up
VPN for them to connect and map network shares. This seems to
work (except for the VPN Connect dialog periodically popping up
and asking for the remote user's password again).
There is a software package installed on the server that they
need to run via Remote Desktop. I had this working 9 months
ago. In testing, people could connect via VPN, map drives,
remote to the server, run the app, and all was well. Though it
worked, a critical person could not get broadband until
recently so this configuration sat idle.
Now, however, they're trying again and getting errors. People
who could access before were getting "You do not have
permission" to access http://ourserver.dyndns.org/tsweb. Once I
added their IP to the tsweb directory security list, they got
to the Remote Desktop entry page but after entering the server
name, screen size, and clicking Connect they got something like
an "Unknown server" error. I've been mucking about with various
security group combinations, permissions, etc. and need some
help.
What's the best way to get tsweb up and running for remote
users? What is Remote Web Workplace and would it be more
appropriate for this situation?
Thank you. -bill
- References:
- Help with Remote Desktop, Terminal Services
- From: bweaverusenet
- Re: Help with Remote Desktop, Terminal Services
- From: bweaverusenet
- Help with Remote Desktop, Terminal Services
- Prev by Date: Re: Help with Remote Desktop, Terminal Services
- Next by Date: Re: RDP suddenly stops
- Previous by thread: Re: Help with Remote Desktop, Terminal Services
- Next by thread: Windows hangs
- Index(es):
Relevant Pages
|