You can see if the port is listening by going to the command line and doing a netstat -n -a
Steve ----- Original Message ----- From: "Doug" <[EMAIL PROTECTED]> To: "CF-Server" <[EMAIL PROTECTED]> Sent: Monday, September 23, 2002 10:01 AM Subject: Re: Win2K Terminal Services, non-standard port > I am making an assumption here. > > 1. You have edited the server registry in BOTH places mentioned in the MSKB and BOTH now have the > same, but new port assignment. > 2. You have followed the instructions to create a new connection, export it , then import it to the > standard connection file, on the client. > 3. you do not have the old port number (3389) blocked with IIS lockdown or some other port blocker. > 4. if you are behind a router of some kind, you have the new (And the old) port numbers forwarded to > the server. > 5. You have terminal services running (after a re-boot) in Services. > > If these assumptions are correct, you should connect up right away. but just by omitting one of the > steps above, the connection will fail. > Remember the part in the KB article that says port 3389 cannot be changed for Active-X over terminal > services? > > I followed this on my test box, just for the fun of it (new pot of coffee was not ready yet) and it > connected fine. I did an extra step though. Before making any changes on the Server registry, I > exported the default key to a .reg file, and when I was through playing around with it, I re-merged > the key and it reset the registry back to the defaults. > > I don't normally use terminal services, as I have never seen a compelling reason to have them > running. > > Good luck! > > ================================ > This address is filtered through the open relay database at http://www.ordb.org > and is virus scanned by ANTIVIR > http://www.dwhite.ws > mailto:[EMAIL PROTECTED] > ================================ > ----- Original Message ----- > From: "Mark Woods" <[EMAIL PROTECTED]> > To: "CF-Server" <[EMAIL PROTECTED]> > Sent: Monday, September 23, 2002 6:48 AM > Subject: Win2K Terminal Services, non-standard port > > > | I need (well, want) to run terminal services on a port other than 3389, so > | I read the article on the MSKB about it ( > | http://support.microsoft.com/support/kb/articles/Q187/6/23.ASP ) and > | followed the instructions. > | > | The server is now listening on port 3390 (and not 3389), but I can't get > | the client to connect on that port. I exported the connection settings to > | text, changed the server port value and imported the updated settings back > | into the client connection manager but no luck. > | > | Anyone managed to get this working? Any idea what I'm doing wrong? > | > | > | Thanks > | > | Mark > | > | > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
