Posted: 2/16/2011 4:58:18 AM EDT
|
When logging in to Outlook Web Access, how does it identify the computer that you are using?
They did some server upgrades at work and ever since, I've only been able to log in to OWA with my work laptop. Before the changes I could use any computer or mobile device that would support it. Our IT guy hasn't been able to figure it out yet. I don't know if he's filling me full of BS or not. My first thought was they are using MAC filtering, but I ruled that out by taking my laptop home and disabling the internal wireless adapter and using a USB wireless adapter to provide a new MAC. I was still able to connect. When I try from any other device I get the following message "The Local Security Authority cannot be contacted" It's kind of frustrating because I am rarely at me desk and travel between two of our facilities frequently. It was nice to be able to check mail on my iPhone instead of now tethering the laptop to the phone to check mail. |
|
Have your admin look at these 2 possible solutions http://support.microsoft.com/kb/832981 or 1). Open the properties of the problematic account in AD Users and Computers. 2). Click the Account tab. 3). Click the Log On To button. 4). Set it to All Computers. ETA: You can use an Outlook client without a vpn via RPC. |
|
SSL certificates... as your computer tried to connect with the OWA server, it sends a request to your pc asking for the SSL certificate. If you don't have it to authenticate, it won't allow the connection...
Same thing happens if you try to connect and the server certificate isn't published. Make sure you're trying to go to the correct URL... Make sure you're trying to go to the correct IP address as well. I didn't stay at Holiday Inn Express. I'm NOT an Exchange administrator... this is just from my experience of fuckin' with the system and talking to my IT guys that deal with Exchange shit daily. |
|
Quoted:
Thanks, I will share that info with our IT admin. My original question is still unanswered though. How does the server know what computer I am using? It doesn't know. It's something configured on one machine that isn't on the other, like an installed certificate, or maybe even domain authentication stuff that was enabled during the upgrade and your other devices aren't members of the domain. Also, regarding real outlook and the VPN, I think you'll find that given enough time, you'll start to prefer OWA. It functions exactly like outlook, including tray notifications and so on, if you use IE, except that it can't really hang / take over the machine. Since it's in the browser, you can always kill it by killing the browser, and there's no risk to damaging PSTs etc. |
|
Quoted:
Quoted:
Thanks, I will share that info with our IT admin. My original question is still unanswered though. How does the server know what computer I am using? It doesn't know. It's something configured on one machine that isn't on the other, like an installed certificate, or maybe even domain authentication stuff that was enabled during the upgrade and your other devices aren't members of the domain. Also, regarding real outlook and the VPN, I think you'll find that given enough time, you'll start to prefer OWA. It functions exactly like outlook, including tray notifications and so on, if you use IE, except that it can't really hang / take over the machine. Since it's in the browser, you can always kill it by killing the browser, and there's no risk to damaging PSTs etc. And you don't need a VPN anymore. Outlook Anywhere (aka RPC over HTTPS) allows for the use of the real Outlook client across HTTPS. |
|
Quoted:
Quoted:
Quoted:
Thanks, I will share that info with our IT admin. My original question is still unanswered though. How does the server know what computer I am using? It doesn't know. It's something configured on one machine that isn't on the other, like an installed certificate, or maybe even domain authentication stuff that was enabled during the upgrade and your other devices aren't members of the domain. Also, regarding real outlook and the VPN, I think you'll find that given enough time, you'll start to prefer OWA. It functions exactly like outlook, including tray notifications and so on, if you use IE, except that it can't really hang / take over the machine. Since it's in the browser, you can always kill it by killing the browser, and there's no risk to damaging PSTs etc. And you don't need a VPN anymore. Outlook Anywhere (aka RPC over HTTPS) allows for the use of the real Outlook client across HTTPS. That's true, though I still prefer OWA to the real outlook client. Using strictly OWA solved a lot of "problems" for me –– like creating rules that were local to the client and not being run when I was on via OWA from somewhere else, or outlook hanging and bogging the whole machine down while I tried to kill it. There's almost nothing outlook can do that OWA can't, so long as you use IE to access OWA. Using other browsers for OWA results in a very... well lets call it "retro" webmail experience. |
|
Quoted:
Have your admin look at these 2 possible solutions http://support.microsoft.com/kb/832981 or 1). Open the properties of the problematic account in AD Users and Computers. 2). Click the Account tab. 3). Click the Log On To button. 4). Set it to All Computers. ETA: You can use an Outlook client without a vpn via RPC. That was it. I didn't get to talk to our IT guy. I did run into a technician from the IT service that we use who was in working on our server. I explained the situation and he couldn't figure it out either so I pulled up this thread on my iPhone. With the above 4 steps I was online again in seconds. It looked like I was only set to log on from 5 different computers. Thanks again! |