Tag Archive
TCP Backlog Capture
TCP Backlog capture is an effect that prevents a server application on the Stratus module listening on port X from successfully creating a connection with any client trying to connect to port X. Connections to other ports even from the same clients work fine. The typical solution is to shut down and restart the server [...]
Network traces and data security
Many times the only way, or at least the fastest way, to resolve network communications problems is by collecting a trace of the communication and sending it to an expert for analysis. When the expert is not part of your organization this may present security concerns since the trace will contain application data. However, typically [...]
Telnetd and remote (TCP connected) printers
Back in May of 2009 I wrote about securing telnetd so that only the RSN process has the ability to use it (Telnet can’t live with it, can’t live without it). At the time I was thinking about the remote service network but I was recently reminded of another very import reason for running the [...]
TCP is a stream of bytes not messages
“The application has been running fine for years, last week the network was upgraded and we moved from 100 mbps to gigabit. Now the last half of the data in some messages is garbage. The network people swear it is not the network – but that is the only thing that changed.” The good news [...]
Is Your Pre-production Network Testing Effective?
I would like to expand on Paul’s recent blog “Is your pre-production testing effective?”. Paul covered CPU utilization and code paths but there is another very important aspect of many applications – network utilization. Many applications are tested in a LAN environment with latencies in the sub-millisecond range and bandwidth at least at 100 mbps. They [...]
