Internet domains, SBS domains, and how they mix

Discussion in 'Windows Small Business Server' started by Jim Graue, Dec 14, 2007.

  1. Jim Graue

    Jim Graue Guest

    Hi, all:

    We own a domain name, say, mydomain.com, which is hosted somewhere other
    than here. When configuring our SBS, I opted to call it
    sbs.mytown.mydomain.com. Probably, it would be a good idea, I'm going to
    guess, to contact the host for mydomain.com and tell them that I've added
    sbs.mytown.mydomain.com, and they could create an MX record for it?

    I'm having some trouble with DNS. I've got a TS on the network and a bunch
    of thin clients. When I try to logon, they take a long time unless I've just
    rebooted the SBS.
     
    Jim Graue, Dec 14, 2007
    #1
    1. Advertisements

  2. Jim Graue

    Alwin Guest

    Hi Jim,

    I'm only going to address your domain question, because about the other
    question I don't have much experience with thin clients...

    it's possible to have a subdomain called mytown and then point a mx record
    to your smtp server to deliver e-mail, cause that's what you want to reach
    with a MX record right? But i'm curious, does the organization have several
    offices / divisions and that's why you want to create a subdomain "mytown"
    for it?

    if you only have 1 single office or division, why not just go for a simple
    mydomain.local domain name and change the mx record for the mydomain.com to
    your server.

    as of the DNS issues, perhaps you can perform some tests like dcdiag,
    netdiag, ipconfig /all ?

    good luck
     
    Alwin, Dec 14, 2007
    #2
    1. Advertisements

  3. Jim Graue

    Jim Graue Guest

    Hi, Alwin:

    My replies/comments are in-line, below:

    Not yet.
    Changing a domain name in SBS isn't possible, to my understanding, without
    flattening and rebuilding. I'm not keen to do that.
    Thanks, I'll do those.
     
    Jim Graue, Dec 14, 2007
    #3
  4. Jim Graue

    Joe Guest

    The SBS name and domain name have no DNS relevance outside your network,
    though as noted, the SBS name will normally appear in some of the email
    headers. Your domain hosting company can make an A record for
    <anythingatall>.domain.com and set the MX record to it. The host
    <anythingatall>.domain.com doesn't need to exist anywhere. It's the
    official name of your mail server, but doesn't need to be the real name.

    What you will ideally need is for your ISP (not the domain host, unless
    they happen to be the same company) to adjust the PTR record for your
    public IP address to also read <anythingatall>.domain.com, so that it
    complements an A record which points to the public IP address. Some
    email servers will reject mail from an IP address which does not conform
    to this. Finally you should configure the HELO string your Exchange
    server uses to the same name again. This is done in the FQDN
    configuration of the default SMTP server. This is less important, but it
    is said that some mail servers insist on it.
     
    Joe, Dec 14, 2007
    #4
  5. Jim Graue

    Jim Graue Guest

    Hi, Joe:

    My replies/comments are in-line, below:

    :

    I think I get it, though I reserve the hope that I can ask for further
    clarification, later. I've been having some trouble logging into a terminal
    server (member of domain) on the network; I thought it would be DNS-related,
    and the only anomaly that I could find was the above mess with domain. Now
    that I think of it, the workstations, themselves, have no issue logging onto
    the domain; it's only admin TS on one server and app-mode TS on the other.
    They'll take fully 2 minutes to get logged on, unless I've just rebooted the
    SBS, which is the only DC. ipconfig yields nothing unusual, all systems
    point to SBS as only DNS, WINS, DHCP (well, servers have static private
    addresses), gateway, etc. The hang-up is on "applying personal settings,"
    which always smacks of DNS confusion in AD, right?

    Even after a reboot, I can't get Outlook on the app-mode TS to connect to
    the Exchange server. Outlook reports that Exchange isn't available, I think,
    and I can't get the username to resolve. I've used the CEICW several times
    to see if I could fix it, but, so far, no luck.

    Sorry, I should repost at the top rather than dump this all here. The
    struggle continues!

    Best regards
    Jim Graue
     
    Jim Graue, Dec 14, 2007
    #5
  6. Hello Jim,

    Thank you for posting here. Let's also thank Joe and Alwin for the input.

    According to your description, I understand that it will take you long time
    to logon internal Terminal Server. If I have misunderstood the problem,
    please don't hesitate to let me know.

    Based on my research, I suggest we try the following steps to see if we can
    resolve this issue:

    1. Ensure the SBS does not have performance issue when the issue happen.

    2. Please ensure the Terminal Server's DNS is also point to SBS.

    3. Do you enable roaming profile for the logon user account? If yes, please
    disable the roaming profile and try again.

    4. Please rerun the CEICW to make sure your SBS 2003 server have right
    network configuration. Go through the follow KB and rerun CEICW carefully.

    How to configure Internet access in Windows Small Business Server 2003
    http://support.microsoft.com/kb/825763/en-us

    If we cannot resolve the issue after we perform the above steps, please
    help me collect some information for further investigation:

    1. Does the logon taking long time issue happen on external clients or
    internal clients or all clients?

    2. Run command "ipconfig /all > c:\ipconfig_sbs.txt" and "route print >
    c:\route_sbs.txt" on SBS, send the files c:\ipconfig_sbs.txt and
    c:\route_sbs.txt to me at

    3. Run command "ipconfig /all > c:\ipconfig_client.txt" and "route print >
    c:\route_client.txt" on problematic client, send the files
    c:\ipconfig_client.txt and c:\route_client.txt to me at


    4. Run command "ipconfig /all > c:\ipconfig_terminal.txt" and "route print
    c:\ipconfig_terminal.txt and c:\route_terminal.txt to me at


    5. Gather MPS network report on Terminal Server:

    a. Download MPSrepot_network from
    http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
    15706/MPSRPT_NETWORK.EXE

    b. Run MPSRPT_NETWORK.exe.

    c. The tool will automatically collect the information. This procedure will
    take 10~15 minutes.

    d. Open Windows Explorer, navigate to the folder:
    %SystemRoot%\MPSReports\Network\Reports\Cab\

    e. Send the .cab file directly to me at

    I hope these steps will give you some help.

    Merry Christmas and happy new year!

    Best regards,

    Terence Liu(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | Thread-Topic: Internet domains, SBS domains, and how they mix
    | thread-index: Acg+lvI1b3N3tn6sSY2xFv1DTyO2dA==
    | X-WBNR-Posting-Host: 207.46.19.197
    | From: =?Utf-8?B?SmltIEdyYXVl?= <>
    | References: <>
    <>
    | Subject: Re: Internet domains, SBS domains, and how they mix
    | Date: Fri, 14 Dec 2007 13:19:00 -0800
    | Lines: 47
    | Message-ID: <>
    | MIME-Version: 1.0
    | Content-Type: text/plain;
    | charset="Utf-8"
    | Content-Transfer-Encoding: 7bit
    | X-Newsreader: Microsoft CDO for Windows 2000
    | Content-Class: urn:content-classes:message
    | Importance: normal
    | Priority: normal
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
    | Newsgroups: microsoft.public.windows.server.sbs
    | Path: TK2MSFTNGHUB02.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:82081
    | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Hi, Joe:
    |
    | My replies/comments are in-line, below:
    |
    | "Joe" wrote:
    |
    | <SNIP>
    | >
    | > The SBS name and domain name have no DNS relevance outside your
    network,
    | > though as noted, the SBS name will normally appear in some of the email
    | > headers. Your domain hosting company can make an A record for
    | > <anythingatall>.domain.com and set the MX record to it. The host
    | > <anythingatall>.domain.com doesn't need to exist anywhere. It's the
    | > official name of your mail server, but doesn't need to be the real name.
    | >
    | > What you will ideally need is for your ISP (not the domain host, unless
    | > they happen to be the same company) to adjust the PTR record for your
    | > public IP address to also read <anythingatall>.domain.com, so that it
    | > complements an A record which points to the public IP address. Some
    | > email servers will reject mail from an IP address which does not
    conform
    | > to this. Finally you should configure the HELO string your Exchange
    | > server uses to the same name again. This is done in the FQDN
    | > configuration of the default SMTP server. This is less important, but
    it
    | > is said that some mail servers insist on it.
    |
    | I think I get it, though I reserve the hope that I can ask for further
    | clarification, later. I've been having some trouble logging into a
    terminal
    | server (member of domain) on the network; I thought it would be
    DNS-related,
    | and the only anomaly that I could find was the above mess with domain.
    Now
    | that I think of it, the workstations, themselves, have no issue logging
    onto
    | the domain; it's only admin TS on one server and app-mode TS on the
    other.
    | They'll take fully 2 minutes to get logged on, unless I've just rebooted
    the
    | SBS, which is the only DC. ipconfig yields nothing unusual, all systems
    | point to SBS as only DNS, WINS, DHCP (well, servers have static private
    | addresses), gateway, etc. The hang-up is on "applying personal
    settings,"
    | which always smacks of DNS confusion in AD, right?
    |
    | Even after a reboot, I can't get Outlook on the app-mode TS to connect to
    | the Exchange server. Outlook reports that Exchange isn't available, I
    think,
    | and I can't get the username to resolve. I've used the CEICW several
    times
    | to see if I could fix it, but, so far, no luck.
    |
    | Sorry, I should repost at the top rather than dump this all here. The
    | struggle continues!
    |
    | Best regards
    | Jim Graue
    |
     
    Terence Liu [MSFT], Dec 17, 2007
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.