Prev: HELP! Lost Raid 1, now Error loading operation system!
Next: Problem running Best Practices and other MS programs
From: Lanwench [MVP - Exchange] on 29 Sep 2008 20:51
Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> Lan:
>
>
> My replies/comments are in-line, below:
>
> <SNIP>
>
>>>> Did you run the CEICW and select the RWW options you wanted?
>>>
>>> Yes. In CEICW, during the certificate creation phase, I used the
>>> static routable address for the FQDN.
>>
>> I've never tried this with an IP address. Set up an A record, such as
>> rww.mydomain.com, in your domain's public DNS and specify your
>> static IP. Then redo the ssl cert and try again to see what you get.
>
> So, I wonder if the issue is that I don't have a name to resolve to.
> By tomorrow night, I would, anyway, since I planned to put in a
> request to my Webhosting service regarding MX record. I'd have
> mail.mydomain.com as my FQDN, at that point. I'm loath to go to too
> much work to get the bare IP to function when I want to have the MX
> record changed.
>
> I just wanted to be sure that everything was working, but I can see
> that it works from within the LAN. Maybe I ought to wait until
> tomorrow afternoon. If the change of MX record fixes this, I'll post
> then.

Sure. But your MX record is immaterial here - it's an A record you need, and
you could create a totally different one without disrupting your email flow.


From: Jim Graue on 29 Sep 2008 23:38
Hello, LW:

My replies/comments/questions are in-line, below:

"Lanwench [MVP - Exchange]" wrote:

> Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> > Lan:
> >
> >
> > My replies/comments are in-line, below:
> >
> > <SNIP>
> >
> >>>> Did you run the CEICW and select the RWW options you wanted?
> >>>
> >>> Yes. In CEICW, during the certificate creation phase, I used the
> >>> static routable address for the FQDN.
> >>
> >> I've never tried this with an IP address. Set up an A record, such as
> >> rww.mydomain.com, in your domain's public DNS and specify your
> >> static IP. Then redo the ssl cert and try again to see what you get.
> >
> > So, I wonder if the issue is that I don't have a name to resolve to.
> > By tomorrow night, I would, anyway, since I planned to put in a
> > request to my Webhosting service regarding MX record. I'd have
> > mail.mydomain.com as my FQDN, at that point. I'm loath to go to too
> > much work to get the bare IP to function when I want to have the MX
> > record changed.
> >
> > I just wanted to be sure that everything was working, but I can see
> > that it works from within the LAN. Maybe I ought to wait until
> > tomorrow afternoon. If the change of MX record fixes this, I'll post
> > then.
>
> Sure. But your MX record is immaterial here - it's an A record you need, and
> you could create a totally different one without disrupting your email flow.

I tried this (create an A record). When I get to the site (using the IP,
since there is no other way to get to it), I get the cert warning, where I
install the cert. Then, I get a 403 error (URL is forbidden). Maybe I
didn't create the A record in the right place... [forward lookup zone,
mydomain.local]?
--
Best regards,
Jim
From: Duncan McC on 30 Sep 2008 05:53
In article <266FEB46-7CD1-447C-AB73-5687B05E2B9C(a)microsoft.com>,
JimGraue(a)discussions.microsoft.com says...
> Hello, LW:
>
> My replies/comments/questions are in-line, below:
>
> "Lanwench [MVP - Exchange]" wrote:
>
> > Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> > > Lan:
> > >
> > >
> > > My replies/comments are in-line, below:
> > >
> > > <SNIP>
> > >
> > >>>> Did you run the CEICW and select the RWW options you wanted?
> > >>>
> > >>> Yes. In CEICW, during the certificate creation phase, I used the
> > >>> static routable address for the FQDN.
> > >>
> > >> I've never tried this with an IP address. Set up an A record, such as
> > >> rww.mydomain.com, in your domain's public DNS and specify your
> > >> static IP. Then redo the ssl cert and try again to see what you get.
> > >
> > > So, I wonder if the issue is that I don't have a name to resolve to.
> > > By tomorrow night, I would, anyway, since I planned to put in a
> > > request to my Webhosting service regarding MX record. I'd have
> > > mail.mydomain.com as my FQDN, at that point. I'm loath to go to too
> > > much work to get the bare IP to function when I want to have the MX
> > > record changed.
> > >
> > > I just wanted to be sure that everything was working, but I can see
> > > that it works from within the LAN. Maybe I ought to wait until
> > > tomorrow afternoon. If the change of MX record fixes this, I'll post
> > > then.
> >
> > Sure. But your MX record is immaterial here - it's an A record you need, and
> > you could create a totally different one without disrupting your email flow.
>
> I tried this (create an A record). When I get to the site (using the IP,
> since there is no other way to get to it), I get the cert warning, where I
> install the cert. Then, I get a 403 error (URL is forbidden). Maybe I
> didn't create the A record in the right place... [forward lookup zone,
> mydomain.local]?

