Taking a moment's reflection, Peter Pan mused: | | Sounds like *YOU* are trying to create a scenario where you are | indispensible. He said it hadn't worked for 4 days.. You gonna sit there | for 4 days?
Your first sentence makes no sense. But, since we've moved into the realm of the ridiculous ... do you believe the client PC hasn't been rebooted once over the course of those four days?
| I love your absolute proclamation of "it won't".. Show's you aren't | thinking.... I am on a computer this second that has both a wired | connection, and is the network exchange mail server on the network, with a | second bridged wireless connection to the WAP/Router and cable | connection.. Not so odd, we have had a wired network for years, and | bridged it to the new wireless one we are installing incrementally as | wired stuff dies. And by the way, that scenario will simulate EXACTLY the | symptoms the op described.
Again, you are making assumptions that aren't relevant to the information the OP has provided. So far, these permutations have gone from
1) reboot the mail client PC; 2) reboot the wireless mail server on the internal network (assuming it exists), or simply click "okay" if it is XP SP2 to accept the SSID change; and now, 3) reboot the client, because the client is also the wireless mail server on the internal network (another assumption).Your advice is relevant to the scenarios you have created to support them, granted. But, there's no information so far to suggest that your created situations are in any way similar. When a car has a rough idle, you can say that it's dirty fuel injectors because that's exactly the symptom of dirty injectors ... but what if the car's carburated? No dirty injectors.