I
Ian Beyer
I fired up outlook on my laptop on a wired network, where it got set up and
connected to my Exchange server quite happily. When I went into standby and
brought it back up on the wireless network, it said it was disconnected, with
no option to go back online. I dropped the machine in the dock and got it
going on the wired network again, and it's still stuck in "Disconnected"
mode. Even a reboot doesn't cure this. I found another post that seemed to
indicate that not running in cahced mode might be the culprit, so I turned
that off. Now when it can't find the server, it simply blows up in my face
and refuses to start, and I can't even change the settings. Both networks are
on the same subnet, so it's not a subnet change at issue here.
While I realize this is in Beta, if this is normal behaviour, something
needs to be fixed, because this is not going to go over well with non-IT
users. If Outlook can't deal with IP address changes without melting down,
there's a serious design flaw there. The inability to make configuration
changes to an existing installation without an Exchange server present (real
or imagined on Outlook's part) is also quite problematic.
connected to my Exchange server quite happily. When I went into standby and
brought it back up on the wireless network, it said it was disconnected, with
no option to go back online. I dropped the machine in the dock and got it
going on the wired network again, and it's still stuck in "Disconnected"
mode. Even a reboot doesn't cure this. I found another post that seemed to
indicate that not running in cahced mode might be the culprit, so I turned
that off. Now when it can't find the server, it simply blows up in my face
and refuses to start, and I can't even change the settings. Both networks are
on the same subnet, so it's not a subnet change at issue here.
While I realize this is in Beta, if this is normal behaviour, something
needs to be fixed, because this is not going to go over well with non-IT
users. If Outlook can't deal with IP address changes without melting down,
there's a serious design flaw there. The inability to make configuration
changes to an existing installation without an Exchange server present (real
or imagined on Outlook's part) is also quite problematic.