Bug fix: not attempting connect if port range is wrong on constructor

For some reason this didn't catch when I was testing locally.