Jtdylktuy

I'm having an error I'm not sure how to solve when trying to run an .exe file in a remote system:

C:UsersAdministratorDesktopPSTools>PsExec.exe \172.19.15.50 -u doctor -p doctor "C:Program FilesAppGApp.exe"



PsExec v2.2 - Execute processes remotely

Copyright (C) 2001-2016 Mark Russinovich

Sysinternals - www.sysinternals.com







Unhandled Exception: System.Net.Sockets.SocketException: Only one usage of 

each socket address (protocol/network address/port) is normally permitted

at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress 

socketAddress)

at System.Net.Sockets.Socket.Bind(EndPoint localEP)

at System.Net.Sockets.TcpListener.Start(Int32 backlog)

at System.Net.Sockets.TcpListener.Start()

at AppG.CLI.TelnetServer.ListenForClients()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, 

ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

C:Program FilesAppGApp.exe exited on 172.19.15.50 with error 

code -532459699.



C:UsersAdministratorDesktopPSTools>

Another error I get is:

Found 1 matching device [ Vendor ID 0x10EE, Device ID 0x7 ]:



1. Vendor ID: 0x10EE, Device ID: 0x7





WARNING!!!

----------

Your hardware has level sensitive interrupts.



Interrupts

-----------



Found 1 matching device [ Vendor ID 0x10EE, Device ID 0x7 ]:



1. Vendor ID: 0x10EE, Device ID: 0x7

Anyone knows how to solve this, please?

The problem seems to be that a bound port is not released.

I can see two possibilities:

• The program App.exe is stuck on termination and blocks any new invocation
  of itself.
  
  The only solution is to kill it using taskkill, wait a few minutes,
  and start again. The wait period could perhaps be shortened as described below.



• 
  

  Windows is keeping a bound socket alive so as to let the other side complete
  any sending that it does. This is because TCP has no mechanism for notifying
  the device on the other side of the connection that the connection was
  terminated.

  
  
  

  The solution is to set in the registry at key
  HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters
  the DWORD entry TcpTimedWaitDelay to the number of seconds that
  Windows will wait before allowing another process to bind itself to the
  same TCP port.
  The default setting is 120, meaning 2 minutes, and you may set it as low as you
  like (zero is not recommended).
  This setting affects Windows only and not the other device.

  
  
  

  For more information see
  Settings that can be Modified to Improve Network Performance.