Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
Aaron Clark wrote: The RDP port is in the registry. It's at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber Bug or not, it only happens when Tomcat is running. Maybe. But what people here are telling you is that - one process cannot change the port another process is listening on. If it can, then this is a bug of the O.S. - if the RDP process changes the port it itself is listening on, then it sounds like a problem of the RDP service/program. - if one process is already listening on one port (like Tomcat is listening on port 80 in this case), then another process cannot open the same port to listen on. If it can, then it is (again) a problem of the O.S. - we've run a lot of Tomcats on a lot of Windows, and never heard of a problem like that. So all in all, do you not want to re-examine your assumptions ? (not saying this to sound nasty or send you back to the MS guys; just trying to be logical, and to look at the more probable causes first, before looking at the less probable ones) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
No offense taken. If I could handle this problem myself I wouldn't be asking for others help. I don't understand how a bug in the OS would cause the RDP port to change if (3rd Party Application A) is running. Aaron K. Clark Senior Technician A+, Network+ CCNA Intellicom, Inc (308) 237 - 0684 x 228 (308) 234 - 6645 (Fax) 1700 2nd Ave Kearney, Ne 68847 -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Friday, June 25, 2010 11:35 AM To: Tomcat Users List Subject: Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port Aaron Clark wrote: The RDP port is in the registry. It's at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber Bug or not, it only happens when Tomcat is running. Maybe. But what people here are telling you is that - one process cannot change the port another process is listening on. If it can, then this is a bug of the O.S. - if the RDP process changes the port it itself is listening on, then it sounds like a problem of the RDP service/program. - if one process is already listening on one port (like Tomcat is listening on port 80 in this case), then another process cannot open the same port to listen on. If it can, then it is (again) a problem of the O.S. - we've run a lot of Tomcats on a lot of Windows, and never heard of a problem like that. So all in all, do you not want to re-examine your assumptions ? (not saying this to sound nasty or send you back to the MS guys; just trying to be logical, and to look at the more probable causes first, before looking at the less probable ones) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
From: Aaron Clark [mailto:acl...@intellicominc.com] Subject: RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port I don't understand how a bug in the OS would cause the RDP port to change if (3rd Party Application A) is running. We've seen on numerous occasions that Windows mixes up handles occasionally (although I've never seen that with sockets before). If whatever lookup table Windows uses to translate an fd/socket handle into the real structure is corrupted, the process can suddenly start using another port. I can't think of any possible way for any lump of user code to cause this - unless Windows security has taken a giant step backwards. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
2010/6/23 Aaron Clark acl...@intellicominc.com: 1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Are access logs enabled on that system? What happens with Tomcat when this happens (is it down and unable to start?) I doubt that this change might happen while Tomcat still runs. Is the system property secured? E.g. such trivial issue as CVE-2009-3548 http://tomcat.apache.org/security-6.html Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
Konstantin Kolinko wrote: 2010/6/23 Aaron Clark acl...@intellicominc.com: 1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Are access logs enabled on that system? What happens with Tomcat when this happens (is it down and unable to start?) I doubt that this change might happen while Tomcat still runs. Is the system property secured? E.g. such trivial issue as CVE-2009-3548 http://tomcat.apache.org/security-6.html Aaron, to insist : - there is no way for a process (RDP) to tell the Operating System (Windows), something like change the port number of my listening socket to xxx. Such a call does not exist. - there is no way for a process to tell the OS change the listening port number xxx of process yyy to zzz. Such a call does not exist. - Tomcat itself (nor the JVM that actually runs Tomcat) does not contain code that would even try to do that. But a rogue webapp running under Tomcat /might/ contain code that helps a hacker into doing something like that. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
Do you think its more likey that its a bug in the OS, or the server has been comprimised. Aaron K. Clark A+, Network+, CCNA Intellicom, Inc acl...@intellicominc.com 308-237-0684 x228 (Office) 308-440-5500 (Cell) 1700 2nd Ave Kearney, Ne 68847 From: André Warnier [...@ice-sa.com] Sent: Friday, June 25, 2010 3:47 PM To: Tomcat Users List Subject: Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port Konstantin Kolinko wrote: 2010/6/23 Aaron Clark acl...@intellicominc.com: 1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Are access logs enabled on that system? What happens with Tomcat when this happens (is it down and unable to start?) I doubt that this change might happen while Tomcat still runs. Is the system property secured? E.g. such trivial issue as CVE-2009-3548 http://tomcat.apache.org/security-6.html Aaron, to insist : - there is no way for a process (RDP) to tell the Operating System (Windows), something like change the port number of my listening socket to xxx. Such a call does not exist. - there is no way for a process to tell the OS change the listening port number xxx of process yyy to zzz. Such a call does not exist. - Tomcat itself (nor the JVM that actually runs Tomcat) does not contain code that would even try to do that. But a rogue webapp running under Tomcat /might/ contain code that helps a hacker into doing something like that. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
On 25/06/2010 21:49, Aaron Clark wrote: Do you think its more likey that its a bug in the OS, or the server has been comprimised. The latter is easier to analyse, plenty of tools around to do that. Or nuke the server and start over. p Aaron K. Clark A+, Network+, CCNA Intellicom, Inc acl...@intellicominc.com 308-237-0684 x228 (Office) 308-440-5500 (Cell) 1700 2nd Ave Kearney, Ne 68847 From: André Warnier [...@ice-sa.com] Sent: Friday, June 25, 2010 3:47 PM To: Tomcat Users List Subject: Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port Konstantin Kolinko wrote: 2010/6/23 Aaron Clark acl...@intellicominc.com: 1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Are access logs enabled on that system? What happens with Tomcat when this happens (is it down and unable to start?) I doubt that this change might happen while Tomcat still runs. Is the system property secured? E.g. such trivial issue as CVE-2009-3548 http://tomcat.apache.org/security-6.html Aaron, to insist : - there is no way for a process (RDP) to tell the Operating System (Windows), something like change the port number of my listening socket to xxx. Such a call does not exist. - there is no way for a process to tell the OS change the listening port number xxx of process yyy to zzz. Such a call does not exist. - Tomcat itself (nor the JVM that actually runs Tomcat) does not contain code that would even try to do that. But a rogue webapp running under Tomcat /might/ contain code that helps a hacker into doing something like that. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org signature.asc Description: OpenPGP digital signature
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
From: Aaron Clark [mailto:acl...@intellicominc.com] Subject: RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port The RDP port is in the registry. It's at \HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ TerminalServer\WinStations\RDP-Tcp\PortNumber Grumble... regedit doesn't seem to find non-text values, so I missed it when searching for 3389. Does the registry entry change when the switch happens? Do you think its more likey that its a bug in the OS, or the server has been comprimised. Very good question, and not easily answered. Looking in Windows' event logs (in addition to the previously suggested Tomcat logs) might show something of interest going on at the time of the switch. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
On 23/06/2010 15:47, Aaron Clark wrote: 1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Tomcat has no knowledge of any other service, unless it's running an application which does. It also doesn't have a mechanism for changing it's own port, or any other application's port once it's running. What applications are you running and could one of those be causing the problem? p Aaron K. Clark Senior Technician A+, Network+ CCNA Intellicom, Inc (308) 237 - 0684 x 228 (308) 234 - 6645 (Fax) 1700 2nd Ave Kearney, Ne 68847 -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Tuesday, June 22, 2010 6:03 PM To: Tomcat Users List Subject: RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port From: Aaron Clark [mailto:acl...@intellicominc.com] Subject: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port We have a customer that is running Tomcat Server 6.0.18 under Windows 2008 R2. On this server the Remote Desktop Port (3389) is being changed to port 80 after X (usually ~3) number of days. Sounds like Windows is broken - again. Regardless, a few questions: 1) Can you clarify what you mean by is being changed to port 80? Do you mean that svchost.exe suddenly appears to be listening on port 80 instead of 3389? 2) How did you determine this? 3) What does netstat -ano show both before and after the apparent switch? 4) Is Tomcat normally the process listening on port 80? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org signature.asc Description: OpenPGP digital signature
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
From: Pid [mailto:p...@pidster.com] Subject: Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port It also doesn't have a mechanism for changing it's own port, or any other application's port once it's running. Actually, no process has the ability to change the ports used by some other process. I have to think this is a serious Windows bug - getting handles confused. Often observed on other versions of Windows for various objects (especially icons), so it doesn't really surprise me that the tradition continues in 2K8R2. The RDP port does not appear to be kept in the registry (other than in the firewall open port list), so it doesn't look like it could be an inadvertent registry edit causing the problem. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
When we stop the service the port stops changing. It's a microcomputer system; Anything is possible. Aaron K. Clark Senior Technician A+, Network+ CCNA Intellicom, Inc (308) 237 - 0684 x 228 (308) 234 - 6645 (Fax) 1700 2nd Ave Kearney, Ne 68847 -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, June 24, 2010 9:02 AM To: Tomcat Users List Subject: Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port On 23/06/2010 15:47, Aaron Clark wrote: 1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Tomcat has no knowledge of any other service, unless it's running an application which does. It also doesn't have a mechanism for changing it's own port, or any other application's port once it's running. What applications are you running and could one of those be causing the problem? p Aaron K. Clark Senior Technician A+, Network+ CCNA Intellicom, Inc (308) 237 - 0684 x 228 (308) 234 - 6645 (Fax) 1700 2nd Ave Kearney, Ne 68847 -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Tuesday, June 22, 2010 6:03 PM To: Tomcat Users List Subject: RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port From: Aaron Clark [mailto:acl...@intellicominc.com] Subject: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port We have a customer that is running Tomcat Server 6.0.18 under Windows 2008 R2. On this server the Remote Desktop Port (3389) is being changed to port 80 after X (usually ~3) number of days. Sounds like Windows is broken - again. Regardless, a few questions: 1) Can you clarify what you mean by is being changed to port 80? Do you mean that svchost.exe suddenly appears to be listening on port 80 instead of 3389? 2) How did you determine this? 3) What does netstat -ano show both before and after the apparent switch? 4) Is Tomcat normally the process listening on port 80? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
The RDP port is in the registry. It's at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber Bug or not, it only happens when Tomcat is running. Aaron K. Clark Senior Technician A+, Network+ CCNA Intellicom, Inc (308) 237 - 0684 x 228 (308) 234 - 6645 (Fax) 1700 2nd Ave Kearney, Ne 68847 -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Thursday, June 24, 2010 9:30 AM To: Tomcat Users List Subject: RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port From: Pid [mailto:p...@pidster.com] Subject: Re: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port It also doesn't have a mechanism for changing it's own port, or any other application's port once it's running. Actually, no process has the ability to change the ports used by some other process. I have to think this is a serious Windows bug - getting handles confused. Often observed on other versions of Windows for various objects (especially icons), so it doesn't really surprise me that the tradition continues in 2K8R2. The RDP port does not appear to be kept in the registry (other than in the firewall open port list), so it doesn't look like it could be an inadvertent registry edit causing the problem. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
1) Terminal Services starts listening on port 80 instead of 3380 2) We determined this by disabling Tomcat. The problem stopped. This is happening on their website, so we would know it happens because customers would call in saying the website is down. 3) Right now (before the switch) it is showing tomcat running on 80 and svchost running on 3389. I haven't run this command after the switch yet. 4) Tomcat is what runs on port 80, yes. Aaron K. Clark Senior Technician A+, Network+ CCNA Intellicom, Inc (308) 237 - 0684 x 228 (308) 234 - 6645 (Fax) 1700 2nd Ave Kearney, Ne 68847 -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Tuesday, June 22, 2010 6:03 PM To: Tomcat Users List Subject: RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port From: Aaron Clark [mailto:acl...@intellicominc.com] Subject: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port We have a customer that is running Tomcat Server 6.0.18 under Windows 2008 R2. On this server the Remote Desktop Port (3389) is being changed to port 80 after X (usually ~3) number of days. Sounds like Windows is broken - again. Regardless, a few questions: 1) Can you clarify what you mean by is being changed to port 80? Do you mean that svchost.exe suddenly appears to be listening on port 80 instead of 3389? 2) How did you determine this? 3) What does netstat -ano show both before and after the apparent switch? 4) Is Tomcat normally the process listening on port 80? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it may contain information that is confidential, privileged and exempt from disclosure under applicable law. It is intended solely for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by reply E-mail and destroy all copies of the original message. Additionally, we will take the appropriate action to avoid sending you an unintended E-mail in the future. Thank you for your cooperation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port
From: Aaron Clark [mailto:acl...@intellicominc.com] Subject: Apache Tomcat 6.0.18 on Windows Server 2008 R2 Changes RDP Port We have a customer that is running Tomcat Server 6.0.18 under Windows 2008 R2. On this server the Remote Desktop Port (3389) is being changed to port 80 after X (usually ~3) number of days. Sounds like Windows is broken - again. Regardless, a few questions: 1) Can you clarify what you mean by is being changed to port 80? Do you mean that svchost.exe suddenly appears to be listening on port 80 instead of 3389? 2) How did you determine this? 3) What does netstat -ano show both before and after the apparent switch? 4) Is Tomcat normally the process listening on port 80? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
