Browser hangs after software reboot

[greengene]

this appears to be new(?), but now when i do a ForceReboot(), an open browser session,
e.g., IE7, Firefox, the window just hangs waiting.
when i netstat -a it shows sockets still established with the NB.
i don't think this used to be the case. i need to open a new browser instance in order
to connect to the NB - a new tab won't do it.

anyhow, can i force the NB to close the sockets, i.e., send a FIN, before I reboot?
will doing a close() on each socket's fd send the FIN?

how can i stop new connections while i'm going through my processing leading up to the reboot?

StopHttp() is just a stub so i don't think that is any help.
KillStack() is described in the manual as "do not use".

any help will be appreciated.

[greengene]

close() on each socket worked.

odd that the reboot after a software upload didn't have the problem.
some day i'll look and see what that is doing differently than me.

[rnixon]

If no data is in the pipe when you reboot, then you do need to close the sockets first. Otherwise there is nothing in the tcp/ip protocol to tell the web browser the netburner (or any other device) went away, so it leaves the sockets open.

[greengene]

maybe NB can sell their KeepAlive code to MS

actually, it no longer is broken, i.e., i'm loading the same versions of
our app that i did earlier and now they aren't hanging the browser!
MS is so much fun!