What *could* be happening when your user drops connection and tries to reconnect to a naned pipe session, sql server is picking it up and trying to reconnect to the "sleeping" process it left behind. And because the IP has changed even though you use named pipes to connect, I guess it kind of loses its marbles.
Try connecting via TCP/IP instead of named pipes and see if that solves it. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
