Well, it looks there are two different things going on there. First of all, you clearly have something wrong with your tcpexit.cmd file. No way for me to know what, but probably something is mistyped, or perhaps it's trying to run something in a non-default shell.
Second issue is the failed restore on that connection. Showing the details would tell me more, but I'm pretty sure it's a timing problem related to TCP/IP initialization.
From your description, I'd say the reason you don't see this on the other system is that it prompts you to enter the password before it attempts to restore the connections, and that delay prevents the timing problem.
I've seen this happen occasionally on my own system which uses DHCP, and it's on my TODO list to add some better check logic to the restore routine. However, since no bug reports have submitted on this by any users so far (hint, hint), it has not been near the top of my priorities.
