scuse my French but, damn those MS instructions. Oh, and apologies for dragging out this OT thread.
I (stupidly) never checked what port the server was listening on after removing and re-creating the RDP listener and... problem is not solved, removing and re-creating the RDP listener removes the registry entry with the new port and re-creates it with the default port of 3389 (which does make sense really, and if my brain was working yesterday I would have spotted the flawed instruction). Of course my connection worked after doing this, the server was again listening on the port the client seems to insist on connecting to. I can get the server to listen on port 3390 (after making the registry changes on the server and restarting terminal services, I can connect to port 3390 with netcat or telnet but not to 3389) but the client just seems to refuse to connect on anything but 3389 and I have followed the instructions to the letter but it still doesn't work. I'm using Client Connection Manager v.5, I also checked that my imported connection did actually import the Server Port value correctly by exporting what I'd imported to text and checking the Server Port value. Doug, could you tell me which client you are using and, if possible, send me the .cns file (off-list) that you imported to get the client to connect on a different port. Your help would be much appreciated. Mark ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
