Remote Desktop Web Connection / ISA / W2K Term Serv

[Jeff]

Hi,

I went back 17 of the 45 pages and found some useful
things to check with regards to my problem. However,
alas, nothing helped.

I am trying to connect to a Windows 2000 server running
TS in Admin mode from the Internet. I have RDWC
installed and running on an XP workstation.

I can use RDWC to connect to the W2K server without
difficulties internally.

There is an ISA server between the Internet and LAN:
1)I have a Protocol Rule allowing port 3389 inbound &
outbound and port 9999 inbound,
2)I created Protocol Definitions 3389 outbound and 9999
inbound with no secondary connections),
3)I have a Server publishing rule to redirect port 9999
inbound to the W2K server
4)I have a Web Publishing Rule for the RDWC service on
the XP workstation.


From the Internet I can:
1)Telnet for a few seconds to my external IP port 9999
but then receive a "Connection to host lost" message,
2)I can reach the MS Windows RDWC page but, it will not
allow me to enter in IP:9999, "error on page",
3)if I simply use the IP I get a white window, then it
times out with "The client could not connect to the
remote computer..."

When I tried to create a Server Publishing rule for port
3389 on the ISA the Event Log showed that it could not
bind to 3389 (but I couldn't determine what process was
already using the port). That is why I went with port
9999.

This is a cool tool and I would really like to get this
going for our Admins and Power Users.

Any help someone can provide would be appreciated.

Thanks.

 

[Jeff]

Well, this morning I was able to determine why the Telnet
session and Server Publishing rule binding error were
being generated. Those interested can look at 294720.

Still having problems entering a port in the server
window with the RDWC client. Doesn't like the : or
anything anything after it. Keeps reporting an
error "unknown name, or invalid procedure call or
argument". So I have had to resort to using port 3389.

I would also like to "port forward" the packet through
ISA but haven't found out how to do that yet (server
publishing seems to pass on the inbound port to the
destination server and not allow you to change it). That
way I don't have to change the default port on all of my
TS servers.

As always any help would be appreciated.

Thanks.

 

[Jeff]

More follow-up (for those that might be interested)...

The following is taken from a KB article entitled
(Publishing POP and IMAP Services Using Microsoft ISA
Server). It states... "With server publishing, the
external port on the ISA Server computer and the port
number on the internal server must be the same because
ISA Server cannot perform port redirection."

So that answers all of the questions I posted here.
Since ISA does not support port redirection there is no
need to determine how to get the RDWC client to allow
entry of a port (other than the default 3389).

Merry Xmas.