Turns out while the plug-in initially worked via the public ip, it refused to work that way again. On a whim, I tried the
internal LAN IP of the machine and it worked. Also throw into the equation a firewall that was installed that I did not know
about. I don't know why this works, I never would have thought that an IWP session could call the URL using the internal IP.
The plot thickens........
Moved the server to a new location. Had to change the URL to use the external IP ( what I would expect to be normal )
so why would the plug only work in that situation if the internal IP was used?