On Sat, 31 Jul 1999, Robert wrote:
> I also rebooted serveral times, and I'm not running behind any firewalls
> or the like.
This should not be such a great mystery. If tcpserver complains that it
can't bind to a port, then something else must be using this port.
Period.
No exceptions. Therefore, you need to establish and verify two items of
information:
A) What port tcpserver is trying to bind. Examine your command line
arguments to tcpserver.
B) What is listening on the same port. netstat will show you that. Don't
forget to use the -a option to netstat.
