I have 3 client PCs running various versions of Windows and 1 file server, running Vista Home Premium 64. All 4 machines are using the Gigabit CT Desktop Adapter for connectivity. This server has previously been running Linux for 2 years and no hardware has changed, but I just installed Windows instead. My problem is this: WOL from any of the clients works perfectly, as far as waking up the server. However, I am then unable to connect to the server. When I go to the server and look in Device Manager, the network adapter has the exclamation point/triangle thing. If I disable the adapter in Device Manager, and then enable it, everything works perfectly. This happens every time it wakes from sleep mode, whether using WOL or waking it directly from the keyboard.
I never had this issue while running Linux, so naturally I suspect a Windows configuration issue or driver issue. Except, one of the 3 client machines is an identical copy, hardware and software (yes, and drivers), for the server, and it never has a problem when waking up.
This behavior started immediately after installing Vista so I really don't believe it's a hardware issue, although I suppose this weekend I could swap card to 100% rule it out. But if anyone has seen this behavior before, and/or has any ideas or suggestions on what I should look for to fix it, I'd appreciate it.
Also, I should have mentioned that I have checked the power management tab for the adapter and the only box enabled is Wake on Magic Packet. This is the same way I have the adapter configured on the twin machine which works.
I can see why you are asking for suggestions. You have already looked at the most obvious items. I would like to propose a possible reason. Maybe one of the voltages in the server is slow to ramp up or has some strange glitch when the server wakes. This could be caused by a power supply component or by any hardware component that is installed in the server. I know this theory sounds "out there, " but many years ago I did hardware maintenance, and I can recall some weird situations where some component other than the power supply made the power supply look bad. And less than perfect power can cause all kinds of weird symptoms.
I like your idea of swapping the network adapter. If the Windows error is caused by some condition that is on the edge of working correctly, you might end up with both computers coming out of sleep normally after the swap. Of course, if the wake error follows the adapter, then you just need to replace the adapter.
If the problem stays with the server, then tracking down the source will be a lot more work. You could swap other components, but first I would double check that the BIOS settings are the same (and the same version of the BIOS is in both), double check driver versions, and other settings.
I am very curious to hear about what caused the problem once you track it down.
Mark, Thanks for the input. Your suggestion of power issues makes as much sense as anything else at this point. I spent last night uninstalling and reinstalling the balky adapter with various driver versions. Turns out I had a much older driver version on the "twin" machine. Aha, I thought. I'll install that version on the server. Didn't make any difference. The machines are running identical BIOS versions. It's an older ASUS motherboard and they quit making BIOS updates a couple of years ago so both machines are on the final version. Nothing I did, software-wise, including installing *just* the driver and not the Proset software, and managing the adapter via Windows, made any difference to the behavior. So, I just finished swapping adapters in the duplicate machines. Again, nothing changed. The balky adapter works properly in the client machine, and the adapter that was working perfectly in the client machine wakes up, but then loses connection and must be disabled/enabled in device manager before it starts working again.
I finally gave up, disabled the Intel nic, and am using the built in adapter on the motherboard - which also works perfectly. I'd love to beat my head against this wall until I manage a solution, but I just have too much going on right now to spend who knows how many hours troubleshooting when a workaround is so readily available, so for now I'm going to drop it. In a few weeks I'll reenable the adapter and see if it wants to play nice again. Maybe some Windows update will mysteriously fix the issue. Or not. If I do manage to figure it out I'll post back. Again, appreciate the help.