NetBurner Community Forum

That was a typo on my part. I think your code should work or you can just use the BogusPacketPP pointer instead of p. You should sniff the packets using wireshark on a PC. You may need to have a hub instead of a switch so your PC can see the packet. This will show you if the reset packets are being ...

In the code I posted I put the following line twice

Yup thanks for that.

It appears that so far this method isn't working yet. I get it to increment all the way through the 65535 possible socket #'s, but I never see the destination stuck mod5282 come out of it.

I do have a question about your ...

Now this is a really tough one. So it looks like you are using ReadWithTimeout, you check for an error but not for a timeout. What happens to your code when TCP_IP_size = 0 because of a timeout? Does it just loop back around and try to read again? If so the TCP socket will never close on its own ...

Help Help. I have a rookie ehternet problem here and I need help.

Due to a TCP IP timeout error on the PC, the PC cannot access the data on any of the netburners(32 in all) in the system. A Processor "Reset" is not allowed.

The netburners are stuck in a loop using this section of code ...