tommyt

hallo, habe eine anweisung zum umbiegen gefunden: Greetings all: In his latest article on MCP Magazine, Bill Boswell bestowed a titbit of knowledge that I'm sure many people will be happy to have: You can now customize the Terminal Server ActiveX control to use an alternate port than the standard TCP 3389 to connect up to your TS resources. The MSRDP.OCX ActiveX control that ships with the TSWEB components on SP2 and the Win2K download was hard-coded at 3389- therefore, you could not use the ActiveX control to connect to servers where the listen port was changed. .Net and XP now ship with an updated version of MSRDP.OCX that has a new component (RDPClient). Among the new methods of the control is "AdvancedSettings2" and one of the properties of "AdvancedSettings2" is "RDPPort." The way the TSWeb access works is by simply loading an ASP page (CONNECT.ASP) that calls the MSRDP.OCX ActiveX Object. For those of you that want to use the ActiveX control to connect to a different listening port, all you have to do is edit the CONNECT.ASP page, and add the following line before the MsTsc.Connect method: MsTsc.AdvancedSettings2.RDPPort=X - - where is X is the custom port your TS is listening on (in decimal). When the ActiveX control attempts to connect to the TS, it will now use this port. Replacing your existing Win2k TSWeb components is easy- just go to an XP box, and under Add/Remove Programs/ Windows Components, install "IIS (Details) -> WWW Services (Details) -> Remote Desktop Web Connector." When you install this, it creates a %SystemRoot%\Web\TSWeb directory. Just copy the contents of this directory to your Win2k TSWeb directory (kill the existing files first) and you are good to go. Of course, remember to edit the CONNECT.ASP to point to the new port. When the remote clients go to the TSWeb site, they will be prompted to install the new ActiveX control. Those of you using the control in VB / C ++ can directly access the properties programmatically. A thread here where we discussed hacking the old control to point to a custom port drew lots of interest, though I was never successful in making it work. Now we don't have to worry about it. Hopefully those interested parties are still on the list and will get this information... Sorry I could not contact everyone directly. Thanks to Dr. Tom Shinder for pointing me to the MCP mag article in the first place. Cheers, gruss thomas