Happy hunting, Lou. My gut tells me that this is not an issue? with IB or TWS. It is sufficient that some defunct process holds on to port 9707 for TWS to be denied access to that port. Those sockets in that state may not show up in netstat listings of established connections. A couple ways to check this are:
- My favorite command "lsof". Try it as " lsof -iTCP -n" so that it only shows you the processes that use TCP resources.
- Or you could go to the horse's mouth with "cat /proc/nettcp" but make sure you convert to numbers from hex to decimal or look for port "25EB"
闯ü谤驳别苍
On Thu, Jul 7, 2022 at 09:00 AM, Lou Dudka wrote:
闯ü谤驳别苍 and joanmarcel119,
Again, thanks for your input.
Firstly, I don't use IB's ports simply because we may (and do) run multiple TWS's on the same machine.
I bought up another TWS on the same machine and tried to assign port 9707.? TWS refused it and said it was in use, which it wasn't.
I ran? netstat -ano -p tcp and port 9707 did not show up.
I think it's an IB problem, not a "network" problem.? It appears IB doesn't think it "let go" of the port.
I'll guarantee you when I re-boot the machine this weekend and assign 9707 to the "offending" TWS it will work.
This is not a big deal (now) to me since I'm up and running.? I consider myself a trader first and a technician second, but it does intrigue me.
I'll keep you posted.
Thanks, as always, Be Well,
Lou Dudka
