TCP Port Problems

  • Thread starter Thread starter julianwarne
  • Start date Start date
J

julianwarne

Hi,

I am running an application that uses a batch file to open
a TCP port to listen for connections.

I have set the batch file up as a service to start on port
1000.

However whether I run the batch file standalone or as the
service it seems to open the port for a short period of
time then the port becomes unusable and telnet cannot
connect to it.

Are there any known problems with W2000 Advanced Server in
this area?

Thanking you in advance
Julian
 
No, there are no known issues with Windows 2000 like this. It could be that
the application only allows a certain number of connections and you have
reached the connection limit, if you run "netstat -an" from a command
prompt, how many connections do you see to port 1000?
Another possiblity could be that something happens with the application
and it tells TCP to stop listening. If you run "netstat - an" from a
command prompt does it show as listening on TCP 1000?

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
Hi Marc,

Thanks for the reply.

No services are shown running with netstat -an on port
1000.

What happens is that I cannot restart the service on any
port once it has stopped even after restarting the system.

I have to uninstall the application that uses this batch
file, deleting the batch file & directories etc, then
reinstall them, then run up the batch file again.

Is there another port I should be using?

Why would the service stop once it has started?

Is there any other command that can be used to 'clear the
port' so that I don't have to go through the uninstall-
reinstall process?
 
Back
Top