From looking at the UI images
I'll take a guess
(I stress this is a guess) that:
* The device can be set to "server" or "client" mode.
* The former is (a) what you've selected and (b) what you want in order to allow another device to connect to it and receive the serial data
* The latter would be used to connect to a remote
server and bridge that to serial
* In "server" mode (as selected) the "remote address" is actually greyed out. So 192.168.11.245 is a red herring here.
* The address you actually want to connect to is that of the serial-wifi device. If this is working as a hotspot/router (rather than a station on an existing network) and is what your laptop
is connecting to, then the address you want is 192.168.16.254.
So assuming the port is 8080 (it does say "local/remote" in the UI) which as nohal points out is a bit suspicious as that's usually where people run web servers when they don't have access to privileged ports
telnet 192.168.16.254 8080
If it connects and you see NMEA-format data then happy days: if there's a problem with OCPN we next need to look at your data connection settings.
If it connects and there's no data then either there's an issue with data going into the device, OR perhaps the device is expecting you to connect with some protocol layered on top of tcp (websockets? http?). If either of the latter, then start searching for a program which runs on windows to bridge a connection of that type to pure tcp.
If it doesn't connect...well..that was my best suggestion :-/