No, not local. See where Lanwench said "in your domain's public DNS" :)

ie who's yer nameserver/host?

--
Duncan
From: Jim Graue on 30 Sep 2008 13:15
Hello, Duncan McC:

My replies/comments/questions are in-line, below:
"Duncan McC" wrote:

> In article <266FEB46-7CD1-447C-AB73-5687B05E2B9C(a)microsoft.com>,
> JimGraue(a)discussions.microsoft.com says...
> > Hello, LW:
> >
> > My replies/comments/questions are in-line, below:
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> > > Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> > > > Lan:
> > > >
> > > >
> > > > My replies/comments are in-line, below:
> > > >
> > > > <SNIP>
> > > >
> > > >>>> Did you run the CEICW and select the RWW options you wanted?
> > > >>>
> > > >>> Yes. In CEICW, during the certificate creation phase, I used the
> > > >>> static routable address for the FQDN.
> > > >>
> > > >> I've never tried this with an IP address. Set up an A record, such as
> > > >> rww.mydomain.com, in your domain's public DNS and specify your
> > > >> static IP. Then redo the ssl cert and try again to see what you get.
> > > >
> > > > So, I wonder if the issue is that I don't have a name to resolve to.
> > > > By tomorrow night, I would, anyway, since I planned to put in a
> > > > request to my Webhosting service regarding MX record. I'd have
> > > > mail.mydomain.com as my FQDN, at that point. I'm loath to go to too
> > > > much work to get the bare IP to function when I want to have the MX
> > > > record changed.
> > > >
> > > > I just wanted to be sure that everything was working, but I can see
> > > > that it works from within the LAN. Maybe I ought to wait until
> > > > tomorrow afternoon. If the change of MX record fixes this, I'll post
> > > > then.
> > >
> > > Sure. But your MX record is immaterial here - it's an A record you need, and
> > > you could create a totally different one without disrupting your email flow.
> >
> > I tried this (create an A record). When I get to the site (using the IP,
> > since there is no other way to get to it), I get the cert warning, where I
> > install the cert. Then, I get a 403 error (URL is forbidden). Maybe I
> > didn't create the A record in the right place... [forward lookup zone,
> > mydomain.local]?
>
> No, not local. See where Lanwench said "in your domain's public DNS" :)
>
> ie who's yer nameserver/host?

I assumed that LW was referring to my MS domain, since the change in MX
record at the Webhosting service is the same as getting a domain named, say,
"rww.mydomain.com." If the change of MX record at the nameserver/host points
"mail.mydomain.com," to my static, routable IP and I OWN mydomain.com, then I
can use mail.mydomain.com as the name of my SBS on my static, routable IP.
I.e., mail.mydomain.com will resolve to my assigned IP. But, thanks for
your input. It's appreciated.

It follows that when I make the request for MX to point to my system and I
recreate the SSL cert, the name on the cert and the name of the site will be
the same. It's still a little confounding that an IP, by itself, won't allow
usage of RWW/terminal services. After all, resolution, by definition, gives
the requesting program an IP. I'm not one to stand in the way of tech,
however. I just need to make it work. It's what I do.
--
Best regards,
Jim Graue
From: Lanwench [MVP - Exchange] on 30 Sep 2008 13:29
Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:

<snipped for length>

> I assumed that LW was referring to my MS domain, since the change in
> MX record at the Webhosting service is the same as getting a domain
> named, say, "rww.mydomain.com."

Nope - your internal DNS has nothing to do with this. You do not need to
change your MX record (e.g., change your mail hosting) in your public DNS to
do this - set up an *A* (address / host) record, such as
somethingelse.mydomain.com, that points at your public IP.

> If the change of MX record at the
> nameserver/host points "mail.mydomain.com," to my static, routable IP
> and I OWN mydomain.com, then I can use mail.mydomain.com as the name
> of my SBS on my static, routable IP. I.e., mail.mydomain.com will
> resolve to my assigned IP. But, thanks for your input. It's
> appreciated.
>
> It follows that when I make the request for MX to point to my system
> and I recreate the SSL cert, the name on the cert and the name of the
> site will be the same. It's still a little confounding that an IP,
> by itself, won't allow usage of RWW/terminal services. After all,
> resolution, by definition, gives the requesting program an IP. I'm
> not one to stand in the way of tech, however. I just need to make it
> work. It's what I do.

I don't know that you *can't* use an IP address. I have never tried, and
since you have a domain name, why not just set up a record now to test it?


First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: HELP! Lost Raid 1, now Error loading operation system!
Next: Problem running Best Practices and other MS programs