Link to home
Start Free TrialLog in
Avatar of Night_Wolf87
Night_Wolf87

asked on

Hamchi and vpn

I am trying to find out if I can keep my outllook looking at the same dns name when i connect using hamachi. I changed the hamchi preferred dns to the hamachi IP address of the server that host my exchange but the PTR record for my hamchi IP is set up for a nick name that is different from the address of the local domain and local name. I did this because the guide I was using said that if I set the name as the same in the pointer record it would interfere with my local mail service. I want to know if there is a way I can set up my DNS to see both IP addresses as the same name so When I am home I can get mail and when I am in the office I can get the mail without having to be logged into my hamachi server.
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Night_Wolf87
Night_Wolf87

ASKER

I have been trying to figure out how to set up the last section of the server configuration. I need an fqdn (fully qualified domain name) and an ssl certificate to go with it. However I though that I could just use the subdomain of my site mail.website.com but the company that provided me with the domain and hosted my website says that I can only link my ssl to my www.website.com
Do I need to link it to my www or am I going about this the wrong way?
Do I need to own mail.website.com as apposed to having a sub domain?
I assume this is not Small Business Server? It is much simpler and different.
Also I am assuming you have your own Exchange server and it is not a hosted service?
You do need an external DNS record that points to your Exchange server such as mail.MyDomain.com. You should be able to create a new self-signed SSL certificate within IIS, but I have never done so for Exchange, this is quite simple with SBS. If doing so then you need also enable OWA (Outlook web Access), receive a certificate warning, and accept, download, and install the certificate from that site. The other option is to purchase an additional SSL cert for this FQDN. The one for your web site will not work.

I have not worked with rpc/http on a stand alone Exchange server so I am not that familiar with the configuration I am afraid. My knowledge is much stronger in the VPN area, where I found your question. If continuing to have problems you may want to post a question in the Exchange topic area. I do use rpc/http on a daily basis and cannot imagine living without it.

The following link may be a little simpler, by Sembee, the leading Experts-Exchange Exchange specialist.
http://www.amset.info/exchange/rpc-http.asp
This may be of further help.
http://www.microsoft.com/downloads/details.aspx?FamilyId=F7D2D6E5-579F-4779-A6B8-7EF931EC02A5&displaylang=en
Thanks Night_Wolf87.
Cheers !
--Rob