Re: Remote access ip/remote okay, domain/remote NOPE
- From: "SBS in Silicon Valley" <user123@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 5 Feb 2007 12:29:39 -0800
Here is what I do Cheryl to elimnate confusion and simplify things. I'm
going to use mycompany as mail server name. My domain name ia different so I
don't have certain issues.
You send me an email at allen@xxxxxxxxxxxxx and it comes to my SMTP Exchange
server and delivers the mail. My A record for my mail server is
mail.mycompany.com which is linked to the external IP of my SBS server. My
MX record points to mycompany.com. So in my case I cannot use or create
another A name record to mycompany.com becuase it is used for our external
website that is tied to a different IP. So I had my ISP create a new alias
C.Name record and I called it gomycompany.com so for anything that uses that
external IP I can use this alias.
For OWA they use https://gomycompany.com/exchange
For remote they use https://gomycompany.com/remote
For external access for comapnyweb they can use https://gomycompany.com:444
and even the access my Citrix server they can use http://gomycomapny.com
So you see the whole idea of creating an A record is to use an laternative
name for the IP address it is linked to. Now given the above information you
can see that I can also use https://mail.mycompany.com/remote because
mail.mycompany.com and mycomapny.com are linked to the same external IP.
Hope all this helps out.
"CherylDetrick" <CherylDetrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C21FCCC-719F-4A92-9262-204D03C3463A@xxxxxxxxxxxxxxxx
Okay.. another question: can I tell CEICW that I want to use a specific
name
(like my .org)? And if I do, I have an A record setup for that, but I
can't
setup the .local through yahoo. Everything they have is webserver.org and
that is where it stops.
I need an A record not an MX record right?
"SBS in Silicon Valley" wrote:
Who hosts your Exchange MX records? Your MX records are the ones that
direct
emails sent to you to the mail server whoever hosts it whether it be
yahoo
or you host your own SMTP mail servers. Do you have email delivered
directly
to your own SMTP Exchange mail server or do you use POP3 and pull your
emails down from Yahoo?
"CherylDetrick" <CherylDetrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:3B7CD611-CDBF-4E72-A6D9-4ACDC809B2A4@xxxxxxxxxxxxxxxx
Hi:
Okay, this is probably a REALLY stupid question. Here is the
situation,
our
domain is hosted via Yahoo. All the A records on our control hosting
panel
there end in our domainwebsite.org. However, my server is
publishing.serverdomain.local. I'm currently on the phone with yahoo
tech
support (that is an adventure, they know less than I do!) ... is there
another way to create an A record?
"SBS in Silicon Valley" wrote:
The certificate must match the DNS A name record. So seeing how you
are
using a static IP address you'll always get this error message. So
most
likely you are using the default certificate generated when you run
the
CEICW which is usually domainname.local. You need to register a FQDN
and
create a new certificate. The reason why you cannot access
https://yourdomain.com/remote because there is no DNS A record for
yourdomain.com that is linked to the IPaddress. DNS does not know
about
yourdomain.com. Most likely your mail server is registered at your ISP
as
mail.yourdomain.com and you can likely get to
https://mail.yourdomain.com/remote
"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:OpAULbUSHHA.5100@xxxxxxxxxxxxxxxxxxxxxxx
What public DNS A record are you using for the CEICW FQDN on the
self
generated certificate?
"CherylDetrick" <CherylDetrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:01218B76-6226-4A6F-BB52-2EBC3039E3C3@xxxxxxxxxxxxxxxx
Using SBS 2k3 release 2 without a desktop workstation (my laptop is
my
workstation in the office and my remote outside of it); I can only
access
the
server using our staticip/remote, not https://domain/remote. Of
course,
when
I access with the staticip/remote, I get the error message that the
certificates don't match and that causes issues too.
So, question, why can I access to the ip and not the domain. (yes,
I've
run
the remote connection wizard on the server.)
Help!
.
- Follow-Ups:
- Re: Remote access ip/remote okay, domain/remote NOPE
- From: CherylDetrick
- Re: Remote access ip/remote okay, domain/remote NOPE
- References:
- Re: Remote access ip/remote okay, domain/remote NOPE
- From: Steve
- Re: Remote access ip/remote okay, domain/remote NOPE
- From: SBS in Silicon Valley
- Re: Remote access ip/remote okay, domain/remote NOPE
- From: SBS in Silicon Valley
- Re: Remote access ip/remote okay, domain/remote NOPE
- From: CherylDetrick
- Re: Remote access ip/remote okay, domain/remote NOPE
- Prev by Date: Re: Vista VPN
- Next by Date: Re: Remote access ip/remote okay, domain/remote NOPE
- Previous by thread: Re: Remote access ip/remote okay, domain/remote NOPE
- Next by thread: Re: Remote access ip/remote okay, domain/remote NOPE
- Index(es):
Relevant Pages
|