vbscript: Remote Desktop Disconnected
|
Prev: HELP! Lost Raid 1, now Error loading operation system!
Next: Problem running Best Practices and other MS programs
From: Jim Graue on 30 Sep 2008 14:21 Hello, LW: My replies/comments/questions are in-line: below: "Lanwench [MVP - Exchange]" wrote: > 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. Ah! I see what you're referring to, here. An A record is as good as an MX record, here. See below. > > > 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? I don't know how others do this. I know what I've done in the past that has worked, and so I use this tack: Most companies, mine included, have a hosted Website. Generally, the hosting service handles POP3 mail. When an SBS is installed, it's just as easy to change the MX record at the hosting service as it is to create an A record (I don't control public DNS for my domain). I'm not telling you anything you don't know, and I'm not pretending to have a handle on all of this, but SBS is supposed to be a mail server, right? So, rather than create an A record for a test (which will change), why not just change the MX record, which will be permanent, anyway? I don't want my SBS to handle our Website. That sort of uptime is tough to maintain (though e-mail has gotten very important to any company, too). I can get my hosting service or ISP to become a backup e-mail store, though, while providing backup for a Website might have its nuances. I'm happy to entertain another train of thought. I defer to your extensive knowledge in this arena. -- Best regards, Jim Graue
From: Lanwench [MVP - Exchange] on 30 Sep 2008 15:12 Jim Graue <JimGraue(a)discussions.microsoft.com> wrote: > Hello, LW: > > My replies/comments/questions are in-line: below: > > > "Lanwench [MVP - Exchange]" wrote: > >> 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. > > Ah! I see what you're referring to, here. An A record is as good as > an MX record, here. See below. And a wink's as good as a nudge to a blind bat, eh? > >> >>> 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? > > I don't know how others do this. I know what I've done in the past > that has worked, and so I use this tack: Most companies, mine > included, have a hosted Website. Yep. > Generally, the hosting service > handles POP3 mail. If they don't have their own mail server in house, yes. > When an SBS is installed, it's just as easy to > change the MX record at the hosting service as it is to create an A > record (I don't control public DNS for my domain). Well - an MX record *uses* an A record. For example, if your mx record is mail.mydomain.com, then mail.mydomain.com is an A record. When you change your mail to point somewhere else, you can just change the IP address specified for mail.mydomain.com to the new one. Or you can set up a new A record (blah.mydomain.com) and specify the IP address you wish. You could use that in your MX record, or not. It's not really related. > I'm not telling > you anything you don't know, and I'm not pretending to have a handle > on all of this, but SBS is supposed to be a mail server, right? Exchange is, yes. > So, > rather than create an A record for a test (which will change), why > not just change the MX record, which will be permanent, anyway? Well - you can set up mail.mydomain.com and point it at 123.123.123.123 (your public IP), and set up your SSL cert to use mail.mydomain.com & use mail.mydomain.com for your RWW access. All this without disturbing your current mail setup. When the time comes to switch from your hosted mail to bringing it in house, you just change your public MX record to use mail.mydomain.com (the new A record you created) and remove the old one. Boom. > I > don't want my SBS to handle our Website. Nope -nor should you. > That sort of uptime is > tough to maintain It's also a big security risk, hosting that in-house - and you should never do it on your DC. Best to keep it outside. > (though e-mail has gotten very important to any > company, too). I can get my hosting service or ISP to become a > backup e-mail store, though, Yes, although this is not as frequently offered as it used to be and can increase your spam delivery. > while providing backup for a Website > might have its nuances. > > I'm happy to entertain another train of thought. I defer to your > extensive knowledge in this arena. Aw, I just make this stuff up as I go along, you know. ;-)
From: Jim Graue on 30 Sep 2008 15:56 Hello, LW: My replies/comments/questions are in-line, below: -- Best regards, Jim Graue "Lanwench [MVP - Exchange]" wrote: > Jim Graue <JimGraue(a)discussions.microsoft.com> wrote: > > Hello, LW: > > > > My replies/comments/questions are in-line: below: > > > > > > "Lanwench [MVP - Exchange]" wrote: > > > >> 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. > > > > Ah! I see what you're referring to, here. An A record is as good as > > an MX record, here. See below. > > And a wink's as good as a nudge to a blind bat, eh? My favorite is: A nod's as good as a wink to a blind horse, but I have no quibble with learning new twists on old favorites. > > > >> > >>> 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? > > > > I don't know how others do this. I know what I've done in the past > > that has worked, and so I use this tack: Most companies, mine > > included, have a hosted Website. > > Yep. > > > Generally, the hosting service > > handles POP3 mail. > > If they don't have their own mail server in house, yes. > > > When an SBS is installed, it's just as easy to > > change the MX record at the hosting service as it is to create an A > > record (I don't control public DNS for my domain). > > Well - an MX record *uses* an A record. For example, if your mx record is > mail.mydomain.com, then mail.mydomain.com is an A record. When you change > your mail to point somewhere else, you can just change the IP address > specified for mail.mydomain.com to the new one. Or you can set up a new A > record (blah.mydomain.com) and specify the IP address you wish. You could > use that in your MX record, or not. It's not really related. > > > I'm not telling > > you anything you don't know, and I'm not pretending to have a handle > > on all of this, but SBS is supposed to be a mail server, right? > > Exchange is, yes. > > > So, > > rather than create an A record for a test (which will change), why > > not just change the MX record, which will be permanent, anyway? > > Well - you can set up mail.mydomain.com and point it at 123.123.123.123 > (your public IP), and set up your SSL cert to use mail.mydomain.com & use > mail.mydomain.com for your RWW access. All this without disturbing your > current mail setup. When the time comes to switch from your hosted mail to > bringing it in house, you just change your public MX record to use > mail.mydomain.com (the new A record you created) and remove the old one. > Boom. OK, now I'm confused. My Webhost uses mail.mydomain.com on which to home e-mail. If I have them create an A record for mail.mydomain.com, when mail comes looking for me(a)mydomain.com, won't DNS get confused? Or, is the MX record for mail.mydomain.com pointing to 231.231.231.231, while the A record for mail.mydomain.com is pointing to 123.123.123.123? If, on the other hand, I used rww.mydomain.com to create the A record pointing to 123.123.123.123, create the cert, etc., when it's time to switch mail from hosted to in-house, there will be two names that will resolve to the same address (not the first time this would have happened in the world, is it?), rww.mydomain.com and mail.mydomain.com. When I use rww.mydomain.com, the cert will match. Of course, if I want consistency with how I've set this up elsewhere, I could remake the cert, at that point, to match mail.mydomain.com. Believe it or not, I'm not trying to complicate things. > > > I > > don't want my SBS to handle our Website. > > Nope -nor should you > > That sort of uptime is > > tough to maintain > > It's also a big security risk, hosting that in-house - and you should never > do it on your DC. Best to keep it outside. I'm glad to be reminded of this. That's why MS makes the Web edition of W2K3, huh? Not suggesting that I would use it in our situation; we're not big enough to need/want our own in-house Web server. > > (though e-mail has gotten very important to any > > company, too). I can get my hosting service or ISP to become a > > backup e-mail store, though, > > Yes, although this is not as frequently offered as it used to be and can > increase your spam delivery. Yes, that's true. I use some wicked software on Exchange to tamp spam down: Sunbelt's Ninja ROCKS. > > > while providing backup for a Website > > might have its nuances. > > > > I'm happy to entertain another train of thought. I defer to your > > extensive knowledge in this arena. > > Aw, I just make this stuff up as I go along, you know. ;-) Anyway, it's nice of you to share. Those of us starting out really appreciate the help. -- Best regards, Jim Graue
From: Lanwench [MVP - Exchange] on 30 Sep 2008 20:07
Jim Graue <JimGraue(a)discussions.microsoft.com> wrote: <snipped for length> >> And a wink's as good as a nudge to a blind bat, eh? > > My favorite is: A nod's as good as a wink to a blind horse, but I > have no quibble with learning new twists on old favorites. New? Not hardly! http://www.youtube.com/watch?v=SrDFGa0juCM <snip> >> Well - you can set up mail.mydomain.com and point it at >> 123.123.123.123 (your public IP), and set up your SSL cert to use >> mail.mydomain.com & use mail.mydomain.com for your RWW access. All >> this without disturbing your current mail setup. When the time comes >> to switch from your hosted mail to bringing it in house, you just >> change your public MX record to use mail.mydomain.com (the new A >> record you created) and remove the old one. Boom. > > OK, now I'm confused. My Webhost uses mail.mydomain.com on which to > home e-mail. If I have them create an A record for > mail.mydomain.com, But you've just shown that you already have an A record for that. That's what your current MX record is, which means it's an A record. I used mail. as an example. It could just as easily be toasteroven.mydomain.com or petercottontail.mydomain.com. > when mail comes looking for me(a)mydomain.com, won't > DNS get confused? Not relevant.... > Or, is the MX record for mail.mydomain.com Ah. There's no such thing unless you have a subdomain (let's not go there). You have an MX record for mydomain.com. It specifies the A record mail.mydomain.com. That A record points to 123.123.123.123 or whatever the ISP's mail server is. > pointing to 231.231.231.231, while the A record for mail.mydomain.com > is pointing to 123.123.123.123? Not relevant, as you can now see. > , on the other hand, I used > rww.mydomain.com to create the A record pointing to 123.123.123.123, > create the cert, etc., when it's time to switch mail from hosted to > in-house, there will be two names that will resolve to the same > address (not the first time this would have happened in the world, is > it?), rww.mydomain.com and mail.mydomain.com. That's fine. You can have a gazillion hosts pointing at the same IP. > When I use > rww.mydomain.com, the cert will match. Of course, if I want > consistency with how I've set this up elsewhere, I could remake the > cert, at that point, to match mail.mydomain.com. Yes. Is this clearer now? http://www.msexchange.org/tutorials/MF002.html may help. > > Believe it or not, I'm not trying to complicate things. No worries :) > >> >>> I >>> don't want my SBS to handle our Website. >> >> Nope -nor should you > >>> That sort of uptime is >>> tough to maintain >> >> It's also a big security risk, hosting that in-house - and you >> should never do it on your DC. Best to keep it outside. > > I'm glad to be reminded of this. That's why MS makes the Web edition > of W2K3, huh? Well, that's one reason.... > Not suggesting that I would use it in our situation; > we're not big enough to need/want our own in-house Web server. I'm witn you. > >>> (though e-mail has gotten very important to any >>> company, too). I can get my hosting service or ISP to become a >>> backup e-mail store, though, >> >> Yes, although this is not as frequently offered as it used to be and >> can increase your spam delivery. > > Yes, that's true. I use some wicked software on Exchange to tamp > spam down: Sunbelt's Ninja ROCKS. I'm a Vamsoft ORF fan, myself. But whatever works :) > >> >>> while providing backup for a Website >>> might have its nuances. >>> >>> I'm happy to entertain another train of thought. I defer to your >>> extensive knowledge in this arena. >> >> Aw, I just make this stuff up as I go along, you know. ;-) > > Anyway, it's nice of you to share. Those of us starting out really > appreciate the help. Hope it helps. Post back if you're still having trouble. Remember, using your real domain name in the cert may not fix the problem, but it's what I'd start with. |