Re: vpn to server then remote desktop to client

The server does not have any registered domain name that points to its ip
address so I tried http://ipaddress/remote and https://ipaddress/remote with
the same result. After three attempts to logon as Administrator I got an
error page telling me to modify web.config to get a detailed error
description. When I did that i got...

Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
ASP.NET Files\remote\3f1585d2\3070828a" is denied.

"Cris Hanna [SBS-MVP]" wrote:

There are numerous books on the subject in the public domain which cover
all this and SBS 2003 has been out for 4 years

RWW access should already be in place, if you ran the CEICW wizard
From a browser you simply type what ever you type for vpn to the server
ie http://mail.domain.com and then follow it with /remote
so http://mail.domainname.com/remote

Logon with your user name and password (preferably one with Admin
priviledges) and then click on link to Connect to Desktop Computers
It will do an ActiveX install and then show a list of the desktops

Click on the one you want, click on Connect button...
Pretty simple really.

But if you can't get to them this way....post back and well see what we
can come up with
"tricky300" <tricky300@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5E135533-5D3D-4D10-A9FD-A9E29F283030@xxxxxxxxxxxxxxxx
OK Larry/Cris. I am convinced that at some point in time RWW is worth
investigating and maybe even implementing. Right now however I have more
pressing demands on my time not least of which is the problem that this
post
is about.

Some MS users/MVPs may have the luxury of comprehensive education before
being let loose on MS products. Many in the real world (myself included)
do
not. As a result we end up being crisis driven through no fault of our
own.
We also end up having to teach ourselves, again through no fault of our
own.

This method (originally via terminal services client) is the method that
I
have historically had to use going back to previous versions of SBS to
administer the servers. It is only relatively recently that I have
discovered
that it can also be used to administer clients too. It works on two of
the
servers but not on the other.

Can you help me with my problem or is your only suggestion to get
educated
on RWW?

"tricky300" wrote:

> Hi,
>
> Thanks in advance to anyone who can help.
>
> I administer several SBS2003 servers remotely. 2 of them are
'standard' the
> other is 'premium'. I am having trouble with the 'premium' server that
I am
> not having with the others though whether this is down to it being
'premium'
> I do not know.
>
> By establishing a vpn to the server first I can use remote desktop to
> administer a client that is locally connected to that server. This
works fine
> for both of the standard servers but not for the premium servers. For
> example, in a domain called JH there is an SBS2003 server called JH01
which
> has a locally attached client called JH02. I establish a vpn to JH01
and then
> run remote desktop to connect to JH02.
>
> All 3 servers are basic default configuration/setup with no extra
security
> added and all clients are running XP Pro sp2 with all updates and are
set up
> to allow remote connections.
>
> Has anyone got any ideas why the 'premium' server won't cooperate?
>
> Thanks once again to any responders.
>
> Tricky

.

Loading