Thanks for responding, and so quickly. I took your advice and finally "got
it". My ports were set right, thus why I was able to connect in RD and RWC.
Actually from reading your prior suggestions to Ian a year ago, I was already
in the ballpark but overlooked a few things, er, mostly in the name of "user
error" (some things never change).
For one, I never realized the connection template/interface resides on the
host computer. It makes sense of course once you think about it, but I always
presumed that screen was local to the client side.
Secondly, since I generally hide file extensions in Explorer (not always a
smart thing even in detailed view), I had not noticed that Randow's 'Advanced
RWC has a .html ending, whereas he default one is .htm. Always helps to have
your connection addresses (URLs) dead on.
A few additional things I have noticed: It appears you can place the ARDWC
template alongside the default one in the tsweb directory if you care to, as
long as you take into account the proper connection syntax (use
/advanced.html in place of /default.htm in the address). That way you have
the option of using either when connecting at any time, and no conflicts seem
to appear. Or of course you can rename it to replace the original default
(and back that one up for safety reasons, just like you suggested).
If anyone were to set things up correctly in MS RWC and then ARDWC, and
still had file transfer problems, they may want to check their Services.msc
to make sure the required networking protocols are enabled. Now I'm no
networking expert so I'm only guessing here, but I can imagine some folks
might disable things like Clipbook there not thinking they'd ever need it and
that might effect the ability of ARDWC to do its thing.
As for the end results, Mr. Randow's template works well, very well in fact.
I was most surprised at how seamless it was/is, both the ease in which you
implement it, and how well its features work. The original download was only
6 KB in a compressed zip file, which extracts to roughly 23 KB (a single
file). A very nice addition to RWC in such a small package!
Al, hat's off to you my friend. You got me over the hump, like you have with
so many others on this forum (and elsewhere). Never underestimate the value
of MVPs. I've known this for some 10 years now.
JM
"Sooner Al [MVP]" wrote:
>
> You need to install it on the host PC as a replacement for the default.htm
> file which I believe is in the "C:\Windows\web\tsweb" folder. I would save
> the original default.htm file as a backup in case you want to roll back.
> Both TCP Port 80 (IIS) and TCP Port 3389 (RDP) need to be forwarded/opened
> on any firewall/router the PC is behind. Obviously both IIS and Remote
> Desktop need to be running on the host.
>
> --
>
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the
> mutual benefit of all of us...
> The MS-MVP Program - http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
> How to ask a question
> http://support.microsoft.com/KB/555375
FAQ
Search
Profile
Private Messages
Log in
Windows