Setup OWA on BB 8520 - Problems, as ever?
Hello there,
First things first - I am a newbie here and to bb. So, begging pardons in advance if I seem to be doing some 'silly' mistakes. I have scoured tons of internet material including this forum and others as well as bb's own site and have gone through the documentations. Have become something of someone whom my friends approach to setup their e-mails on their bb. Sad part is I am not able to get my work e-mail setup on mine:shock: To put it in a nut's shell, 1. I am trying to setup my work e-mail OWA on my bb 2. Trying this through my operator's website (tried it on my bb - i am yet to get used to the keypad, so my laptop to the rescue) 3. My company IT guys told me that they will not disclose the POP/IMAP port numbers - hence was forced to go the other way. Tried the auto-forward to private mail option as well - blimey! our IT guys are so paranoid they have blocked this too. 4. Could not wiggle out the IP address of the OWA from the IT team - finally, me dumb wit, found it on the OWA page itself. Below are the details. Mailbox owner: FName, LName [LName.FName@mydomain.com] User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; MS-RTC LM 8) Outlook Web Access experience: Premium User language: English (United Kingdom) User time zone: (GMT+05:30) Chennai, Kolkata, Mumbai, New Delhi Exchange mailbox address: /o=mydomain/ou=First Administrative Group/cn=Recipients/cn=LName.FName Outlook Web Access host address: https://hostaddress.mydomainname.com/owa Outlook Web Access version: 8.1.240.5 Outlook Web Access Proxy Host Address: https://proxyaddress.mydomainname.com/owa Proxy Outlook Web Access version: 8.1.240.5 Proxy server name: hostaddress.mydomainname.com Client Access server name: HOSTADDRESS.MYDOMAINNAME.COM Exchange Client Access server .NET Framework version: 2.0.50727.926 Client Access server operating system version: Microsoft Windows NT 5.2.3790 Service Pack 2 Client Access server operating system language: en-US Microsoft Exchange Client Access server version: 8.1.240.0 Client Access server language: en-US Client Access server time zone: India Standard Time Microsoft Exchange Client Access server platform: 64bit Mailbox server name: MAILSERVER.MYDOMAINNAME.COM Mailbox server Microsoft Exchange version: 8.1.240.0 Other Microsoft Exchange server roles currently installed on the Client Access server: Hub Transport Authentication type associated with this Outlook Web Access session: Basic Authentication type for Microsoft Exchange Client Access server to Client Access server proxy session: Negotiate Public logon: No 5. Tried out the details on my laptop's internet browser and my bb's browser; they were working fine 6. Got the details from the KB05333 documentation and fed them in the page in order with details from 4 & 5 above 7. The moment I hit a 'Next' after I enter the details, the web site seemed to take offence and screamed back "Cannot connect to email server or invalid server name" 8. Checked the web again and tried various combinations (like http's' which I need to use) and so on - with the same disastrous result After trying out for more than a week, I am this close to being desperate. Could some kind souls point me in the right direction please? Appreciate the help in advance PS - My wife always tells me that brevity was never a strong point with me :oops:- apologies for the long story |
Wirelessly posted (Its All About the U!)
If the server is using 2007 , you may have a problem as i do with one corporate site. Max sure your username and mailbox name are correct. I have found that when someones username for entry to a network is different than the prefix of the e-mail address, there is a problem. |
Quote:
Now, I agree that I am a nit wit of the first rate :-? , but I don't think my mail box name is a "#". Any clues here, if you could suggest. |
Ok. Discovered a goof-up - not that it solves the problem. Rather, an aggravation. All this while, I was trying on my office laptop – now when I tried on my personal one, I discovered that the web page which I had specified in the URL is not accessible.
When I pulled some strings, I discovered that the URL is indeed not exposes directly over Internet by the IT boffins. Is there any other way that I can overcome this? Without getting caught and getting fired in the process, that is. As it stands, my job is hanging by the loose threads of a hair :shock: Any help, anyone? |
All times are GMT -5. The time now is 12:13 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.