The following list identifies problems in the NetAcquire program that Kensit is aware of. The list includes work-arounds, identification of status, and requests for help where Kensit has insufficient knowledge of what to do:
When hosting, no one is able to connect to the IP that NetAcquire shows.
Cause: PCs that have more than one network device installed may encounter this problem (ie. a modem and a network card). NetAcquire is picking up the network address of the wrong device. So, in effect, the host is telling the potential joiners the wrong IP address.
Workaround:
Find out what the other IP address is and use that one.
That is to say, ignore the IP address NetAcquire shows and tell the joiners the
correct IP address.
There are a number of ways to determine the right IP address.
One way is to open a Command Window and type in the command IPCONFIG.
This lists all network devices and their associated network information.
Then you simply note the IP Address of the device that you know is connected to
the Internet.
Status: Kensit uses a third party TCP handling tool and has no control over it. In order to fix the problem, NetAcquire will have to make some native Winsock calls to determine the right IP Address. Kensit does not yet have the program code to do this yet. Anyone familiar with TCP programming and Visual Basic and willing to provide that code, please contact Kensit.
No one is able to join a host that is on a network that uses a gateway to connect to the Internet.
This is not really a problem with NetAcquire, but rather an inherent design anomaly of networking. There are ways to configure gateway routers to allow NetAcquire to be hosted. Technical details for this vary depending on the hardware/software being used. The NetAcquire web page contains some more information about this.