Remote Desktop Web connection and non standard RDP port

[jtpryan]

I changed my RDP port to a nonstandard number from 3389. I can connect
fine to it from outside. I then wanted to try the web interface, also
at a non standard port. That seems to connect fine in that I get the
default htm file. But if I click "connect" I get the "server not
accepting connections or is busy..." message. I tried putting in the
server nameort number, to no avail.

Any thoughts on this?

-Jim

 

[Sooner Al [MVP]]

I changed my RDP port to a nonstandard number from 3389. I can connect
fine to it from outside. I then wanted to try the web interface, also
at a non standard port. That seems to connect fine in that I get the
default htm file. But if I click "connect" I get the "server not
accepting connections or is busy..." message. I tried putting in the
server nameort number, to no avail.

Any thoughts on this?

-Jim

See this article for help with this issue...

http://support.microsoft.com/default.aspx?scid=kb;en-us;326945

You also might be interested in a modified Default.htm file created by
Jeffrey Randow, MS-MVP. Go to the "Client" section and click on the
"Advanced Remote Desktop Web Connection" link...

http://www.schinning.net/FreeTools/tabid/54/Default.aspx

--

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...

 

[jtpryan]

See this article for help with this issue...

http://support.microsoft.com/default.aspx?scid=kb;en-us;326945

You also might be interested in a modified Default.htm file created by
Jeffrey Randow, MS-MVP. Go to the "Client" section and click on the
"Advanced Remote Desktop Web Connection" link...

http://www.schinning.net/FreeTools/tabid/54/Default.aspx

--

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...

Al,

Thank you. I read the article and made the change to the default.htm
file as said:

1. Locate the Default.htm file in the %system root%\Web\TsWeb folder.
2. Open Default.htm in Notepad or in another text editor.
3. Locate the entries that start with "MsRdpClient.AdvancedSettings2".
4. Add the following line after these entries
MsRdpClient.AdvancedSettings2.RDPPort = xxxx
where xxxx is the new port.
To make sure that you can connect with the new setting, append the port
number to that of the published URL (that is,
www.xxx.xxx.xxxortNumber).

However, I get the same error. I am a little confused by the last
line. Where exactly are they talking about with the "published URL"?
I have 2 non-standard ports here, the one the web client sees (call it
6060) and the one RD uses (call it 7070).

So, I get to the site by typing http://mywebsite:6060/tsweb. That
works. I then get the web interface and leave the server name blank
and hit connect. Where exactly to I enter the :7070 as said in the
last line? I did modify the default htm file with the line:

MsRdpClient.AdvancedSettings2.RDPPort = 7070

-Jim

 

[jtpryan]

See this article for help with this issue...

http://support.microsoft.com/default.aspx?scid=kb;en-us;326945

You also might be interested in a modified Default.htm file created by
Jeffrey Randow, MS-MVP. Go to the "Client" section and click on the
"Advanced Remote Desktop Web Connection" link...

http://www.schinning.net/FreeTools/tabid/54/Default.aspx

--

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...

Got it. I didn't realize there are TWO default.htm's. I was changing
the one in below the inetpup directory, the interface was looking at
the one below \windows\web\tsweb. All for naught tho', I still can't
get there from work. They must have it blocked somehow.

-Jim