Would like to connect to exchange server from user/computer which is NOT a domain member
I have a VPN tunnel between my work and home.
My home computer is not a member of the domain, and I would like to access my Exchange email account from Outlook XP at home.
Because I would like to be able to sync my Palm from home, I cannot use OWA.
I cannot find any means of authenticating my PC to Exchange, although the VPN allows the 2 to "see" each other (I don't need to forward ports).
My home computer is not a member of the domain, and I would like to access my Exchange email account from Outlook XP at home.
Because I would like to be able to sync my Palm from home, I cannot use OWA.
I cannot find any means of authenticating my PC to Exchange, although the VPN allows the 2 to "see" each other (I don't need to forward ports).
There is no requirement that a PC running Outlook be a domain member in order to connect to Exchange.
Are you getting a login prompt at all? If not then it may be a firewall blocking something, or some other configuration error.
If you are getting a login prompt then try with and without the domain name as suggested by Cyclops3590.
Are you getting a login prompt at all? If not then it may be a firewall blocking something, or some other configuration error.
If you are getting a login prompt then try with and without the domain name as suggested by Cyclops3590.
Why are you not just using Outlook 2003 and RPC/HTTP?
Did you try the different authentication methods in the Outlook profile?
ASKER
I am not getting any kind of login prompt. I can't even create the profile.
redseatechnologies,
I am using 2002 because I have a spare license (plus I'm not a fan of the 2003 interface).
is this not possible with office XP?
redseatechnologies,
I am using 2002 because I have a spare license (plus I'm not a fan of the 2003 interface).
is this not possible with office XP?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I didn't know I had an Outlook license with each Exchange CAL. I'm still not wild obout the Outlook 2003 interface, but I did get it to work.
BTW, I don't think RPC/HTTP is necessary in this configuration. The VPN tunnel allows full access to all ports. Effectivly, it is like having the computer inside the firewal boundary, just not a member of the domain.
BTW, I don't think RPC/HTTP is necessary in this configuration. The VPN tunnel allows full access to all ports. Effectivly, it is like having the computer inside the firewal boundary, just not a member of the domain.
VPNs are a PITA though - if all you want is email, they are not worth the hassle.
Once your users are connected to the VPN, they browse the net via your local lan - RPC/HTTP is a far simpler thing for users, and isn't as daunting as it may seem.
-red
Once your users are connected to the VPN, they browse the net via your local lan - RPC/HTTP is a far simpler thing for users, and isn't as daunting as it may seem.
-red
ASKER
Very true for most users, but in this case It is only for me, not the other users (they use OWA). I'm the sysadmin, and like to have full access when I'm at home.
Fair enough, I know what that is like.
Still, I encourage you to configure RPC/HTTP - all you need is an SSL certificate, and even a homegrown will do the job (or you can get a good cheap one for like $20). Even if you want to connect over a VPN connection, RPC/HTTP is what I use. It is quicker, and it works even when you are not on the VPN.
-red
Still, I encourage you to configure RPC/HTTP - all you need is an SSL certificate, and even a homegrown will do the job (or you can get a good cheap one for like $20). Even if you want to connect over a VPN connection, RPC/HTTP is what I use. It is quicker, and it works even when you are not on the VPN.
-red
ASKER
might be a good idea...
Doing some reading, I found that one of the requirements is that RPC over HTTP/S requires Windows Server 2003 in a Global Catalog role. My Exchange server is separate from my DCs (one of which is the GCS). Is this an issue?
Doing some reading, I found that one of the requirements is that RPC over HTTP/S requires Windows Server 2003 in a Global Catalog role. My Exchange server is separate from my DCs (one of which is the GCS). Is this an issue?
ASKER
I followed the guide below:
http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm
I need to reboot the exchange server, so I'll have to wait for the weekend. I'll report back after I test it.
http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm
I need to reboot the exchange server, so I'll have to wait for the weekend. I'll report back after I test it.
That guide isn't going to work if your exchange server is not a DC (but let's see how you go).
If it fails, try this -> http://www.amset.info/exchange/rpc-http.asp
-red
If it fails, try this -> http://www.amset.info/exchange/rpc-http.asp
-red
ASKER
Yea, I noticed the "global catalog server" part, and wondered if that would be an issue.
I'll see how it goes and try that link if it doesn't work.
Probebly better to do this durring the weekend while people are off the system anyway.
I'll see how it goes and try that link if it doesn't work.
Probebly better to do this durring the weekend while people are off the system anyway.
<<netbios domain name>>\<<username>>