Question Locked

Exchange 2003 Remote Access from Outlook

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi, first time asking a question here.

I've installed exchange at our company for the first time and I've managed to get it working the way I liked it.

However sales rep will also be accessing their e-mails through outlook on their laptops from outside the company network and I haven't been able to get remote access working so far.

If I type the DNS of the server in the server space during the exchange setup in outlook, it seems it can't connect to the server; it doesn't even ask me for the credentials of the server. This is not a DNS issue as Remote Desktop Connection works if I type in the DNS.

I have opened ports 25 and 110 on the router along with port 53 (dns), 143 (imap) and 135 (rpc).

I'm obviously missing something here to get this working and there is so much exchange info out there I can't find what I'm looking for : its like looking for a needle in a haystack.

Any help on getting access to my exchange server through remote outlook access would be very much welcome.

PS : I use exchange 2003 sp1 and windows server 2003 sp2.

UPDATE : Please look at the important update reply I posted. I found what appears to be a solution, but I still have an issue.

9 replies

by bhuvnesh_aim

Hi
I have never get a chance to install Exchange. But i get the traning from Microsoft way back 6 to 8 months ago.
Can u tell me how`s ur exp. in this ?
and also tell me which type of problem ur facing.

Thanks & regards
Bhuvnesh Arora
Mob. +91-9810970695

by optronix_quebec

It's actually the first time I install exchange so I'd say I'm fairly green in regards to exchange. As a matter of fact IT manager isn't even my main function, it's just part of my job. But I am the one who set up from A to Z here, from the server, to the Active Directory structure and even installed all applications so I know pretty much everything there is to know about our system and troubleshooted everything to get it working up to par.

Currently, I have gotten exchange all set up as I wanted it to be : we have two domains and one mailbox can fetch mail from both of these as long as the mailbox name is the same (ex: abc@1.com and abc@1.net). I can also send and receive mails just fine internally and externally so I'd say exchange is working just as it should so far.

What's left to figure out for myself is the remote access part of it : my initial efforts at getting outlook to access my exchange server through our dns name has been uncesful.

The step blocks at the part where outlook checks for the exchange connectivity before finalizing the mailbox. I don't know if its an exchange option I have to open up, if its a port I've missed opening or if its a security setting but I do know that when I get to that point, it doesn't even ask me for the domain logon credentials so obviously it can't get access to the computer where the exchange server is located.

If I do it through our internal network, everything works, but as soon as I attempt to do it through our DNS, it does not. As I've stated, laptop users will be fetching their mail while out of the office so this is paramount. I also want these guys to have full outlook integration just as if they were here and even though I know I could just use Terminal Services to give them access to the server remotely (so access to their Exchange account at the same time) but I'd rather not go through that route to give users as seemless an integration as possible and to keep strain on the server to a minimum.

Any help on this would be appreciated as all the info I've found so far are regarding the Outlook Web Interface or mobile PDA's and cell phone access which are not options I'm looking at as I want full Outlook integration.

Thanks.

by rkuhn040172

You mentioned you don't think it is a DNS issue.

I would suggest that your users use a VPN to connect to the domain for security purposes and then connect to the Exchange server.

by optronix_quebec

Thanks for the info.

However I did look into OWA and it would have been a great way to do things but the reps use the calendar functions in outlook and as I understand it, you can't use calendar from their exchange account using OWA.

Also, I've read that the contacts don't behave the same way as they normally do in Outlook. As in they don't give out suggestions. Since the reps won't exactly be experts in computers. I'd rather have them have as close an experience as can be.

I've found a method which seems to solve that part, now I only need to fix the https issue and I should be in business.

Thanks for the help so far.

by optronix_quebec

Hi

After some digging I seem to have found a solution to get this working which is rpc over http. The article detailing this can be found here : http://support.microsoft.com/kb/833401

However this brought up a new problem.

Right now I have a dynamic ip so I have to use a free no-ip client to get a working dns.

I've been using this DNS to get access to remote desktop and I also use it as my MX record and it works great but the Outlook solution outlined above needs SSL (https). Whenever I add the https in front of the DNS, it doesn't reach the server. If I take the https out, it reaches the server and I get a message to use a secure SSL connection (in internet explorer). I did open port 443 in my firewall for the https.

I figure it might be a no-ip free account limitation so I've mailed them about it but haven't gotten a response yet.

I've never add to use IIS before but I've followed the instructions in the article up there to a tee (I've skipped the SSL certification part for now though).

If anybody has any idea on the next step I'd love to hear about it. I'll keep digging around to see if there's something I missed or something else I need to do.

by optronix_quebec

Hi.

I've finally managed to get this working.

For some reason I needed to create a new Outlook profile for it to work. I also needed to log in using the user@domain.suffix way for it to work.

I even changed basic authentication to NTLM so I can just "set it and forget it" as far as passwords go.

Thanks for people who helped me out with this.

by optronix_quebec

Right now I have terminal services set up to use remote desktop connection so that may be what I end up doing if I can't solve the issue completely.

I know that would work but I'd rather avoid it.

The solution I've found to use rpc through http would seem to solve that but I haven't gotten the https part of it working properly yet.

This discussion is closed to new replies.