- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- TCPIP port reused
Networking
1819805
Members
3091
Online
109607
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2008 07:18 AM
тАО07-21-2008 07:18 AM
TCPIP port reused
I have a problem under Windows Server 2003, when a client connect to a specific application (Ataman RLOGIN ).
The first CONNECT is okay (we launch our application after the connection). The second CONNECT is not accepted if the client tries
to connect less than 30 second after closing the first connection.
I trace the connection with WireShark and just fin a "TCP port reused" message.
I try to change some registry parameters :
- TcpTimedWaitDelay
- KeepAliveinterval
without success
The first CONNECT is okay (we launch our application after the connection). The second CONNECT is not accepted if the client tries
to connect less than 30 second after closing the first connection.
I trace the connection with WireShark and just fin a "TCP port reused" message.
I try to change some registry parameters :
- TcpTimedWaitDelay
- KeepAliveinterval
without success
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-12-2009 03:32 PM
тАО06-12-2009 03:32 PM
Re: TCPIP port reused
Sounds like an issue with RLOGIN, not Windows or your network.
in 2003 on the server you can run this command to see all listening ports and what PID (last column) is doing the listening:
NETSTAT -ano |FIND "LISTEN"
Try running that before you connect, 1 second after you disconnect and then 60 seconds after disconnect and see if the RLOGIN process is actually listening during that 30 second process or not.
in 2003 on the server you can run this command to see all listening ports and what PID (last column) is doing the listening:
NETSTAT -ano |FIND "LISTEN"
Try running that before you connect, 1 second after you disconnect and then 60 seconds after disconnect and see if the RLOGIN process is actually listening during that 30 second process or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2009 12:04 AM
тАО06-15-2009 12:04 AM
Re: TCPIP port reused
Hi Chamberlin,
It appears to me that since this Ataman rlogin application is Terminal Server aware, chances are you'll need to change server settings into Application Server mode.
Either that or the application wasn't correctly installed. By default whenever you double click a setup.exe file or type "atrls install start" Windows 2003 changes USER MODE from EXECUTE into INSTALL.
However, just to make sure, you may want to either run this command "change user /install" before you start the installtion process, and run "change user /execute" only when you're done or Start - run - appwiz.cpl - Add new programs - CD or floppy - select the location of the files and so on.
Please, let us know the outcome.
Hope it helps.
Edgar.
It appears to me that since this Ataman rlogin application is Terminal Server aware, chances are you'll need to change server settings into Application Server mode.
Either that or the application wasn't correctly installed. By default whenever you double click a setup.exe file or type "atrls install start" Windows 2003 changes USER MODE from EXECUTE into INSTALL.
However, just to make sure, you may want to either run this command "change user /install" before you start the installtion process, and run "change user /execute" only when you're done or Start - run - appwiz.cpl - Add new programs - CD or floppy - select the location of the files and so on.
Please, let us know the outcome.
Hope it helps.
Edgar.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP