I am working with mswinsck 6.1.98.16, I don't know if there is a newer version.
I also uses the VB5 engine.
What I just discovered happens on XP and on win7.
This is just a note about a misbehaviour..
I was looking for a bug in one of my apps, it has a control remote console.
Basically, it opens a socket, set listen mode, then it gets the connection, and start receiving byte arrays (frames of a video), and then it renders the video on the window.
The receiver app by protocol, reads the .LocalIP plus localport property from the socket all the time, and comunicate it by another separate communication channel, as a way to say "hey, I am here, so the remote PC don't ping time out the subscription that is identified by the PORT+IP".
and the video sender code at remote PC takes notes and resets the countdown for the ping time out.
The problem is, that the sockets start reading a corrupted IP from the property .LocalIP, it removes just one character.
If the IP is, 10.1.1.200, after a while it start reading 10.1.1.20 from the .LocalIP property. INCREDIBLE but confirmed.
I changed the code to read the localIP only at the beginning, and then using a string backup variable to send the information by protocol. And it fixed. But was incredible, because I already looked at the code , that .LocalIP was NEVER assigned by my vb code.
maybe is a newer version that fix the problem. Is one?
I also uses the VB5 engine.
What I just discovered happens on XP and on win7.
This is just a note about a misbehaviour..
I was looking for a bug in one of my apps, it has a control remote console.
Basically, it opens a socket, set listen mode, then it gets the connection, and start receiving byte arrays (frames of a video), and then it renders the video on the window.
The receiver app by protocol, reads the .LocalIP plus localport property from the socket all the time, and comunicate it by another separate communication channel, as a way to say "hey, I am here, so the remote PC don't ping time out the subscription that is identified by the PORT+IP".
and the video sender code at remote PC takes notes and resets the countdown for the ping time out.
The problem is, that the sockets start reading a corrupted IP from the property .LocalIP, it removes just one character.
If the IP is, 10.1.1.200, after a while it start reading 10.1.1.20 from the .LocalIP property. INCREDIBLE but confirmed.
I changed the code to read the localIP only at the beginning, and then using a string backup variable to send the information by protocol. And it fixed. But was incredible, because I already looked at the code , that .LocalIP was NEVER assigned by my vb code.
maybe is a newer version that fix the problem. Is one?