I always wanted to discover my first bug in a Microsoft product.... :)
For now, I can answer the first two Q's - the 3rd one I'll do tomorrow when I can grab that 64bit machine again.
Q: What's the device type that it gives you when you run it in 32-bit? I'm assuming it's "vpn" since it's using a WAN miniport.
A. Yip - "vpn"
Q: Are you able to replicate this problem.
A. Yes, we actually seen it onsite when our app crashed. I had a gut feel it was 64bitNESS playing up, but only when I had the debugger on both 32bit/64 bit machines,
it could know for sure.
For our use, we verify the virtual adapter, in case someone tampers with it... so we can reset it. I've managed to look at another property to get a similar functionality,
so for now there is no crises per se. Funny that although the device is null, I can still connect with it to our vpn end point... will also double check that with Q3 for ya.
I agree with your statement - keep everything as is -let’s see what our Microsoft friends have to say!
Thanks for the assistance and help! Good job!